Interoperability
Open formats and integration
Nexma is an operating system, not a walled garden. It speaks open spatial formats, exposes everything through APIs, connects to the systems you already run, and lets your data round-trip without lock-in.
Core concepts
The DataStore is the single source of truth, but it is deliberately built on open foundations so it never becomes a trap.
- Open formats. Spatial data is stored and exchanged as GeoJSON and other standard formats. Geometry is geometry — there is no proprietary container you have to escape from.
- Everything is a file. Because the world model is a filesystem, exporting it is reading files, and importing is writing them. There is no opaque internal representation between you and your data.
- APIs over the whole platform. The HTTP API exposes projects, the DataStore, the ontology, and Jax itself, so anything the UI can do, a program can do.
- Connectors via SyncEngine. The Nexma SyncEngine discovers and ingests external data sources — enterprise systems, telemetry, public and geospatial feeds — straight into the store.
How it works
Data moves into Nexma through connectors, lives in the store in open formats, and moves back out through the same formats and APIs.
1 EXTERNAL SYSTEMS NEXMA OUT
2 ┌────────────────┐ ┌──────────────┐ ┌──────────────┐
3 │ SAP · Salesforce├──Sync──▶│ │──API──▶│ BI · GIS · │
4 │ Warehouses │ Engine │ DataStore │ │ data science │
5 │ PostGIS · OSM ├────────▶│ (GeoJSON, │──Geo──▶│ Shapefile · │
6 │ Satellite · Web │ │ open files) │ JSON │ GeoJSON · │
7 │ Telemetry feeds ├──Event──▶│ │ │ exports │
8 └────────────────┘ Broker └──────────────┘ └──────────────┘- Ingest. Batch and reference data arrive through the SyncEngine; high-frequency telemetry streams through the Event Broker into the DataBase.
- Operate. Inside the store, every object is typed by the Ontology and edited by humans and Jax alike.
- Export and round-trip. Read any layer back out as GeoJSON or another standard format, push results to a warehouse, or call the API to drive Nexma from your own systems.
Connecting your stack
Nexma is designed to sit alongside the data infrastructure you already operate, not replace it on day one.
| Category | Examples | How it connects |
|---|---|---|
| Enterprise systems | SAP, Salesforce, data warehouses | SyncEngine connectors |
| Geospatial sources | OpenStreetMap, PostGIS, satellite imagery | SyncEngine + SatelliteEngine |
| Live telemetry | Flights, vessels, sensors, devices | Event Broker → DataBase |
| Programmatic access | Your apps and scripts | HTTP API + MCP |
The agent reaches external context through the same generic primitives it uses for everything else, plus an MCP surface for tool-to-tool integration.
No lock-in
Lock-in is a design failure, not a retention strategy. Nexma avoids it structurally:
- Your data stays yours. It is stored in open formats and exportable at any time, in bulk, through the API.
- Round-trip without loss. Import from your GIS, work in Nexma, and export back — geometry and attributes survive the trip because they were never converted into a closed format.
- Standards, not adapters. Because the foundation is GeoJSON and open files, integration is a matter of standard tooling, not bespoke adapters that rot.
If you can read a file and call an HTTP endpoint, you can get every byte of your world model out of Nexma. That is the contract.
Where to go next
- See the ingest layer: SyncEngine and Event Broker.
- Drive Nexma programmatically: API reference.
- Understand the open foundation: Nexma DataStore.
- Choose where it all runs: Supported platforms.