Public Preview · Self-hosted · Source-available

Declare to build,command to govern.

Build fast. Change safely.

AuraBoot is an AI-native enterprise application runtime for complex business. Models, pages and processes are declaration-driven; every business write — from people, automation, or AI — passes through one permission, validation and audit path.

Run locally in 5 min See the product loop

Runs on your infrastructure
Source-available
Community license

workspace / sales / lead-intake · full loop from declaration to audit

● localpreview

01Declare

versioned DSL

models/lead.jsonpages/leads.json

{

"modelCode": "crm_lead",

"name:zh-CN": "销售线索",

"fields": [

{ "code": "company",

"dataType": "string",

"required": true },

{ "code": "stage",

"dataType": "enum",

"dictCode": "lead_stage" }

}

// command: crm:create_lead (risk: medium · auditable)

ready for reviewgit · diff · promote

02Operate

designer + runtime

Northstar CRM

Sales workspaceLM

Leads

18 new this week · 9 to follow up

AllMineTo follow up

客户阶段负责人更新

ACAcme Cloud已联系林默10:42

NSNova Steel新线索陈一09:18

OSOrbit Systems已联系林默昨天

HLHelio Labs新线索周然昨天

AuraBot is ready to run crm:create_lead Customer, owner and next step identified; submitting still enters the same command boundary.

03Govern

command trace

crm:create_lead

actoraura-agent

riskmedium

tenantnorthstar

idempotencyenabled

permission

3 ms

schema validate

2 ms

state guard

1 ms

handler

18 ms

audit + event

5 ms

Audit record#CMD-24F8A

resultcompleted

changedcrm_lead / 1 record

sourceAI agent

Declarations are the source　versioned, reviewable, promotable.

The UI is a view of the same contract　designer and code never fork the truth.

Commands are the only write boundary　people, processes, APIs and AI all leave a trace.

Design principles

Not more features — fewer bypasses.

AuraBoot collapses complexity into three stable principles: declarations define the system, commands constrain change, plugins carry delivery. When AI enters, it gets no special channel.

01 / DECLARE

Declarations are the source.

Models, pages and processes are expressed as versioned contracts. The visual designer edits that same truth — not a hidden second format.

version · diff · review · promote

02 / GOVERN

Commands are the boundary.

Business writes are expressed as commands, then pass authorization, validation, state guard, execution, audit and events in order. Governance is not scattered across every button and endpoint.

one write contract

03 / DELIVER

Plugins are delivery.

Industry capability contributes models, commands, pages, permissions and processes as plugins. Customization need not live as long-term patches on the trunk.

capability as a package

AI / SAME RULES

AI is no
exception.

AI on the same rails

What it can call is decided by the command contract; what it did still passes permission and audit.

Adoption path

Developers run it first, teams adopt it together.

Start with a local environment, DSL and plugins; when business teams join, the designer, permissions, processes and audit still land in the same runtime model.

Developers get controllocal first

Source, declarations, API, CLI and plugins are all at hand. Verify the runtime first, then decide how the team adopts.

~/auraboot

$ git clone https://github.com/AuraBootTeam/auraboot.git

$ cd auraboot

$ docker compose --profile full up --build -d

# PostgreSQL · Spring Boot · React

Git diffPlugin SDKAPILocal debug

Teams get a shared languagesame runtime

Business users change pages and processes in the designer; engineers still review contracts, set boundaries and trace every change.

Two ways of working, one runtime model.

Proof, not promises

Real products, built on AuraBoot

We don't just sell the platform — we build complex products on it. These are real, golden-tested systems running on the same stack you'd self-host.

No anonymous logos. Each entry shows a real interface and states its status, scope and the AuraBoot capabilities it uses.

QUOTING · BOM

AuraQuote + BOM standardization

A PCBA quoting flow that standardizes messy customer BOMs, reviews material candidates, counts process work, and exports quote-ready Excel from one governed command pipeline.

Read the case →

DATA · CRAWLER

Crawler data platform

A governed crawl operations product that turns jobs, frontier URLs, extracted documents, artifacts, lineage, quality checks, session / lease state, and usage cost / SLO signals into one auditable platform workflow.

Read the case →

Choose the right shape

Not every app needs AuraBoot.

We state the boundary up front: it serves long-lived, operationally complex systems that need governance and are ready to let AI execute business actions.

A better fit for systems that…

Span multiple business domains

Quoting, orders, procurement, fulfillment and traceability cross several domains.

Need more than a role table

Record-level, org-level, attribute-level or field-level governance and traceability.

Need AI to act, not just answer

Agents must safely call business operations under the same rules.

Productize industry capability long-term

Deliver as plugins instead of maintaining a pile of customer patches.

Pick another tool when…

You just need a departmental form

When commands, audit and layered permissions are unused, a lightweight builder is more direct.

You want to swap in a mature accounting or payroll suite

Country compliance and packaged-suite depth are not something a runtime replaces on day one.

Audit and traceability are not requirements

For a throwaway internal tool, learning the governance contract may not be worth it.

Runtime architecture

Every entry point returns to one contract.

UI, automation, external integrations and AI share one command boundary; models, pages, permissions, processes and plugins are the platform first-class citizens.

Model

Page

Command

Permission

Process

Plugin

Your infrastructure / your data boundary

Automation

API / Webhook

AI Agent

↓

COMMAND CONTRACT

permission

validation

state guard

audit

event

RuntimeModel · Page · Process Command · Permission

Plugin deliverymanifest · dependency upgrade boundary

PostgreSQL

Your integrations

self-hostedsource-availabledata stays in your environment

Start with evidence

Run it locally first, then decide whether to adopt.

Spin up the community edition with Docker Compose and see for yourself whether declarations, pages, commands and audit fit your system.

Open the 5-min quick start View source

quickstart.sh

$ git clone https://github.com/AuraBootTeam/auraboot.git

$ cd auraboot

$ docker compose --profile full up --build -d

# open http://localhost:3000