Modern geospatial delivery on top of rsync.net-backed storage

Keep your storage.
Deliver modern
geospatial APIs.

The Geospatial Data Proxy turns existing archives into a secure
delivery layer for browser apps, files, tiles, STAC, OGC, Esri-style
access, analytics, 3D workflows, transactional editing, and real-
time streaming without requiring an object-storage migration first.

Why buyers care

Modernize access first

The strongest commercial advantage is sequencing: teams can publish useful geospatial products before funding or waiting on a broader storage replatforming effort.

File delivery STAC OGC API COG Point clouds I3S API keys Editing WFS-T StreamServer GPKG

What the platform unlocks

One service boundary can support several classes of data product and buyer need.

Modern access without forced migration Turn archived content into usable delivery surfaces without moving the archive first.
Interoperable publishing Expose STAC, OGC-style, Esri-style, tile, and browser-ready endpoints for varied consumers.
Operational control Support API keys, JWTs, admin UX, health checks, and self-hosted deployment patterns.
Expandable platform scope Start with access and grow into analytics, 3D, collaboration, and site hosting.
Transactional editing Create, update, and delete features through Esri FeatureServer, WFS-T, and GeoJSON transaction endpoints.
Real-time streaming Ingest live data from WebSocket, Kafka, Redis, and HTTP sources with DuckDB-backed buffering and SSE broadcast.

Best-fit buyers

Who this is for

  • GIS and geospatial platform teams modernizing delivery
  • Imagery and remote sensing teams needing search and dynamic raster access
  • Utilities, engineering, infrastructure, and environmental teams with large file-based archives
  • Public-sector and regulated operators who prefer self-hosted control
  • Product teams building partner portals and browser applications around existing geospatial content

“If your archive already lives on rsync.net-backed storage, the next modernization step does not have to be a storage rewrite. It can be a delivery-layer launch.”

Pricing

Simple licensing options for teams that need modern geospatial delivery on top of existing archives.

Geospatial Data Proxy — Standard License

$2,000

Full-featured license for one production deployment. Includes all delivery, catalog, analytics, 3D, editing, and streaming modules. Self-hosted, no recurring fees.

  • All 6 feature modules included
  • File delivery, STAC, OGC, Esri-style APIs
  • Analytics, 3D scenes & point clouds
  • Transactional editing (WFS-T, FeatureServer)
  • Real-time streaming & SSE broadcast
  • API key & JWT-based access control
  • Self-hosted — your infrastructure
  • One-time payment, no subscription
Enterprise / custom

Geospatial Data Proxy — Enterprise License

Custom

Multi-deployment or enterprise arrangement. Includes priority support, custom integration assistance, and expanded deployment rights. Contact us to discuss your requirements.

  • Everything in Standard License
  • Multi-site or multi-tenant deployment rights
  • Priority support + SLA
  • Custom integration assistance
  • Onboarding & setup guidance
  • Source code access available
  • White-label options
  • Volume pricing

Representative platform surfaces

The product story is strongest when one dataset can be consumed in more than one way.

Files and browser apps

  • /files/* for range-capable file delivery
  • /sites/* for static site serving
  • /mbtiles/* for tile serving

Catalog and feature services

  • /stac/* for STAC catalog and item search
  • /ogc/* for OGC API features
  • /vector-tiles/* for PBF vector tiles

Tiles, analytics, and 3D

  • /arcgis/rest/services/* for FeatureServer
  • /arcgis/rest/services/*/MapServer for map service
  • /wfs for WFS-T editing

Ops and management

  • /cog/* for Cloud Optimized GeoTIFF
  • /pointcloud/* for LAZ/LAS delivery
  • /scene/* for I3S 3D scene layers

Transactional data management

  • /admin/* for user/key management
  • /health for service health checks
  • /audit/* for access logging

Real-time data ingestion

  • /stream/* for stream CRUD and SSE subscribe
  • /stream/StreamServer/* for Esri StreamServer

Recommended pilot

Prove value in 30 days

  1. Connect one rsync.net-backed dataset family.
  2. Publish one browser or partner-facing workflow.
  3. Expose one searchable or standards-based endpoint surface.
  4. Add one higher-value workflow such as dynamic COGs, raster analytics, point clouds, 3D scenes, transactional editing, or real-time streaming.
  5. Validate API-key or JWT-based access with a controlled user group.

Core CTA

Start with the delivery problem, not the storage debate.

Lead with one simple message: keep the archive, modernize access, and prove value with a pilot that shows more than one consumption path from the same platform boundary.