Architecture

The whole product, one map

One declarative DSL, compiled into every surface. Four layers — from the kernel that keeps it safe up to the verticals we ship on it — plus the cross-cutting concerns that thread through all of them.

Architecture · one platformself-hosted
L3Industry solutionsVerticals
AuraQuote + BOMCrawler platformSmart mfg / PCBAAuraQR
L2Business modulesReusable packs
CRMSalesFinanceProcurement+6
L1Platform capabilitiesBuild with
Page DesignerDashboard DesignerReport DesignerBPMN Designer+10
L0Kernel runtimeThe contract
Command PipelineMetadata RegistryPermission engineMulti-tenancy+5
Cross-cutting

runs through every layer

ObservabilityCLI & toolingOperationsSecurity & identity

one declarative DSL tables · REST API · web · mobile · workflows · permissions

Layer by layer

From the foundation up. Every capability links to its explanation, how-to, or a live example.

L0

Kernel runtime

The contract

The platform contract (not plugins) — what makes it governable, AI-safe, upgradable.

Architects: why it stays honest at scale

Explore in the docs →
  • Command Pipeline — The single write contract — 10 ordered stages: authn→authz→entitlement→validate→…→execute→audit→events.
  • Metadata Registry — Live store of resolved Model/Field/Command/Page/Permission/Process.
  • Permission engine — Five layers: RBAC + ReBAC + org scope + ABAC + field-level.
  • Multi-tenancy — MetaContext carries (tenant, user, role); isolation at the principal, not the row.
  • Audit & events — Audit is a queryable artifact; events drive automation & inbox.
  • Control / business plane — Definitions vs operations split — governance, AI safety, upgrade safety.
  • Profile registration — Plugin contributions merge into named profiles; plugin-delivered, not monolith.
  • Plugin substrate — PF4J hosting, isolated classloaders, dependency ordering, manifest validation.
  • Storage — PostgreSQL (+pgvector) system of record; Redis operational tier.
L1

Platform capabilities

Build with

The horizontal capabilities you compose apps from.

Developers: what blocks do I have

Explore in the docs →
  • Page Designer — Drag list/form/detail/dashboard/workbench; 29 block types.
  • Dashboard Designer — Widgets, charts, metric strips bound to queries.
  • Report Designer — A4 report canvas with data tables + export.
  • BPMN Designer — Visual BPMN 2.0 processes.
  • Flow Designer — Node-based flows with a custom node registry.
  • Query Builder — Named queries reused across dashboards & reports.
  • Automation — Cron + event rules; every rule issues a command.
  • BPM (SmartEngine) — Embedded BPMN runtime; service tasks resolve to commands.
  • AuraBot (AI runtime) — Unified NL/agent runtime. Skills: create model, add field, query, ChatBI charts, generate dashboards.
  • Agent runtime — Tool registry, MCP tools, ACP durable workflows, guarded actions.
  • RAG / Knowledge — pgvector retrieval + knowledge bases for grounded answers.
  • Mobile runtime — Same Page schema renders native on iOS & Android.
  • IM / Inbox — Record-tied messaging, approvals, @AI, workflow inbox.
  • Plugin system — PF4J plugins add models/commands/pages/handlers.
L2

Business modules

Reusable packs

Reusable business building blocks, delivered as plugins.

Implementers: don't reinvent the wheel

Explore in the docs →
  • CRM — Leads, accounts, contacts, pipeline.
  • Sales — Orders, quotes, fulfillment.
  • Finance — Cost, billing, payment.
  • Procurement — Sourcing, purchase, supplier.
  • Inventory — Stock, warehouse, movement.
  • Quality — Inspection, CAPA, nonconformance.
  • Project — Tasks, milestones, Gantt.
  • HR — Org, employees, leave.
  • Asset — Equipment lifecycle & maintenance.
  • Knowledge base — RAG-backed docs & retrieval.
L3

Industry solutions

Verticals

Vertical products and flagship scenarios — the ones we build on AuraBoot ourselves.

Decision-makers: proof it can build complex products

Explore in the docs →
  • AuraQuote + BOM — Multi-level quoting & BOM standardization, all on models/commands/workbench pages.
  • Crawler platform — Governed crawl operations with frontier, evidence, QA, lineage, session/lease, and cost/SLO surfaces; flagship vertical.
  • Smart mfg / PCBA — PCB-assembly ERP: quoting, BOM, SMT production, quality, warehouse.
  • AuraQR — QR-driven field operations on the platform.

Cross-cutting

Runs through every layer

Concerns that aren't a layer — they cut down through L0–L3: observability, tooling, operations, governance.

Operators & platform teams: how you run and govern the whole stack

  • Observability — Structured logs, OpenTelemetry traces, per-command-stage metrics — built into the pipeline, not bolted on. (Observability Pro adds preconfigured dashboards + per-stage budgets.)
  • CLI & tooling — The aura CLI — status, import / directory-sync, scripted operations that span many modules.
  • Operations — Deploy · cluster / HA · env promotion · backup / DR · upgrade · secrets — the production lifecycle around any module.
  • Security & identity — Auth, secrets, security hardening, and the audit trail that every layer writes into.
  • Marketplace + Entitlementent — Productized plugin distribution; per-tenant entitlement enforced at the pipeline's entitlement stage.
  • Agent Control Planeent — Cross-tenant agent orchestration, audit replay, risk-graded approval gates, budget guards.
  • Multi-regionent — Active-active routing and cross-region failover for tenant data, processes, and audit.