Put any coding agent
to work on your operation.
Claude Code, Codex, OpenCode or Navica's own agent work your organisation's requests. Every change is proven in its own test installation and approved by a person before it ships.
01import { defineOntology } from '@navica-ai/sdk';02 03export const operations = defineOntology(04 ({ nodeType, relation, string, date, enumOf }) => {05 const project = nodeType('project', {06 name: string().role('identity'),07 dueDate: date(),08 status: enumOf(['active', 'complete']),09 });10 11 const team = nodeType('team', {12 name: string().role('identity'),13 });14 15 relation('deliveredBy', project, team);16 },17);Keep the context.
Build on top of it.
Declare the objects and relationships once. Use that shared model across queries, interfaces, agents and actions. Extend an existing product or build a new application for your own operation.
From code to running software
Declare what your software works with.
Types, properties and relationships capture the structure of your domain, once.
1import { defineOntology } from '@navica-ai/sdk';2 3export const purchasing = defineOntology(4 ({ nodeType, relation, string, date, enumOf }) => {5 const supplier = nodeType('supplier', {6 name: string().role('identity'),7 });8 9 const part = nodeType('part', {10 name: string().role('identity'),11 });12 13 const order = nodeType('purchaseOrder', {14 number: string().role('identity'),15 dueDate: date(),16 status: enumOf(['awaiting', 'approved']),17 });18 19 relation('placedWith', order, supplier);20 relation('orders', order, part);21 },22);Requests in. Proven software out.
A codebase bound to your organisation's requests. Agents pick up the work, Navica's browser captures the proof, and the same build that passed review is the one that is released.
Requests1
- R-231Show depot on each vehicle
Building1
- R-226Add a filter to the fleet mapCodex
In QA1
- R-219Fix dates in the rota exportOpenCodeTests failing
Ready for review2
- R-214Export inspections to CSVClaude Code
- R-208Supplier scorecardNavica agentReview waiting
Released1
- R-201Shift handover formClaude Code
One command. The whole operation in context.
Run the Navica MCP server next to your agent. It can read the live model of your operation straight away; anything that writes waits for an approval grant.
- Claude Code
- Codex
- OpenCode
- Navica agent
- Any MCP client
$ navica mcp serve
navica_query read
navica_show read
navica_tail read
navica_app write · approval grant
navica_act write · approval grant
› navica_query part where stock is below minimum
3 rows · Bin B-07 first
› navica_show purchaseOrder PO-30882
linked: supplier, budget line, 3 quotes
› navica_act raise reorder for Bin B-07
held · waiting for the stores manager
From operational
need to application.
Use Navica to build the tools that sit between your existing systems: project readiness, service coordination, resource planning and more.
See the application workflowYour product.
More connected.
Bring context-aware AI and connected workflows into the software your customers already use. Discuss the integration and deployment model with our team.
Discuss a software partnershipOne model underneath. Every kind of application.
Finance, stock, rosters, berths, batches and work orders are all views and actions on a model of the work. Every panel here is an application for a demo organisation.
The application development workflow
Access, domain modelling, compilation and deployment.Developer onboarding
Request SDK packages and a provisioned starter project.Bring your domain.
Build with Navica.
Talk through your data, application and deployment requirements with our team.
Book a demosales@navica.ai