Version control for your geospatial data.
Branch, diff, merge, and roll back spatial datasets, the way you already version code. Git-style versioning is coming to ELEMNT in Q4 2026.
ELEMNT is live now, free during early access. Versioning follows in Q4 2026. Early-access testers hear from us first.
Your maps are versioned. Your map data isn’t.
Most geospatial stacks can render a map but cannot tell you who changed the data behind it. A teammate overwrites a layer, a bad import ships to production, an auditor asks “what changed, and when,” and the honest answer is a backup file and a guess. Code has had branches, diffs, and rollbacks for twenty years. Spatial data still works like a shared folder where the last person to save wins.
A Git workflow for spatial data. Q4 2026.
Branch. Spin up a branch of a dataset, edit it safely, and merge when it is ready. Stop editing production in place.
Diff. See exactly what changed between two versions, feature by feature and attribute by attribute.
Review and merge. Review spatial changes before they land, the way you review a pull request.
Roll back and time travel. Restore any prior version, or query your data as it stood on any date.
This is a data-integrity feature, not a rendering feature.
When a bad dataset ships, you want a branch to roll back, a diff to review, and an audit trail the auditor can read. Versioning is the layer that makes spatial data reproducible: tag the exact version behind a published map, share it, and reproduce that map months later. It is the capability regulated-industry and data-heavy teams ask about most, and the one most map platforms still do not offer at SaaS scale.
The platform it runs on is live today.
Versioning lands in Q4 2026. The cloud-native platform underneath it is live now, free during early access, with:
- Import: six open formats, plus zip and URL
- Organize: orgs, projects, collections, schema and hierarchy
- Tiles: PMTiles generation from any collection
- Serve: OGC API Features Part 1 + Style JSON
- Export: the same open formats out, no trapped data
- Credentials: API keys and service accounts
(Cloud-Optimized GeoTIFF, Zarr, PostGIS, and Snowflake are on the post-GA roadmap, not in the launch build.)
What is shipping, and when.
- July 16, 2026: GA platform live: import in open formats, PMTiles generation, OGC API Features + Style JSON. Free during early access.
- Q4 2026: Git-style data versioning. Branch, diff, merge, roll back, time-travel queries.
- Q1 2027: Real-time collaborative editing with a feature-level audit trail.
- Release trains: Agent access through Model Context Protocol support.
- Release trains: Datastore drivers for BigQuery, ClickHouse, and MongoDB.
- Release trains: A self-host option for teams with data-sovereignty requirements.
We publish the dates we intend to hit, and we tell you when they move.
FAQ
- Is versioning available today?
- No. Git-style versioning is on the Q4 2026 roadmap. The ELEMNT platform itself is live now, free during early access, and early-access testers get the versioning beta first.
- Will it work with my existing data?
- Versioning is designed around the same open formats the live platform already uses (PMTiles and GeoParquet), so your data stays portable. COG and Zarr support follow on the roadmap.
- Do I have to change my frontend?
- No. ELEMNT is MapLibre-compatible. Versioning is a data-layer and backend capability, so your existing map frontend keeps working.
- What will it cost?
- ELEMNT is free during early access. Public pricing is not published yet; when it is, it will be on this site first.
Be first to test versioning.
Join the early-access list. Versioning testers hear from us before the public Q4 2026 release.