Community capabilities and commercial scope
The community repository contains reusable foundations for business applications. Commercial authorization buys a defined branding, customer-delivery or operating scope. It does not automatically buy every industry product or every enterprise module.
What is available in the community source?
This inventory identifies source mechanisms, not a claim that every complete business journey or deployment size has been accepted.
| Foundation | Community source entry |
|---|---|
| Models and fields | MetaModelService |
| Governed business commands | CommandPipeline |
| Tenant isolation | MybatisPlusConfig |
| Data and field permissions | FieldPermissionService |
| RAG retrieval | RagRetrievalService |
| Plugin lifecycle and extension | PluginManagerService |
| Automation | AutomationService |
| Page blocks | BlockRegistry |
| Report designer | ReportDesigner |
| Dashboard designer | DashboardDesigner |
| Command audit records | CommandAuditLogService |
AI and RAG use the provider credentials and infrastructure you configure. Community source availability does not include paid model calls, hosted storage or our implementation labor.
Three useful evaluation journeys
- Tenant and permission isolation: establish two business spaces and ordinary users, confirm allowed records in each, and verify that crossing the space boundary does not expose the other customer's records, files or knowledge.
- Knowledge-grounded business questions: configure a knowledge base for your release, import your own material, ask a relevant question, inspect its evidence, and check that a user without access cannot retrieve it.
- A business extension: follow First Change, then extend a model, page or command through the plugin manifest. Save, reload and check permissions and the resulting business operation.
These are evaluation checklists. They do not certify an installation or replace the acceptance results for the release you deploy.
Customization and white-labeling are different
Community terms can permit private business code, custom fields, pages, commands, rules, components and plugins. The main customer logo and theme can be customized while the specified AuraBoot attribution remains.
Removing that attribution needs commercial white-label authorization. Source copyright, license and NOTICE obligations remain. An independently authored frontend does not become a copied AuraBoot UI merely because it calls a backend API; use the applicable license's defined scope.
Choose the business scope
| Use | Commercial entry |
|---|---|
| Attributed internal business systems and customer-owned delivery | Community terms |
| One entity's internal white-label systems | Standard: RMB 999/year or RMB 3,000 perpetual |
| ISV white-label delivery | Authorization registered to each end customer; the partner may purchase |
| Attributed industry SaaS | Permitted under the proposed Community v3 scope |
| White-label industry SaaS | Named operator and product; an OEM quotation |
| AuraBoot-derived public general-purpose development platform | Prohibited under ordinary offers |
Standard perpetual rights do not require renewal. Adding another internal application for the same licensed entity does not add another platform license fee. Commercial modules, upgrades, implementation and premium SLA are separately identified.
CRM, BPM, EDU, native clients and industry solutions have independent product and delivery boundaries. Do not infer that a complete product is installed merely because a platform integration or designer exists.
Read Pricing and the Community License v3 draft. The draft applies only after formal adoption for an expressly identified release. A deployed release's bundled license and a signed commercial order are the authoritative terms.
Begin with the actual release
Use the installation guide and quick start, including initialization. Confirm the version, selected application, required plugin resources and known limits before describing a capability as production-ready.
For a project quotation, share who owns the system, whether it is internal or operated for subscribers, whether white-labeling is needed, and which actual modules and services you need. Discuss a project.