OGC-native, multi-tenant geospatial catalog platform. Manage trillions of features across isolated tenants and expose them through every major OGC API standard.
Traditional catalog systems trade interoperability for tenancy or scale for flexibility. AIP collapses the trade-off: each catalog you create maps to a physically isolated PostgreSQL schema (zero data leakage, rename without data movement), and every catalog is exposed through STAC, OGC API – Features, Coverages, Tiles, Maps, Processes, Records, EDR, and DGGS without writing extension code per format.
docker compose -f packages/core/src/dynastore/docker/dev.compose.yml up -d
curl http://localhost/stac/catalogs
open http://localhost/web/The running service declares OGC conformance live at /stac/conformance, /features/conformance, /processes/conformance, /records/conformance, /coverages/conformance, /dggs/conformance, /consys/conformance, /movingfeatures/conformance, and the maps service at /{tiles,maps,styles}/conformance.
Three pillars. Modules are backend-agnostic libraries — one module owns one table, no HTTP. Extensions are stateless HTTP adapters that translate requests into module calls — adding a new OGC API standard is adding an extension, not refactoring the core. Tasks are isolated background workers exposed through OGC API – Processes — ingestion, indexing, and analysis run in their own containers.
The catalog → schema → partition mapping is lazy: a code like "agriculture" resolves to an immutable schema like "s_a1b2c3", partitions are created just-in-time by database triggers on first insert, and renaming a logical code never moves a byte of data.
Documentation is layered: this README is the entry point, docs/ holds
high-level concept and reference pages, and each module/extension keeps a
detailed README.md next to its code. The full navigable map — every topic
linked to its concept page, its code-adjacent README, and its source directory —
lives in docs/index.md.
- Getting Started — run it locally and make a first request
- Documentation Index — the complete map of all docs
- Platform Manual — operator-facing tour
- Architecture Overview — the three-pillar design
- The Database Layer · Migrations
- The Query Executor Pattern
- Protocols & Discovery · Configuration · Caching
- Distributed Tasks
- Collection Lifecycle · Collection Metadata
- OGC API – Features · STAC API · Records
- Coverages · EDR · DGGS
- Tiles · Maps · Styles
- 3D GeoVolumes · Joins · Moving Features · Connected Systems
- Legacy WFS · OGC extension map
- Catalog Module · Items Schema · Field Types
- Storage Drivers · Platform Engines · Sidecar Configs · Schema Evolution
- Elasticsearch Integration · STAC Harvest
- Asynchronous Task Ecosystem · Processes · Events