Technical Architecture

PostGIS is the system
of record.

No separate GIS stack. No bolt-on maps. Geometry, tiles, features, realtime, spatial compute, and analytics all run on Postgres + PostGIS. This is the architectural decision that eliminates an entire category of cost and complexity.

Explore the stack Talk to engineers
The stack

One database. Every layer.

┌─────────────────────────────────────────────────────────────────┐
│ GovMap (React + MapLibre GL + deck.gl + MUI v5) │
│ 8 workspace modes · WCAG 2.2 AA · DIL offline cache │
├─────────────────────────────────────────────────────────────────┤
│ API Layer (REST + OGC API + WebSocket) │
│ OpenAPI 3.1 · AsyncAPI · RFC 7807 problem+json · Esri facades │
├──────────────────────┬────────────────────┬─────────────────────┤
│ COP Platform │ Foundation │ 9 Domains │
│ Incidents / ICS │ Taxonomy/Hierarchy │ Water · Energy │
│ Alerts · Dispatch │ Bitemporal (F2) │ SCADA · EV Fleet │
│ TAK/CoT · Symbology│ 3D/Z Geometry (F3) │ Workforce · Permits │
│ AI Analytics · AAR │ Topology/LRS (F4) │ ROW · Fed · Hazards │
│ 37 property tests │ 16 property tests │ 43 domain tests │
├──────────────────────┴────────────────────┴─────────────────────┤
│ pg_eventserv · pg_tileserv · pg_featureserv │
│ Fast* suite · pgRouting · PROJ · TimescaleDB · OPA │
├─────────────────────────────────────────────────────────────────┤
│ PostgreSQL 16 + PostGIS 3.4 (single system of record) │
│ Row-Level Security · UUIDv7 · geometry(…,4326) · timestamptz │
│ EXCLUDE constraints · GIST indexes · btree_gist │
└─────────────────────────────────────────────────────────────────┘

# Deploy: AWS EKS GovCloud · Docker · Helm · TLS 1.3/FIPS
# AI: local vLLM + Gemma inside the FedRAMP boundary
Principles

Design principles

Structural choices that keep GovAssetOS governable, testable, and resilient at scale.

Reuse Over Reinvention

Geometry in PostGIS. Tiles from pg_tileserv. Realtime from pg_eventserv. Spatial compute from Fast*/pgRouting/PROJ.

PostGIS pg_tileserv pg_featureserv pg_eventserv pgRouting PROJ

RLS Is the Isolation Boundary

Cross-tenant reads are structurally impossible at the database level — FORCE ROW LEVEL SECURITY on every table.

Tenant context setEnabled
FORCE ROW LEVEL SECURITYActive
Cross-tenant readBlocked

Pure Decision Logic

Correctness-critical rules are pure TypeScript modules — each covered by fast-check property tests.

Property test suite100+ runs
Shrinking enabledRunning
Pure decision modulesPass

Everything Command-Related Is Audited

C2 actions append to the hash-chained Audit_Log — every transition, denial, and CoT discard.

a3f9…incident.transitionallowed
b812…auth.deniedlogged
c04e…cot.discardchained

Degrade, Don't Fail

Dependency failures produce stale/degraded states with fallback — never a blank screen.

Source probeLive
Feed freshnessStale
Last-good payloadRetained

Open Standards First

OGC API Features/EDR. TAK/CoT. CAP. NIEM. Esri facades without forking investments.

OGCAPI Features
TAKCoT / CAP
NIEMFederation
EsriFacades
Proof

By the numbers

96
Property tests (COP + foundation + domains)
27
Integration tests (RLS + realtime + CoT)
14
Packages in the monorepo
85%+
Code coverage gate per package

Talk to our engineers

Deep-dive the architecture with the team that built it.

Request a Technical Session vs. Incumbents