Community is generally available under Apache-2.0. Team and Enterprise work remains a design-partner pilot until its outcomes are proven and released.
Free
For developers and small teams starting real Java enterprise apps.
A real Apache-2.0 Community base you can use in commercial projects.
Start freePilot
For teams delivering multiple Java projects that want to move faster.
Validate the team workflow with us before a general release.
Apply for the pilotCustom
For organizations needing private deployment, governance and support.
Scope only the governance and delivery work your organization needs.
Request a solution review| Capability | Community | Team pilot | Enterprise pilot |
|---|---|---|---|
| Apache-2.0 Community base included | |||
| Spring Boot + Vue app base | |||
| RBAC, audit, OpenAPI | |||
| Governed single-table generation | |||
| Asset Service | Local/S3/OSS | Same base | Contract scope |
| Shared team templates + Git/PR delivery | — | Pilot | Contract scope |
| Multi-table/tree/master-detail | — | Roadmap | Contract scope |
| Upgrade compatibility report | — | Roadmap | Contract scope |
| SSO / MFA / LDAP | — | — | Contract scope |
| Tenant/compliance integration | — | — | Contract scope |
| Official support | Community | Pilot | Contract |
Most teams don't fail because they can't generate CRUD. They fail because every generated module still needs permissions, menus, tests, OpenAPI, audit logs, file security, deployment scripts and upgrade rules.
StackRivet's paid pilots focus on work that actually costs teams time: governed generation, object-storage integration, AI coding guardrails, upgradeable customization and scoped delivery.
We can help you evaluate whether StackRivet is worth adopting for new projects, and how to migrate existing modules without rewriting everything at once.
Yes. The Community edition is licensed under Apache-2.0 — a permissive, commercial-friendly license — so you can use it in real commercial projects, not a limited demo.
Community is the generally available product. The Team tier is currently a design-partner pilot for shared templates and reviewed Git/PR delivery; roadmap items are labeled and are not sold as shipped capabilities.
Enterprise is currently scoped per pilot. SSO, tenant, compliance, availability and support work is included only when it is named in the signed statement of work.
No. StackRivet is code-first. Generated code stays in your repository, can be tested, reviewed, modified and upgraded.
Not a simple replacement. RuoYi and JEECG are valuable in their own contexts. StackRivet focuses on AI guardrails, governed generation, object storage, upgradeable customization and enterprise delivery.
Community source is open. Team and Enterprise plugin delivery, private source hosting or source escrow exists only when a commercial contract explicitly includes it.
Community can be self-deployed by users. Official deployment, availability or environment-review work is available only when an Enterprise pilot contract names the environment, deliverables and acceptance criteria.
StackRivet uses an architecture path suited for growth: stateless services, capability-routed uploads, async tasks, pagination limits, index guidance, optional Redis and OpenTelemetry. Local and OSS uploads transit the server; S3 uses byte-bound direct or multipart upload only when the capabilities API advertises it. Final capacity depends on deployment, database, workload and tuning.
Talk to us when you need SSO, audit reports, private deployment support, high availability, migration assessment, procurement documents or SLA.
Use the generally available Community edition with your own Java stack. Apply to the Team or Enterprise pilot only when the labeled scope matches a real project.
