AI-native enterprise application runtime — model-driven, command-governed, plugin-delivered
Quick Start • Features • Architecture • Docs • Demo • Trust • Feedback • Community
AuraBoot is a runtime layer for complex, long-lived enterprise applications. It is not a CRUD builder, and it is not a packaged ERP — it sits underneath both.
You declare your business in six first-class concepts: Model, Page, Command, Permission, Process, Plugin. The platform turns those declarations into the database schema, the REST API, the rendered UI, the audit log, and — when the operation declares its risk and idempotency — a surface that AI agents can call safely.
| You are choosing between... | Pick this if... | Limit |
|---|---|---|
| A visual data-app builder | You need a department tool by Friday and a database UI is the goal | Cross-module governance, AI-safe operations, long-lived industry verticals |
| A packaged business suite | You want a working ERP/CRM out of the box and your processes fit its defaults | Deep non-standard processes, custom verticals, runtime-level AI execution |
| AuraBoot | The business is complex, the lifecycle is years, and operations must be governed and AI-callable | Higher learning curve than a pure form builder; not a same-quarter accounting replacement |
Full positioning rationale: auraboot.com/docs/positioning. Architecture: ARCHITECTURE.md.
- Model — entities, fields, relations; drives schema, APIs, default pages
- Page — DSL composition of blocks; business CRUD is contract-rendered, never hand-coded
- Command — the only write path; multi-stage pipeline applies authz, entitlement, validation, state guard, audit, events, side effects
- Permission — five layers: RBAC + ReBAC + organizational scope + ABAC + field-level
- Process — BPMN 2.0 long-running orchestration where each task resolves back to a Command
- Plugin — declared manifest of contributions; industry verticals ship as plugin packages with isolated resources and declared dependencies
| Dashboard | Page Designer |
|---|---|
 |
 |
| Command Pipeline | AuraBot Trace |
|---|---|
 |
 |
