Cartos Atlas5
Government
Smart City · Maritime · Emergency Services · Situational Awareness (3D) · Maritime Domain Awareness (3D)
Cartos · The Approach
Agentic. Enterprise. Agency. Solution-specific.
The geospatial market makes you pick one. A general-purpose GIS suite you must staff an entire department to operate. A point solution that answers one question and dead-ends. A consultancy build that is perfect on delivery day and orphaned by the next budget cycle. Cartos refuses the trade. One sovereign engine that is agent-native at the interface, enterprise-grade underneath, built for the way public agencies are actually held accountable — and delivered as purpose-built, solution-specific editions. One platform. Nine industries. 67 department modules. All nine editions are live, and four of them shipped in the last six weeks.
The scale of it
One platform. Nine industries. 67 modules.
Not eight products with a shared logo — one engine, one data fabric, one agent, one admin model, one login. Every number below is counted from the engine's own module registry, not from a slide.
1
Platform. One Rust core, one web shell, one agent, one permission tree.Everything else is configuration.
9
Industries live today, each on its own sovereign subdomain.Four of them shipped in the last six weeks.
67
Individual department modules across the nine editions.All 67 live today.
31
Shared engine capabilities every module inherits automatically.3D, analysis, compare, export, dashboards, field, agent…
Cartos Grid9
Electric utility
Grid Command · Network & Asset Ops · CIP & Major Projects · Storm Response · Fleet & Field · Vegetation · Real Estate · Environmental · Stakeholder
Cartos Tower10
Airport
Air Traffic · Surface Condition · Tarmac Lighting · Lane Striping · Signage · Property Lease · Major Projects · Emergency Services · Vehicle Traffic · Weather
Cartos Milepost10
Transportation · DOT
Executive Overview · Pavement · Facility · Lane Striping · Live Traffic · Roadwork · Major Projects · Crew Status · Snow Removal · Emergency Response
Cartos Blueprint9
Infrastructure delivery · AEC
Portfolio View · Design Status · Site Selection · Constructability · Environmental & Cultural · Inspections · Safety · Stakeholder & Access · Live Traffic
Cartos Africa9
Government · continental
Continental Command · Food & Agriculture · Health & Immunization · Border · Port · Land Use & Cover · Parcel Fabric · Flood & Climate Risk · Settlement
Cartos Guardian5
Critical-infrastructure protection
Command & Risk · Energy Infrastructure · Utilities & Transport · Emergency Services · Defense & Military
Cartos Sentry3
Crisis monitoring
Crisis Command · Change Detection · Incidents
Cartos Harvest7
Agriculture intelligence · live
Harvest Command · Crop Type & Land Use · Crop Health · Yield Forecast · Water & Drought · Field Boundaries & Registry · Risk & Finance
Sixty-seven modules is what a decade of separate procurements normally buys you — from nine vendors, on nine logins, over nine copies of your data. Here it is one deployment, one permission model, and one agent that can reason across all of it.
It reads what you already own
Agentic AI is only as good as what it can reach.
A geospatial agent that can only see its own database is a demo. Cartos was built to connect outward — into the enterprise systems that hold the authoritative record, into the open standards every mapping agency already publishes, and into the imagery supply chain from free archives up to same-day commercial tasking. Everything below is shipped and wired, not a roadmap.
Enterprise systems of record
Connector-adapter framework with per-tenant registration, scheduled sync and connection status.
esri_unEsri Utility Network — asset and network features synced into the operating picture.parcel_fabricEsri Parcel Fabric — the documented Parcel Fabric information model mapped into a source-agnostic, LADM-aligned (ISO 19152) cadastral store: spatial units, basic administrative units, rights/restrictions/responsibilities and parties. Human review survives re-sync.featureserverGeneric ArcGIS parcel service — a config-driven field map lands any cadastre FeatureServer in the same schema, so you can move between sources without a migration.oms_admsOMS / ADMS — live outage and switching state feeding outage KPIs and the storm map.maximoIBM Maximo — work orders synced with source-prefixed external references.sapSAP PM — plant-maintenance work orders on the same normalised model.p6Oracle Primavera P6 — capital projects, schedule, cost and status.msprojectMicrosoft Project — the same project fabric from an MS schedule.file_csvFile / CSV import — for the systems that will never have an API.
One row per connector per tenant, validated at the database, with a connected / configured / error state visible to the admin.
Geospatial services & open standards
Datasource types in the managed catalogue — added in-app, scoped by tenant, edition, module, group, role and user type.
arcgis-restEsri Feature & Map Services — ArcGIS REST endpoints, including secured ones, server-proxied.wmsOGC WMS — capabilities-probed and rendered as a styled layer.wmtsOGC WMTS — tiled map services, the mapping-agency default.xyz-rasterXYZ raster tiles — any slippy-tile template, including your own.geojson-urlGeoJSON endpoints — the universal exchange format.pmtilesPMTiles — range-read vector tiles direct from object storage.cogCloud-Optimized GeoTIFF — imagery and elevation read in place.flatgeobufFlatGeobuf — streaming vector at scale.postgisClient-hosted PostGIS — your own database, in your own territory.
Plus STAC catalogues, NASA GIBS, and Overture Maps places, transportation, buildings and divisions as first-class overlay kinds.
Imagery & earth observation
From free archive to same-day tasking, with the licence posture and the price on screen before you commit.
sentinelSentinel-1 SAR & Sentinel-2 optical — resolved live via Microsoft Planetary Computer STAC.landsatLandsat C2 L2 — including thermal bands for the heat and fire detectors.firmsVIIRS / FIRMS — active-fire detections with fire radiative power.umbraUmbra — SAR tasking to 0.25 m.capellaCapella Space — SAR tasking to 0.5 m.iceyeICEYE — SAR tasking to 0.25 m.maxarMaxar — optical tasking to 0.3 m.planetPlanet — optical tasking to 0.5 m.
Plus local and GeoTIFF upload for imagery you already hold, and an 82-source external registry — 49 live — spanning HDX, geoBoundaries, GADM, World Bank, UN Data, WorldPop, JRC GHSL, Kontur and national cadastres.
This is the part that makes the agent useful rather than impressive. When an analyst asks Cartos a question, the answer can draw on your Esri feature services, your Maximo work orders, your P6 schedule, your own PostGIS, the open continental base map, and this morning's Sentinel pass — inside one permission scope, with the sources named in the reply. Nobody has to export anything to a shapefile first.
The model
Four properties. Usually mutually exclusive.
Each of these is hard on its own. The reason they rarely coexist is architectural: bolting an agent onto a legacy suite doesn't make it agentic, and hand-building one agency's solution doesn't make it enterprise. Cartos was built the other way round — the hard parts once, in the engine, so every vertical inherits all four for free.
01 · Agentic
Ask, don't author
One AI analyst reasons across every datasource the asking user can see — discovers layers, filters, measures proximity, groups and counts, and says so when the data can't support the answer.
02 · Enterprise
One substrate, many owners
Tenant- and team-isolated data fabric, three-tier Keycloak admin, per-module and per-project access grants, a managed layer catalogue, and connectors into the systems of record you already run.
03 · Agency
Defensible in a hearing
Sovereign in-territory by default, licence posture enforced in code, scores decomposed into their components, confidence never fabricated, and every spend visible before it's committed.
04 · Solution-specific
A slice, not a fork
A vertical is a curated catalogue of department modules with its own theme, geography and data — running on the same engine. New editions ship in weeks, and every one of them upgrades all the others.
01 · Agentic
The map answers questions. It doesn't just display them.
Almost every GIS vendor now ships "AI." Nearly all of it is a chat box stapled to the side of a product that still requires you to know which layer to open, which field to query, and which projection to fight. Cartos is agent-native: the agent holds the same catalogue, the same scope, and the same access rules the map does, so asking it something is genuinely equivalent to doing it yourself — and materially faster.
The industry default
- A chat panel bolted on beside the map, with no access to the real layer catalogue.
- Answers that read confidently and cite nothing.
- An analyst still needed to translate the question into GIS operations.
- The assistant sees more than the user is cleared to see — or far less.
What Cartos does
- Cross-module agent tools —
catalog_layers,query_catalog_layer, scope filters — operating on the live catalogue, not a summary of it. - Attribute, proximity and group-by queries returned as tables and charts, with the layer and filter it used stated in the answer.
- Provenance stated plainly: OSM-derived reference data is labelled as reference data, not passed off as an official registry.
- Every query runs inside the asking user's tenant, team, module and role scope. Never outside it.
Proof — running product
02 · Enterprise
Built to be operated by an institution, not a hero analyst.
Enterprise isn't a logo on a pricing page — it's what happens on day 400, when the person who built the maps has moved on, four departments need different slices of the same truth, and procurement wants to know exactly who can see what. Cartos puts that model in the engine: a managed catalogue, a real permission tree, and adapters into the systems of record that already hold the authoritative data.
The industry default
- Layers configured by hand in project files, owned by whoever made them.
- Access controlled at the app door — everything or nothing once you're inside.
- A separate deployment, and a separate bill, for every department that wants a view.
- Integration as a services line item, re-quoted per system.
What Cartos does
- An admin-managed datasource and layer catalogue, scoped by tenant, edition, module, group, role and user type — configured in-app, not in a file share.
- Three-tier Keycloak-backed administration: provider, tech and user. Modules and features switch on per deployment.
- Per-project and portfolio grants that are default-deny and assignable to a department, agency, team or individual.
- A connector-adapter framework — Esri UN, OMS/ADMS, Maximo, SAP PM, P6, MS Project, file/CSV — so the platform reads the systems of record rather than replacing them.
Proof — running product
03 · Agency
Every number on the screen has to survive being questioned.
Commercial software can afford to be confidently wrong. A ministry, a defence command or a national mapping agency cannot. Agency-grade means the output has to withstand a hostile question from an auditor, a minister, or opposing counsel — so the system is built to show its work, refuse to invent certainty, keep the data inside the territory, and put a price on the screen before anyone commits to it.
The industry default
- A single risk number with no visible derivation.
- A model confidence percentage generated because the UI has a field for one.
- Data leaving the territory the moment it touches a cloud region.
- Licence terms discovered at audit, not enforced at render time.
- Tasking spend reconciled after the fact.
What Cartos does
- Scores decompose on screen into their components — criticality, exposure, category weight — each individually contestable.
- Confidence is a band (Low / Medium / High / Confirmed) earned by independent modalities agreeing. “Confirmed” is analyst-set only, and a degraded model raises nothing at all.
- Sovereign by construction: in-territory deployment, own tenant, own identity, data that never leaves.
- Licence verdict is a hard gate in code — avoid sources are never offered, view-only sources are server-proxied, and every layer carries its terms.
- Commercial tasking shows the cost before the order, and the running spend after it.
Proof — running product
04 · Solution-specific
A vertical is a catalogue away — and it makes every other vertical better.
This is the part that is genuinely hard to copy. A general platform can be configured into anything and is therefore good at nothing on day one. A bespoke build is excellent on day one and never improves. Cartos editions are curated slices of one engine: each ships with its own modules, theme, geography and seeded operational data — and every engine-level improvement lands in all nine at once.
The industry default
- A toolkit, plus a twelve-month systems-integration programme to make it a solution.
- Or a vertical product that can never become anything else.
- A fork per customer, and a maintenance burden that compounds with every one.
- Improvements that reach exactly one deployment.
What Cartos does
- Engine → editions → instances. The substrate, agent and shell are built once; an edition is a module catalogue with a theme and a geography.
- Nine live editions to date, spanning government, electric utility, airport, transportation, infrastructure delivery, a continent, critical-infrastructure protection, crisis monitoring and agriculture.
- Each edition licensable as its own sovereign instance — own tenant, own data, own identity, in-territory.
- Harvest reused Cartos Africa's country-scope and foundation-layer fabric outright instead of rebuilding it. That is the compounding, made concrete.
Proof — running product
The trade nobody else refuses
Why these four rarely coexist.
Shown as categories of approach rather than named vendors — the constraint is architectural, and it applies to whoever is currently occupying each category.
| Approach | Agentic | Enterprise | Agency | Solution-specific | Where it breaks |
|---|---|---|---|---|---|
| General-purpose GIS suite The incumbent desktop-and-server stack |
Bolted on | ✓ | Partial | ✗ | Powerful and generic. Becomes a solution only after a long integration programme, and needs a standing GIS department to stay useful. |
| Point solution One question, answered well |
Sometimes | ✗ | Partial | ✓ | Excellent at its one job. The second question needs a second vendor, a second contract and a second copy of your data. |
| Consultancy build Bespoke, delivered to spec |
✗ | Partial | ✓ | ✓ | Fits perfectly on delivery day. Improves only when funded again, and never benefits from anything built for anyone else. |
| Imagery / analytics API Pixels and detections as a service |
API-level | Partial | ✗ | ✗ | Sells inputs, not decisions. Someone still has to build the operating picture, the workflow and the accountability around it. |
| Cartos Engine → editions → sovereign instances |
✓ | ✓ | ✓ | ✓ | The hard parts are built once in the engine, so a new vertical is a catalogue and a theme — and every edition inherits every improvement. |
The honest version of this table: any one row can be beaten on its own axis by a specialist. What none of them can do is hold all four at once — because holding all four requires having built the engine before you built the solutions, and that decision can only be made at the start.
The receipts
Four editions. Six weeks. One engine.
The clearest evidence that the model works isn't an architecture diagram — it's the delivery rate. These four shipped consecutively, each reusing the last, all in mid-2026.
Cartos Africa
A continental government edition — Continental Command plus eight departments, all 54 African Union states with subnational scope, a foundation-layer fabric and 49 live external sources.
LIVE · africa.cartosatlas.comCartos Guardian
Critical-infrastructure protection with a transparent 0–100 strike-risk model over 103 curated UAE sites, five domains, live AIS/ADS-B and 3,538 features on one picture.
LIVE · guardian.cartosatlas.comCartos Sentry
The platform's first background monitoring daemon, real optical/SAR/thermal detectors, cross-modality confidence fusion, an incident state machine and cost-visible commercial tasking.
LIVE · sentry.cartosatlas.comCartos Harvest
STAC-native agriculture intelligence — crop classification, NDVI-anomaly health, yield proxies with uncertainty, field-boundary delineation and an agri-risk score with an insurance trigger.
LIVE · harvest.cartosatlas.comRead that cadence again. A continental mapping platform, a strike-risk model, an autonomous satellite-monitoring daemon and an agriculture-intelligence suite — four fundamentally different problem domains, shipped in nine days of each other, by the same engine. Guardian's risk score became Sentry's watchlist priority. Africa's data registry became Harvest's imagery resolver. Nothing was forked; everything compounded. That is the approach, and it is the only part of this that a competitor cannot buy.
What it means for you
You are not buying a map. You are buying the rate of change.
Your vertical already half-exists
Nine editions have already paid down the shared cost — data fabric, agent, symbology, dashboards, admin, field edge. Your edition starts from there, not from zero.
Day 400 looks better than day 1
Every engine-level improvement built for any edition lands in yours. You inherit work commissioned by other customers, in other industries, without paying for it.
Nothing leaves your territory
Sovereign by construction — your own instance, tenant, identity and data, deployed in-territory. Sovereignty is the default configuration, not an enterprise add-on.
The analyst shortage stops binding
Ask-the-map means a policy officer, a field supervisor or a minister's advisor can get an answer without a GIS specialist in the loop — and see exactly how it was derived.
Your outputs survive scrutiny
Decomposed scores, earned confidence bands, licence gating in code, and reports that trace back to the imagery and the run that produced them.
It reaches the ground
Cartos Field stands up offline-first, no-code mobile capture whose ground truth surfaces back inside every module and is queryable by the agent. See it →
Design partner program
The tenth edition is someone's industry. It could be yours.
We select a small number of design partners with a real, recurring geospatial need and sovereignty as a genuine constraint — and we build their edition on the engine, not beside it. Early access, roadmap influence, and auditable deliverables your stakeholders can defend. Cohorts are deliberately limited and engagements run under NDA.