Geospatial Data Proxy
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.

Explore feature pages Open slide deck

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.”

Feature pages

Each page turns the documented product capabilities into a clear buyer-facing narrative.

Feature 01

Modernize access without moving storage

Use range-capable file delivery, static site hosting, MBTiles, and dynamic COG rendering to turn existing archives into usable web-facing products.

Feature 02

Turn archives into catalogs and APIs

Expose searchable catalogs and feature access with STAC, OGC-oriented patterns, Esri-style endpoints, and vector-tile paths.

Feature 03

Expand into analytics, tiles, and 3D

Support raster, point-cloud, style, and I3S workflows from the same platform boundary used for file and catalog access.

Feature 04

Give operations and security teams control

Use admin UX, API keys, JWTs, health checks, management APIs, and collaboration routes to make adoption easier.

Feature 05

Edit, create, and update geospatial data in place

Support Esri FeatureServer editing, WFS-T transactions, and GeoJSON-based data creation backed by DuckDB spatial storage.

Feature 06

Ingest and broadcast real-time geospatial data

Stream live data from WebSocket, Kafka, Redis, and HTTP sources with DuckDB buffering, SQL queries, and Esri StreamServer-compatible SSE delivery.

Representative platform surfaces

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

Access

Files and browser apps

  • /data/* for range-capable file delivery
  • /sites/* for public browser apps and dashboards

Discovery

Catalog and feature services

  • /stac/* for catalog and search
  • /api/ogc/* and /arcgis/rest/services* for feature access

Rich delivery

Tiles, analytics, and 3D

  • /tiles/*, /cog/*, and /styles/* for map delivery
  • /api/raster/*, /api/pointcloud/*, and /i3s/* for advanced workflows

Control

Ops and management

  • /_/ for admin UX and user management
  • /health/*, /api/geo/*, and /api/collab/* for operations and controlled access

Editing

Transactional data management

  • /arcgis/*/addFeatures, updateFeatures, deleteFeatures, applyEdits
  • /wfs for WFS-T XML transactions and GeoJSON editing

Streaming

Real-time data ingestion

  • /stream/* for stream CRUD, push, query, and SSE subscribe
  • /stream/StreamServer/* for Esri StreamServer compatibility

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.

Use the slide deck See the API story