- Website walkthrough: auraboot.com/demo shows the core model -> page -> command loop.
- PCBA Pilot package: the PCBA manufacturing package is available for scoped design-partner pilots. It is not GA and should not be described as a full ERP replacement.
- Trust posture: auraboot.com/trust documents the current source-available license posture, security contact, and SOC 2 readiness position. AuraBoot does not claim SOC 2 Type I or Type II certification today.
Define models, fields, commands, pages, and formulas in declarative JSON. A single model definition creates the database table, REST endpoints, form validation, and list/detail pages with no code generation step.
Every data operation flows through a unified pipeline: schema validation → permission check → state machine → field mapping → handler → side effects → webhooks → audit. Fully configurable per command through DSL.
- Page Designer — Drag-and-drop page builder with 20+ block types (forms, tables, charts, dashboards)
- BPMN Designer — Visual workflow editor with human tasks, SLA monitoring, and approval routing
- Automation Designer — Event-driven automation rules with triggers, conditions, and actions
- AuraBot — In-app AI assistant for natural language queries, data operations, and guided workflows
- Agent Control Plane (ACP) — Orchestrate AI agents with skills, tools, and memory
- ChatBI — Ask questions about your data in natural language, get charts and tables back
- RAG Knowledge Base — Upload documents (PDF, DOCX, MD, CSV), vector-indexed for AI retrieval
- Multi-LLM — OpenAI, Anthropic, Zhipu GLM, MiniMax, and more through a unified provider interface
SmartEngine-based BPMN 2.0 engine with visual process design, human task assignment, approval inbox, escalation rules, and SLA tracking.
PF4J-based plugin architecture. The OSS repo ships ~20 first-party plugins covering CRM, HR, BPM, asset management, AI / agent control plane, dashboards, and more. Plugins are declarative JSON packages that add models, fields, commands, pages, and menus. Install from a marketplace or build your own with the CLI.
Row-level tenant isolation, role-based access control at resource/operation/data levels, and a complete permission system with menus, routes, and API-level enforcement.
Multi-channel notifications (email, in-app, webhook), event bus for cross-module communication, and webhook dispatch for external integrations.
git clone https://github.com/AuraBootTeam/auraboot.git
cd auraboot
docker compose --profile full up --build -d # 2–4 min cold start
./scripts/quickstart.sh # creates the admin, imports the pluginsThe full profile starts PostgreSQL + the Spring Boot backend + the Node BFF/SSR frontend. Cold start takes 2–4 minutes (the backend health check has a 120s start period).
scripts/quickstart.sh is not optional. docker compose up starts the services and nothing else: it creates no admin user and imports no plugins. Without this step the login below fails with "Invalid username or password", and even past it the platform has zero models and zero menus. The script is idempotent — run it again any time.
Windows: the runtime is fully supported through Docker Desktop, which runs the whole stack in its WSL2 backend —
docker compose --profile full upworks exactly as above. The only caveat is thatquickstart.sh(and every otherscripts/*.sh) is a bash script, so run it from a WSL shell or Git Bash, not PowerShell/cmd. It needs onlybash+curland talks to the published port, so./scripts/quickstart.shworks unchanged. Native, non-Docker Windows-host deployment is not supported: the reset/init/build tooling is bash-only and there is nogradlew.bat.
Then open http://localhost:3000 and log in:
admin@auraboot.com |
|
| Password | Test2026x (change immediately on first login) |
You should land on a platform with ~41 models and ~109 menus, including a CRM (crm_lead, crm_account, crm_opportunity, …).
If local PostgreSQL is already using port 5432, keep your local service running and start AuraBoot with a different host port:
POSTGRES_PORT=15432 docker compose --profile full up --build -dTo just run AuraBoot without building from source, pull the prebuilt multi-arch images instead — you need only docker-compose.pull.yml + scripts/quickstart.sh (no git clone; postgres schema and backend plugins are baked into the images). Mainland-China users can pull from the Tencent TCR mirror by setting REGISTRY=ccr.ccs.tencentyun.com/auraboot-oss. See DEPLOY.md → Pull-only deployment.
Prerequisites: Java 21+, Node.js 20+, PostgreSQL 15+ (Docker stack ships 16), Redis 7+, pnpm 9+
Start local services first — oss-reset-and-init.sh connects to local PostgreSQL and Redis. Brew/apt-installed services do not auto-start:
| OS | Command |
|---|---|
| macOS (Homebrew) | brew services start postgresql@16 redis |
| Linux (systemd) | sudo systemctl start postgresql redis |
| Windows | See the installation guide |
The script preflights both endpoints and aborts with a clear message if either is unreachable.
The oss-reset-and-init.sh script handles everything: DB reset, backend startup, /api/bootstrap/setup, frontend startup, plugin import, and storage state generation. Use this for a clean, working environment.
git clone https://github.com/AuraBootTeam/auraboot.git
cd auraboot
./scripts/oss-reset-and-init.shWhen the script exits successfully, the system is fully bootstrapped and both backend (http://localhost:6443) and frontend (http://localhost:5173) are running in the background (logs at /tmp/aura-backend.log, /tmp/aura-web.log, /tmp/aura-bff.log).
Use this when you need to inspect a single layer in isolation — e.g. to attach a debugger to the backend or rebuild plugins without restarting the dev session.
# 1. Reset DB only — backend + frontend stay stopped, /setup wizard handles bootstrap
./scripts/oss-reset-and-init.sh --no-bootstrap
# 2. Start the backend (Spring Boot, port 6443) in a dedicated terminal
cd platform
./gradlew bootRun
# 3. Start the frontend (Vite + BFF, port 5173) in another terminal
cd web-admin
pnpm install
pnpm dev:full
# 4. Open http://localhost:5173/setup in a browser to drive the bootstrap wizardpnpm dev:full is the default foreground developer entrypoint. If you need the frontend in background mode, run pnpm sync-plugins once and then start pnpm dev:web and pnpm dev:bff separately.
# Backend baseline tests
cd platform
./gradlew test
# AI runtime regression tests (AuraBot / Agent / RAG / Intent)
./gradlew testAi
# Frontend E2E smoke
cd ../web-admin
NO_PROXY=localhost npx playwright testIf you are working on AI features, run both test and testAi. The AI stack lives in core, but its regression suite is split into a dedicated Gradle task so it can run with a heavier test profile without slowing every default backend run.
| Layer | Technology |
|---|---|
| Language | Java 21, TypeScript |
| Backend | Spring Boot 3.5, MyBatis-Plus, PF4J |
| Frontend | React 19, Tailwind CSS 4, React Router 7, Vite 6 |
| Database | PostgreSQL 15+ (with pgvector) |
| Cache | Redis 7+ |
| BPM | SmartEngine 3.7 (BPMN 2.0) |
| AI | Multi-provider LLM integration (OpenAI, Anthropic, Zhipu, etc.) |
| Testing | JUnit 5, Playwright, JaCoCo |
| Observability | OpenTelemetry, Sentry, structured logging |
| Deployment | Docker, Docker Compose |
┌─────────────────────────────────────────────────────────────────┐
│ Frontend (React) │
│ Page Designer │ BPMN Designer │ Automation Designer │ AuraBot │
└──────────────────────────┬──────────────────────────────────────┘
│ BFF (Express)
┌──────────────────────────▼──────────────────────────────────────┐
│ Spring Boot Backend │
│ │
│ ┌─────────────┐ ┌──────────────┐ ┌────────────────────────┐ │
│ │ DSL Engine │ │ AI Core │ │ BPM Engine │ │
│ │ Model │ │ AuraBot │ │ SmartEngine (BPMN) │ │
│ │ Field │ │ ACP │ │ Human Tasks │ │
│ │ Command │ │ ChatBI │ │ SLA Monitoring │ │
│ │ Page │ │ RAG / KB │ │ Approval Inbox │ │
│ │ Formula │ │ Multi-LLM │ │ │ │
│ └──────┬──────┘ └──────────────┘ └────────────────────────┘ │
│ │ │
│ ┌──────▼──────────────────────────────────────────────────┐ │
│ │ 20+ Stage Command Pipeline │ │
│ │ LOAD → VALIDATE → PERMISSION → STATE → LOCK → HANDLER │ │
│ │ → EFFECT → SIDE_EFFECT → WEBHOOK → AUDIT → COMPLETED │ │
│ └─────────────────────────────────────────────────────────┘ │
│ │ │
│ ┌──────▼──────┐ ┌──────────────┐ ┌────────────────────────┐ │
│ │ Plugin FW │ │ RBAC │ │ Notification │ │
│ │ (PF4J) │ │ Multi-Tenant│ │ Email/Webhook/In-App │ │
│ └─────────────┘ └──────────────┘ └────────────────────────┘ │
└──────────────────────────┬──────────────────────────────────────┘
│
┌────────────▼────────────┐
│ PostgreSQL │ Redis │
└─────────────────────────┘
auraboot/
├── platform/ # Spring Boot backend
│ └── src/
│ ├── main/java/ # Application source
│ └── test/java/ # Integration tests
├── web-admin/ # React frontend + BFF
│ ├── app/ # Application source
│ └── tests/ # E2E and API tests
├── plugins/ # Plugin packages (~20 first-party in OSS repo)
│ ├── crm/ # CRM plugin
│ ├── sales/ # Sales management
│ ├── procurement/ # Procurement
│ └── ...
├── docs/ # Code-coupled fixtures only; user docs at auraboot.com/docs
├── scripts/ # Build, seed, and CI scripts
├── docker/ # Docker configuration
└── docker-compose.yml # One-command infrastructure
Full user documentation lives at auraboot.com/docs — getting started, core concepts, guides, use cases & industry solutions, API reference, plugin development, and deployment.
This repository intentionally keeps no docs/ tree beyond code-coupled test
fixtures; the documentation site is the single source of truth for user-facing
docs. A high-level system overview lives in ARCHITECTURE.md.
| Capability | Community (Free) | Enterprise |
|---|---|---|
| DSL Engine + Page Designer | ✓ | ✓ |
| 20+ Stage Command Pipeline | ✓ | ✓ |
| AI Copilot (AuraBot) | ✓ | ✓ |
| BPM Workflow Engine | ✓ | ✓ |
| Plugin System + CLI | ✓ | ✓ |
| Multi-Tenant RBAC | ✓ | ✓ |
| Agent Orchestration (ACP) | — | ✓ |
| IM (Real-time Messaging) | — | ✓ |
| CRM / ERP Plugin Suite | — | ✓ |
| Mobile Apps (iOS + Android) | — | ✓ |
| Priority Support + SLA | — | ✓ |
For enterprise licensing, use the AuraBoot contact form.
- Website feedback form — Product feedback, beta issues, licensing questions, and private notes
- GitHub Discussions — Ask questions and share ideas
- GitHub Issues — Report bugs or request features
- Discord — Community chat only; use the website form for feedback that needs follow-up
We welcome contributions of all kinds — bug fixes, features, documentation, and plugin development. See CONTRIBUTING.md for the development setup, coding standards, and PR process.
To report a security vulnerability, please email security@auraboot.com. Do not open a public issue. See SECURITY.md for our full security policy.
AuraBoot is released under the AuraBoot License v1.3, a source-available license based on Apache 2.0 with supplementary terms:
- Free for internal use — Use, modify, and deploy for your own business applications. No obligation to open-source your modifications.
- Free for ISV / project delivery — Build and deliver business applications (ERP, CRM, vertical SaaS) to customers, with your changes kept private.
- Attribution required — Retain copyright notices, license notices, and AuraBoot brand information.
- Platform restriction — You may not offer AuraBoot itself as a hosted low-code / no-code / AI platform service without a commercial license.
📖 See the License FAQ (中文) / License FAQ (English) for common questions about commercial use, modification, redistribution, and SaaS boundaries.
For commercial licensing (multi-tenant low-code SaaS, white-labeling, or removing branding), use the AuraBoot contact form.
Built with care by the AuraBoot Team