Ontology
The Typed World Model
Define entities, relationships, and constraints once — then every map layer, panel, validator, and the agent tool is generated from it. Load a new ontology, get a new application, with zero code changes.
What Is an Ontology
A Typed Model of Your World
An ontology defines what exists and how it connects: entity types (the nouns), typed relationships (the edges between them), and the constraints that bind them. Define it once and every map layer, panel, validator, and agent tool is generated from it. The graph below is one example — select a node to inspect its properties and connections.
OLT → Cabinet → Closure → Home. Every relationship is typed and constrained.
Example ontology — entities, typed relationships, and constraints.
Legacy Challenges
Why Hardcoded Software Can't Keep Up
When the data model is buried in code, every new entity type or rule means an engineering project. The schema, the map, the forms, and the logic all drift apart — and adding a domain means rebuilding the app.
Schema Locked in Code
Entity types and rules live scattered across the codebase, so changing the model is a release cycle — not a configuration change.
Core Capabilities
One Model, Every Surface Generated
The Ontology is the single typed definition of your world. Define it once and the platform generates the application around it.
Type everything that exists
Declare entity types and their properties — closures, valves, transformers, waypoints, sensors — with the fields and units that matter to your domain.
Product Benefits
Define the World, Not the Software
Describe your domain once and the platform builds around it — so new entities, rules, and even whole domains are configuration, not engineering.
One source of meaning
Every surface — map, tables, forms, and the agent — reads the same typed model, so the world means the same thing everywhere with no drift.
New domains without new code
Load a different ontology and the application reconfigures — entities, layers, and tools — turning a fiber tool into a water tool with no rewrite.
Evolve the model mid-project
Add a field, type, or rule and every surface adapts instantly, so the platform grows with your understanding of the domain.
Feature Details
A Schema That Builds the Application
The Ontology types every object in your world and generates the surfaces and tools that operate on it.
Entity Types
Declare the things that exist in your domain with typed properties, units, and tiers — the vocabulary of your world.
Link Types
Type the relationships between entities so structure and topology are first-class, not implied.
Constraints
Capture engineering and regulatory rules as constraints the model enforces automatically.
Related Products
Explore the Spatial AI OS
One platform for all spatial data and workloads, from design to field operations.
FAQ
Get the Facts About the Ontology
Read the DocsIt is the typed world model at the center of Nexma — the single definition of the entities, relationships, and constraints in your domain. Every map layer, panel, validator, and the agent tool is generated from it, so the application is built from the model rather than hardcoded.
Because the domain lives in the ontology, not in code. Load an ontology for fiber, water, electric, or defense and the toolbar, layers, and tools reconfigure to match — the same platform becomes a different application with no rewrite.
Yes. Add an entity type, property, relationship, or constraint mid-project and every surface adapts instantly — no migration and no redeploy.
The agent reasons against the ontology, so it understands the world as typed entities and relationships with real constraints — not as anonymous points and lines. That grounding is what makes its actions valid and explainable.