Headless CMS for geospatial content

The spatial backend built for the AI era.

A fully managed, AI-native platform for geospatial content. Your editors manage map data without code. Your developers deliver it through fast, cacheable APIs. AI automates the work in between.

One platform, three jobs

Editors, developers and AI agents work from the same source of truth.

For editors

Manage places and content without code

Add points, lines and areas on the map, then enrich them with text, images and files. Draft changes safely, then publish when ready.

For developers

Build map apps without a backend

A stable API, GeoJSON and vector tiles serve your published content straight to your apps. Nothing to run, and the data is always up to date.

For AI agents

Let agents work with your data

Agents can query your data and make edits through MCP. Every change lands as a draft for an editor to review.

[ image ] Screenshot: Type builder, a "Trailhead" type with its fields (name, difficulty, photos, location) and the type tree on the left
How it works

From raw data to live maps in four steps.

Start and model the data once: the kinds of places and the fields each one has. Editors add content by importing it or drawing on the map, then publish it for your apps to consume through a cacheable API and vector tiles. Put AI agents to work to query and edit your data, with every change landing as a draft for editors to review.

AI

An AI teammate for your map data.

Spatibase AI reads your data model, cleans and enriches entries, and answers questions about your places. You review the changes, then publish.

Spatibase AIWORKING
✦CategorizedTrails, campsites, viewpoints1,204
⌖GeocodedFrom street addresses96
✎Descriptions draftedIn your editorial tone214
⚑Duplicates flaggedWithin 25 m, similar names12
⇄TranslatedEN → DE, FR, ES642
✓Ready for reviewNothing is published automatically38
Ask your datavia MCP
Which campsites near water have no description?
Found 34 campsites within 500 m of water with an empty description. I drafted all of them from their location, type and nearby features.
34 drafts0 publishedReview changes →
Delivery API

Published content, ready to consume.

Cached, ETag-aware and CORS-enabled. Use JSON, GeoJSON or Mapbox vector tiles with the map library you already use.

  • JSON, GeoJSON and vector tiles
  • Draft and published are separate
  • Works with MapLibre, Mapbox, QGIS, ArcGIS
JSONGeoJSONVector tiles
GET/delivery/v1/projects/{id}/entries.geojson
200 OKETagcache HIT18 ms
{
  "type": "FeatureCollection",
  "features": [{
    "type": "Feature",
    "geometry": { "type": "Point",
      "coordinates": [-122.41, 37.77] },
    "properties": {
      "name": "Ocean Beach",
      "type": "beach"
    }
  }]
}
FAQ

Questions, answered.

What is Spatibase?

Spatibase is a headless CMS for geospatial content. Editors manage points, lines and areas on a map without code, and developers get a cacheable API that serves published content as JSON, GeoJSON and vector tiles, so they can build map apps without running a backend.

How is it different from a general headless CMS such as Strapi or Contentful?

Locations are first-class. Entries have real geometries, editors work on a map, and the platform publishes GeoJSON and vector tiles out of the box, instead of storing coordinates as plain text fields.

How is it different from a GIS or a map platform such as Mapbox or ArcGIS?

Spatibase manages the content behind your map: the places, their fields, media and the editorial workflow. You keep using the map library or GIS you already have, such as MapLibre, Mapbox GL or QGIS, to render it.

Do I need to build a backend for my map app?

No. Published content is served directly by the Delivery API, which is cacheable and always up to date, so your app reads the data without a server of its own.

Can AI agents edit my data?

Yes, through MCP. Agents can query your schema and content and propose edits. Every change lands as a draft for an editor to review, nothing is published automatically, and each change is recorded in the audit log.

Which formats can I import and deliver?

Import GeoJSON, CSV and TSV, and upload GPX and KML shapes. Deliver JSON, GeoJSON and Mapbox Vector Tiles with TileJSON.

Enterprise

Built for organizations.

Single sign-on, roles, audit logging and support to match how your team works. Run it managed, on dedicated infrastructure, or self-hosted in your own cloud.

Illustration of a rack-mounted server

Build your spatial backend

Start free, or talk to us about your organization.