The Sovereign Platform.

The substrate

One substrate. Many verticals.

The verticals

Vertical operations, live today.

The module registry

All 67 department modules.

Not a category count — the actual registry, module by module, exactly as the engine enumerates it. Sixty-seven department surfaces across nine editions, each inheriting the same 31 shared engine capabilities, one permission tree and one agent.

Every one of these is a real surface with its own map, its own seeded operational data, its own configurable KPI dashboard, and the same ask-the-map agent scoped to whoever opened it. Turn any of them on or off per client from the admin console.

Cartos Grid · Electric Utility Edition

Connects to the systems utilities already run.

Cartos Grid ships with a real connector-adapter framework that lets any department surface draw live data from the utility's own systems-of-record. An operator pastes an endpoint and credentials into Admin → Integrations; the connector goes live on the next sync — no schema change, no redeploy.

Honest scope: Esri UN is proven against a live ArcGIS service today. OMS/ADMS, Maximo, SAP, P6, and MS Project run realistic mock feeds pending live credentials from the utility. Each connector requires only a trait implementation and one dispatch arm to go live — no new infrastructure.

Cartos Sentry · Crisis-Monitoring Edition

The platform's first autonomous loop.

Sentry is the reactive half. It introduced the engine's first background ingestion daemon: a monitoring watchlist whose enabled rows are auto-processed on an interval, searching satellite catalogues, running real change detectors across three independent modalities, and fusing a confidence band that is earned rather than generated. A hard guard means a degraded model raises nothing at all — the failure mode is silence, never a fabricated incident.

Sovereign administration

Nine editions, configured from one console.

Every Cartos deployment is configured per client through a layered admin model backed by Keycloak identity. A Cartos super-admin grants which editions a tenant is licensed for and deploys modules across them; then three per-client tiers take over — Modules (Provider Admin), Features (Tech Admin), and Users & Teams (User Admin). Everything below is the running console, captured today.

Access · editions licensed to a tenant

Access — grant editions, then deploy modules

All nine industries licensed to one tenant, each with its deployed-module count. Below it, the cross-deployment table: a module has a default industry but can be deployed into others — so Cartos Field can be added to Sentry, or Harvest’s crop surfaces served inside Cartos Africa.

Access · cross-industry deployment

One module, many industries

Harvest’s seven agriculture surfaces are deployed into both Harvest and Cartos Africa — the same module, two editions, one codebase. This is the edition model doing the thing that makes it worth having.

Provider Admin · Modules

Provider Admin — modules per deployment

69 of 71 modules enabled here. Each row carries its vertical, minimum licence tier and default feature count; disabling one hides it from the launcher and disables its agent tools. The registry is the 67 department surfaces plus Cartos Field and the GIQ / Energy / Agriculture integration modules.

Tech Admin · Features

Tech Admin — features, cross-pollinated

Each module’s default features, then a global advanced pool — Live Weather, KPI Dashboard, Layer Catalog, Navigate & Coordinates, Gaussian Splats, Field Captures — that a Tech Admin can cross-add into any module. Build a capability once; reuse it in all 67 surfaces.

Integrations · systems of record

Seven connectors, honestly labelled

Esri Utility Network, OMS/ADMS and File/CSV run against live endpoints; Maximo, SAP PM, Primavera P6 and MS Project run mock feeds until the client provisions credentials. The console says which is which rather than pretending.

Layer Catalog · datasources

Layer Catalog — every datasource type

COG, XYZ raster, GeoJSON URL and internal PostGIS side by side, each connection-tested from the console. Credentials are write-only — entered once, never returned to a client.

Data Sources · 82 external feeds

82 external sources, scoped per module

OpenAQ, Open-Meteo, GDACS, NASA FIRMS, USGS, OpenSky, AISHub and more — grouped by theme, licence-tagged (open / open* / paid / both), individually testable, and assignable per edition and module with per-user overrides.

Data Sources · connection tests

Pass / fail, not wishful thinking

GEBCO, EMODnet, GBIF, GeoNames, OpenAddresses and Foursquare reporting a green Pass; OneGeology and Mapillary flagged where a key or endpoint still needs attention. A per-user override can grant or deny any single source.

Africa Registry · geography-keyed sources

Africa Registry — the licence verdict is the gate

66 candidate sources keyed by geography and minimum zoom, so the best licensed layer surfaces as an operator narrows scope. Sources marked avoid are never offered, and a proxy source is withheld until it has a backing datasource. The rule is enforced in code, not in a policy document.

User Admin · Users & Teams

User Admin — self-service users, teams & module access

Create users, assign roles and teams, reset passwords — through the Keycloak Admin API, in-app. The module-access grid grants an individual user exactly the surfaces they need, across every edition, as the fourth enforcement gate alongside nav, feature panels and the agent’s own tools.

Project Access · portfolio & per-project

Project Access — default-deny, down to one project

For Milepost and Blueprint, grant the whole portfolio or a single project to a department, agency, team or individual, with an access level. Here: City Planning holds portfolio-wide admin, while a restricted user gets view on I-465 Reconstruction alone.

Identity is Keycloak-backed and federation-ready — a sovereign IdP a client can run in-territory, designed to federate upstream to the client’s own identity provider when a sovereign onboarding calls for it.

cartos · identity — sovereign IdP

Inside the platform

Capabilities every module inherits.