Community business applications keep attribution. Standard adds white-label rights; partners license their end customers, and OEM operators receive a product-scoped quote.
Commercial offer · Community License v3 draft
Commercial rights take effect through a signed order. Community v3 remains a draft for an expressly identified release; use the license bundled with your release. Review the actual software and delivery scope.
More community foundations, fewer adoption barriers
Multi-tenancy, AI/RAG, permissions, auditing and extension mechanisms are available in the community source. Check the capability guide for release boundaries and independently delivered products.
Change your logo, theme and business configuration. Community retains its specified attribution; white-label permission removes it.
Original business code can stay private
Copyright, license and NOTICE remain
Independently authored frontends follow the defined UI scope
Customer-owned business delivery
Register white-label authorization to each final customer. The customer can use the designer for its own internal systems.
¥999/year or ¥3,000 perpetual per customer
No separate designer upgrade surcharge
More internal apps for the same customer do not add a platform fee
Industry products and platform protection
Operate attributed industry SaaS under Community terms; white-label product operation follows an OEM agreement.
Quote the operator and named product
Scope, scale and service costs are explicit
No general-purpose competing development platform
What would your project pay?
One company's internal quotation system
Community with attribution, or Standard at ¥999/year / ¥3,000 perpetual for white-label permission.
An ISV delivers to three companies
Three perpetual customer licenses: 3 × ¥3,000 = ¥9,000. The partner may include this in its project quotation.
The same customer adds another internal application
No second platform license fee for the same entity and internal-use scope; extra implementation is a separate service.
An industry SaaS serves 200 subscribers
An OEM quote covers the operator and named product. Each subscriber is not automatically charged ¥3,000.
A current annual customer chooses perpetual
Credit the active year's ¥999 software fee against ¥3,000 and pay ¥2,001. No accumulation of past years.
A public low-code or AI application builder
AuraBoot-derived competing development platforms are prohibited under every ordinary offer, including OEM.
OEM operation
A quote for the product you operate.
Agree the named industry product, operating rights, scale, term, updates and support. No fixed entry fee or tenant quota is assumed, and individual subscribers do not automatically need their own Standard purchase.
Modules and services follow an explicit delivery list.
Commercial authorization does not bundle every enterprise feature. Confirm proprietary modules, versions, deployment, implementation, migration and support before ordering.
RMB offer for mainland China. Users, internal apps and records have no license metering; capacity depends on the deployment. OEM scope and service terms are agreed in the order.
Capability / right
Community
Standard
ISV customer
OEM product
Licensing scope
Internal business applications
Private business code and customization
White-label / remove platform attribution
—
Customer-owned business delivery
With attribution
—
Named customer
As contracted
Customer's internal designer
With attribution
Domain settings; internal development as contracted
Public vertical business SaaS
With attribution
—
—
Named product
Competing low-code / AI development platform
—
—
—
—
Remove copyright / license / NOTICE
—
—
—
—
Community source capabilities
Models, commands and page foundations
Multi-tenant isolation foundations
Roles, data permissions and basic auditing
Plugin and component extension mechanisms
AI and RAG source with your model key
Automation and integration foundations
Approval, native clients and industry packages
Check each product's release
Only the listed modules
Only the listed modules
Only the listed modules
Source availability is not release acceptance
Check the capability guide
Version and delivery list
Version and delivery list
Version and delivery list
Billing and delivery
License price
Free
¥999/year or ¥3,000 perpetual
Same price per named customer
Product-scoped custom quote
License unit
Attributed use
One legal entity
End customer; partner may purchase
Operator and named product
Users, internal applications and records
No license metering
No license metering
Within the customer scope
Scale agreed in the order
Development, production and backup nodes
No separate license fee
No separate license fee
No separate license fee
Deployment scope agreed
Perpetual renewal
Community terms
Optional; use continues
Same for perpetual customers
Term and exit agreed
Annual to perpetual upgrade
—
Active annual fee credited; pay ¥2,001
Same per customer
As contracted
Commercial updates and modules
Not included
First year; listed modules only
Customer order scope
Product order scope
Implementation, migration and premium SLA
Separate service
Separate service
Separate service
Separately priced
Frequently asked questions
What is the difference between annual and perpetual?
Annual authorization provides white-label rights for twelve months. The perpetual option grants continuing white-label use for the named entity without mandatory renewal. Both have the same internal-use scope; commercial modules, upgrades and services must be listed in the order.
What happens if I do not renew?
A perpetual customer keeps acquired rights and community-core branding permission. An annual customer can renew, buy the perpetual license, or restore community attribution during a thirty-day transition. We do not automatically stop the business or delete data. OEM duration and exit are explicitly contracted.
Can an annual customer switch to perpetual?
During the paid current authorization year, the RMB 999 software fee is credited once against RMB 3,000: pay RMB 2,001. Past years and services do not accumulate as credits. Three annual payments do not automatically create a perpetual license.
Can Community use my logo and private business code?
Yes. Customize the main logo, theme, fields, pages, commands and plugins, and keep your original business code private. AuraBoot-derived interfaces retain the specified visible attribution. Commercial permission removes that attribution; source copyright, license and NOTICE obligations remain.
Does my ISV customer need a separate designer upgrade?
No separate runtime-to-designer surcharge applies to a Standard customer authorization. Register the license to the final customer; that customer may configure its own internal business applications. The partner may purchase on its behalf. A retained-attribution Community delivery remains free within Community terms.
How are multiple customers and applications counted?
Each white-label end-customer entity receives its own authorization. Adding another internal application for the same licensed entity does not add another platform fee. Employees, technical tenants, test environments and backups are not separate customer licenses. Group entities and partner volume arrangements are identified in the order.
When do I need an OEM quote?
When operating a named industry product under your brand for multiple subscribing customers. The operator and product receive a scoped commercial agreement; each subscriber is not automatically billed RMB 3,000. Product rights, scale, term, updates and service costs are agreed separately, without a fixed entry fee or tenant quota.
Can I operate an attributed industry SaaS for free?
The proposed Community terms allow attributed business applications and attributed industry SaaS. White-label SaaS operation requires an OEM agreement. General-purpose platform hosting, arbitrary-app builders and competing development platforms remain prohibited even with attribution.
Can a paid license be used to build a competing platform?
No. Standard, ISV and ordinary OEM agreements do not permit selling, distributing or publicly hosting an AuraBoot-derived general-purpose low-code, no-code or AI application-development platform. Independent software using no AuraBoot code and concrete industry business applications are outside that prohibition.
Are all enterprise features and implementation included?
No. The current delivery list names the actual proprietary modules and versions. OIDC/OAuth, LDAP, native clients and industry packages follow their verified product scope. Installation assistance, migration, bespoke development and premium SLA are separate services. No unlimited consulting or response guarantee is implied.
Does more open source mean every capability is production-ready?
No. The capability guide separates community source mechanisms, independently delivered products and release verification. Multi-tenancy, AI/RAG and extension mechanisms can be inspected in the community repository; installation, full business journeys, capacity and product-specific claims still depend on release evidence.
Which terms apply when I purchase?
Prices describe this commercial offer. The Community License v3 text is a draft for an expressly identified release, and does not replace the license bundled with another release. Confirm the licensor, covered software, white-label scope, term, modules, support and tax details in a signed order before delivery.