FAQ
Common questions
This page answers the questions teams ask most often when they first meet Nexma — what it is, how one platform can serve many domains, how the agent works, where data lives, and how it deploys. Each answer links to the page that covers the topic in depth.
What is Nexma?
Nexma is an AI-native spatial operating system — a horizontal platform for spatial decisions. You describe what you want in plain language, and Jax operates a live world model the way an engineer operates a codebase: reading and writing the DataStore, reasoning against the active Ontology, and calling the engines when it needs to compute. The interface is conversation; the output is real, auditable changes to your project.
How is it domain-agnostic?
Domain knowledge is data, not code. An Ontology defines the entity types, relationships, and constraints for a domain; a Skill reconfigures Jax to work that domain. Load a different Ontology and Skill and you get a different application — fiber, water, electric, defense, logistics — with zero code changes. Jax always acts through the same eight generic primitives, so the agent never carries domain-specific tools; the meaning lives in the world model.
Fiber was the first vertical. The platform is built so the next one is a Skill, not a rewrite.
What is Jax?
Jax is the spatial intelligence agent. It is not a chatbot on a map — it is an agent that works the world model directly. Every read and write lands in the DataStore, every action is one of eight known primitives, and every step is visible on a timeline you can replay and question. Ask it "why" and it explains its reasoning grounded in the actual run. See Jax.
What are the engines?
Jax calls specialized engines when a question crosses from "look it up" into "compute it." The MathEngine optimizes, the GeoEngine runs spatial analysis, the InsightEngine perceives imagery and video, and the SatelliteEngine tasks fresh imagery. The glossary lists the full set.
Who owns the data?
You do. Your world model, projects, and feeds belong to your organization, scoped within your tenancy and never shared across org boundaries. Every change is attributed and audited, and you can export your data. Access is governed by the same permission engine for people and agents alike — Jax can never exceed the authority of the person who invoked it.
Can it run on-premise or air-gapped?
Yes. Nexma is built for environments where data cannot leave the perimeter, including on-premise and air-gapped deployments. The world model, the engines, and the agent run inside your boundary, and identity federates through your own provider. Talk to us about your environment for specifics.
How do Skills work?
A project binds one Ontology plus one or more Skills. The Ontology is the typed world model; a Skill targets it with capabilities, a system prompt, and validators. Skills are swappable per project, and the Ontology can be extended mid-project — add a constraint and every surface reacts at once. Browse and fork Skills in the workspace library.
How does it integrate with our systems?
Through the SyncEngine for connecting external systems and feeds. A programmatic API for driving Nexma from your own code, CI, or external systems — including webhooks for detections, jobs, and feed updates — is in preview; contact the team for early access.
What about the field?
Nexma Mobile brings the same project world model to iOS and Android — offline-first, voice-and-vision native, with on-device Jax for crews, inspectors, and surveyors. Designs flow out, evidence flows back, and the desktop Globe updates in real time.
What does pricing look like?
Nexma is sold as an enterprise platform, scoped to your organization, deployment model, and the engines and capabilities you use. There is no single list price; engagements are shaped around your domains and scale. Contact us to discuss your use case.
Where to go next
- Overview — the full picture in one page.
- Quickstart — get from zero to a working project.
- Jax — the agent at the center of the platform.
- Glossary — every canonical term defined.