Deploy shared spatial datain your environment
SpatialDrive
Store, version, and stream massive spatial data for SpatialEngine applications while keeping deployment and data control inside your environment.
Run SpatialDrive with your infrastructure, identity provider, security controls, and operational policies.
Track changes to spatial objects without forcing every application into one fixed schema.
Stream the data each SpatialEngine client needs while teams work from the same project history.
One versioned store, instead of a stack that has to agree with itself
Most teams assemble spatial infrastructure from an object store, a database, a conversion service, and a pile of exports. Every piece has its own idea of what the data means. SpatialDrive keeps the objects, their attributes, and their history in one place that applications read directly.
- Files in object storage, with the meaning of each file kept somewhere else
- A separate tiling or conversion service for every viewer that needs the data
- A database schema that has to be migrated whenever an application adds a field
- Exports and copies for each consumer, which drift apart immediately
- History kept, at best, as dated folders nobody can query
- One store holding the objects themselves, with their attributes attached
- Schema-flexible objects, so a new attribute does not need a migration
- Clients stream what a view needs directly, with no conversion service in between
- One shared source, so every application reads the same current state
- Full version history that applications can query and roll back
Schema-flexible spatial objects
Applications introduce new object types and attributes as the work changes. There is no migration to schedule and no shared schema for every team to agree on first.
Version history as a dimension
Objects and projects are stored through time, so comparing two states or recovering an earlier one is a query rather than a restore from backup.
Streaming to the client, not the whole file
A SpatialEngine client requests the region and resolution a view needs. Large datasets stay usable without copying them to each machine first.
How SpatialDrive fits
Add SpatialDrive when a SpatialEngine application needs shared data, version history, authorization, and streaming beyond one local session.
Runs inside your environment
Deploy it on your own infrastructure and connect it to your identity provider and access controls, so the data and the policy around it stay where they already are.
Grows without a migration
Applications introduce new objects and attributes as the work changes, without a database migration standing between a team and the next change.
Serves every client from one history
SpatialEngine clients request the data each view needs while SpatialDrive keeps the shared project history behind them.
Plan a SpatialDrive deployment
Tell us what you need to host, version, and stream inside your environment.