Software should fit the operation.
Norbital lets teams build and run custom operational apps on one shared system for data, workflows, permissions, automations, and agents.
Why we started
We started Norbital in Singapore in 2024. We kept seeing the same problem: a business process would outgrow its software, then move into spreadsheets, chat threads, forms, and manual reports.
Adding another point tool did not solve the underlying issue. The team still had to copy data, reconcile status, and manage a second permission model. We built Norbital so each workflow can have the right screens without creating another isolated system.
How the product works
@norbital-ai/pod defines the workspace in TypeScript and Svelte. Builders author
collections, apps, hooks, automations, remote functions, and access policies. Core builds, versions, provisions, and runs that workspace.
Product principles
Source is the definition
Schema, policies, apps, and automations are reviewable, testable, and versioned source code.
Releases are controlled
Workspace Studio builds immutable Checkpoints. Builders test schema and app changes in preview before promoting a checkpoint to production. A failed build does not replace the live release.
One access model
Apps, automations, and agents use the same workspace policies. Adding a new interface does not create a separate set of permissions.
Screens match the job
Each team gets the forms, queues, dashboards, and actions required for its work. Users do not need to work directly with the underlying schema.