Norbital Documentation
Norbital is a configuration-first platform for building internal operations software. As a system configurator, you define the data model, access rules, interfaces, apps, and automations in one versioned blueprint instead of stitching together separate admin panels, APIs, and frontend code.
Read these docs as a configuration guide
The docs under /docs are written for the people who design and maintain a
Norbital workspace: operations leads, implementation teams, and internal platform owners.
What You Configure In Norbital
Everything flows through the Blueprint, which is the tenant-specific source of truth for your organization. In practice, that means one system describes:
- Collections for your business entities, fields, relationships, and labels.
- Routes for read and write behavior such as validation, export, and notifications.
- Permissions for which teams can access which routes, records, fields, apps, and pages.
- Interfaces for how records are viewed and edited.
- Apps and pages for department-facing dashboards and operational screens.
- Automations for scheduled or manual browser-driven jobs.
- Codeblocks and CEL for the small amount of logic that needs to be customized.
How Changes Go Live
Norbital does not treat configuration as a set of live inline edits. Structural work happens in a fork, where you stage changes against a cloned tenant database, review issues, and then merge back into production as a new checkpoint.
- Create or open a fork.
- Use Database Studio, app settings, or Commander to stage your changes.
- Review linting, validation, and any configuration issues.
- Merge the fork to create a new production checkpoint.
Saving is not the same as deploying
Saving a change in a fork updates staged configuration. Production schema and schedules are only
updated when that fork is merged.
How To Use These Docs
The documentation is grouped by the job you are trying to do:
- Getting Started explains the blueprint model, forks, and the first setup sequence.
- Data Modeling covers collections, Database Studio, and record interfaces.
- Route Configuration explains validation, exports, and notifications.
- Access Control covers route permissions, field redaction, and approvals.
- Codeblocks explains when to use CEL versus TypeScript and how Dynamic UI works.
- Apps, automations, tasks, and Commander cover the operational surfaces your users see.