AuraBoot
Start free
English简体中文

Architecture overview

This is the top-down map of AuraBoot: the whole product as a small number of layers, plus a cross-cutting axis. Read it once and the rest of the docs have a place to hang. For the interactive version of this map — click any capability to jump to its docs or a live example — see the architecture map.

The one idea underneath everything: one declarative DSL is compiled into every surface — tables, a REST API, web pages, mobile, workflows, and permissions. You describe; the platform produces.

The four layers

AuraBoot stacks four layers, from the kernel that keeps it safe up to the verticals that run in production.

L0 · Kernel runtime — the contract

The platform contract, not plugins. This is why the system stays governable, AI-safe, and upgradable as it scales to dozens of plugins and hundreds of commands.

  • Command pipeline — the single write contract; every write (browser, mobile, API, automation, or agent) runs the same ordered stages, ending in audit and events.
  • Permissions — five layers (RBAC + ReBAC
    • org scope + ABAC + field-level), evaluated against the tenant member.
  • Plugin manifest & profiles — plugin contributions merge into named profiles; the platform is plugin-delivered, not a monolith.
  • Multi-tenancy, audit/events, control-plane vs. business-plane, and storage (PostgreSQL + pgvector / Redis) — all covered in the deep system overview.

L1 · Platform capabilities — build with

The horizontal capabilities you compose apps from.

  • Designers: Page, Dashboard, Report, BPMN, Flow, and the Query Builder.
  • Process & automation: BPM workflows and automation rules — every rule issues a command.
  • AI, native: AuraBot is the unified NL/agent runtime (its skills include model creation, field add, query, ChatBI charts, and dashboard generation); the agent runtime adds tool registry, MCP tools, and durable workflows; RAG / knowledge grounds answers with pgvector retrieval.
  • The same Page schema renders native on mobile.

L2 · Business modules — reusable packs

Reusable business building blocks delivered as plugins — CRM, sales, finance, procurement, inventory, quality, project, HR, asset, knowledge base. Start from a pack and adjust it. See the use cases.

L3 · Industry solutions — the proof

Complete vertical products we build on AuraBoot ourselves — the strongest proof the platform handles real complexity: AuraQuote + BOM, the Crawler platform, IoT / AMOS + manufacturing, smart manufacturing / PCBA, and more.

The cross-cutting axis (⊥)

Some concerns are not a layer — they thread vertically through L0–L3: observability (logs, traces, per-stage metrics), the CLI & tooling, operations (deploy, HA, env promotion, backup/DR, upgrade, secrets), and security & identity.

Enterprise is a tier, not a layer

A few capabilities — Marketplace + entitlement, the Agent Control Plane, Observability Pro, multi-region — ship only with the commercial distribution. They are extensions of the architecture above, marked as a tier, not a layer stacked on top. The OSS distribution is fully self-sufficient for single-region production.

Where to go next