×
close

Self-hosted Spatial Workflow Engine
for regulated operations.

Deploy on-prem or private cloud

Deploy on-prem or private cloud

Docker/Kubernetes ready
API-first

API-first: REST + GraphQL + OGC

Learn more
Terragnos Core Engine

API-First Architecture.
PostGIS-Powered.

See how easy to implement Terragnos into your application

core capabilities

Core capabilities for spatial operations

Workflow Engine

Workflow Engine

Jira-style state machines for assets and work orders—with automation and audit.

Schema Registry

Schema Registry

Versioned object types (JSON Schema/Zod), safe migrations, compatibility checks.

Query & OGC API

Query & OGC API

REST + GraphQL + OGC-style feature layers. GeoJSON/NDJSON, filters, time-travel reads.

Audit & Compliance

Audit & Compliance

Bitemporal history + hash-chain event log. Exportable proof bundles for audits.

Deployment anywhere

Bring Your Own Auth. Bring Your Own DB.

Run Terragnos next to your PostgreSQL/PostGIS and integrate with your IdP—no vendor lock-in.

PostgreSQL 15 + PostGIS
Works with Auth0 / Azure AD / Keycloak
Redis compatible
Host anywhere
PostgreSQL 15 + PostGIS
Works with Auth0 / Azure AD / Keycloak
Redis compatible
Host anywhere
trust & compliance

Built for environments
where every change must be explainable.

Time-travel

Query data as-of any point in time.

Tamper-evident audit logs

Cryptographic verification for every change.

platform capabilities

Enterprise-Ready Features
for Complex Spatial Workflows

architecture

Hexagonal Architecture
Built for Enterprise Scale

01 [ step ]

Domain Layer

Core business logic with clean interfaces. Object types, workflows, and rules defined as domain services with port-adapter boundaries.

02 [ step ]

API Layer

REST and GraphQL endpoints with versioning, OpenAPI documentation, and SDK generation for TypeScript, Python, and C#.

03 [ step ]

Infrastructure

PostgreSQL + PostGIS database adapter, event bus integration, and pluggable authentication providers.

04 [ step ]

Deployment

BYODB model: deploy on your infrastructure. Docker containers, Kubernetes-ready, on-premise or cloud.

01 [ step ]

Domain Layer

Core business logic with clean interfaces. Object types, workflows, and rules defined as domain services with port-adapter boundaries.

02 [ step ]

API Layer

REST and GraphQL endpoints with versioning, OpenAPI documentation, and SDK generation for TypeScript, Python, and C#.

03 [ step ]

Infrastructure

PostgreSQL + PostGIS database adapter, event bus integration, and pluggable authentication providers.

04 [ step ]

Deployment

BYODB model: deploy on your infrastructure. Docker containers, Kubernetes-ready, on-premise or cloud.

Quote

We're onboarding a small number of teams to validate real workflows (field ops, utilities, infrastructure).

Testimonial background
early access

Design partners wanted

Become a design partner
FAQ
faq

Frequently Asked Questions
About Terragnos Core Engine

Terragnos Core Engine is a self-hosted spatial workflow engine for regulated operations. It provides versioned object types, state machines, and audit trails for assets and work orders. The platform runs on your PostgreSQL + PostGIS cluster with BYOA (Bring Your Own Auth) and BYODB (Bring Your Own Database) deployment models.

Yes. Terragnos Core Engine follows a BYODB model: you own the PostgreSQL + PostGIS cluster, and we provide the application layer. Deploy on-premise, in your private cloud, or any environment where you have database access. Docker containers and Kubernetes configurations are included. You own the cluster.

Terragnos Core Engine uses a BYOA (Bring Your Own Auth) architecture. You implement an AuthProvider interface that validates tokens and maps identities to tenants. The platform supports multi-tenancy with row-level security (RLS) policies, and includes a Policy Decision Point (PDP) module for RBAC and ABAC rules. Default adapters are provided for common identity providers as reference implementations.

The platform provides REST APIs (versioned with /v1, /v2) and GraphQL endpoints. OpenAPI specifications are generated for all REST endpoints, and SDKs are automatically generated for TypeScript, Python, and C#. The platform also supports OGC API Features-compliant layer services for integration with mapping applications, and includes webhook subscriptions for event-driven integrations.
Explore More
partners

Our trusted collaborators in progress and success

Partner
Partner
Partner
Partner
Partner
Partner
Partner
Partner
Partner
Partner
Partner
Partner