A common model.
Your own software.

Start with the right project.

SDK packages and starter repositories currently require access. We provide the package configuration and an application starter for your environment as part of developer onboarding.

Declare what your application understands.

Define the objects and relationships in TypeScript. The example below connects projects to teams. Typed queries and evaluations build on the same foundation.

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);

Work in React and TypeScript.

A Navica application brings its declaration, React pages, generated data client and world model together. Keep the interface focused on the work while the model carries its context.

Adapt the page, extend the model and connect the actions your workflow requires. Use maintained UI components or compose your own interface.

Check it before you apply it.

After installing the dependencies and configuring access in the provisioned project, sign in to the target environment and compile the application.

npm install
navica login
navica app compile app.tsx

Compilation validates the application locally. Deployment is a separate, explicit step against your selected environment.

navica app deploy app.tsx --apply

Use the entrypoint from your application project. Review the target environment and deployment changes before applying a release.