Why We Built
AuraBoot
A self-hosted app platform for teams that need to keep control of their data, runtime, and business logic.
Our Vision
Most business systems repeat the same foundation: data models, forms, permissions, approvals, audit logs, imports, notifications, and a few custom rules that make the project real. We built AuraBoot because we were tired of rebuilding that foundation from scratch.
The product is built around a DSL-driven runtime: describe the model, commands, pages, and workflows; write code only when configuration stops being the right tool. AI is available where it helps with querying, workflow assistance, or knowledge retrieval, but the data and runtime stay under your control.
Our source-available Community edition means teams can inspect the platform, self-host business applications, and contribute improvements. We build AuraBoot in the open because transparency and community collaboration produce better software for everyone.
Milestones
Our journey from idea to source-available platform.
Project Inception
AuraBoot started from repeated project work: forms, permissions, workflows, audit, and plugins kept coming back.
Core DSL Engine Complete
The DSL engine became the main contract for models, commands, pages, permissions, and runtime metadata.
Plugin Examples and E2E Coverage
First-party plugin packages and E2E coverage helped turn the runtime into something teams can inspect and extend.
Community Release
AuraBoot was released with source-available Community terms so self-hosted teams can evaluate the platform directly.
Source-Available Commitment
AuraBoot Community is source-available under AuraBoot License Agreement v1.3. It stays free for self-hosted internal apps, customer-owned delivery, and vertical business SaaS, while commercial licenses cover white-label rights, official support, and enterprise terms.