Product

Stop rebuilding the same Java backend on every project.

Generate a delivery-grade module package instead: backend, admin pages, permissions, OpenAPI annotations and tests in one flow — code your team can review, merge, own and upgrade. Let Codex, Cursor and Claude Code do the work inside rules that keep the result shippable.

What it solves

The work a CRUD generator usually leaves behind.

Project setup

Every project rebuilds the same backend, permissions, file handling and deployment.

A running base in minutes, and a business module in well under an hour.

AI that stays in bounds

AI-generated code drifts, misnames things and skips permissions.

Module boundaries and rules that the AI tools read and follow.

Delivery, not just CRUD

Generated CRUD still ships without tests, permissions or audit.

Generation includes permissions, menus, OpenAPI and tests.

A UI that isn't a template

Default Element Plus admins all look the same.

A redesigned theme, and generated pages that follow the design system.

Consistent code

A small team plus AI struggles to keep big-team code discipline.

Standards and review checklists that run in the generator and CI.

Deployment

Going from dev to production always needs improvised scripts.

Docker, config templates, object storage and ops docs are included.

Security

Code that runs is not the same as code that passes a security review.

Default-deny access, secrets kept out of logs, revocable tokens and an SBOM.

Upgrades

Customized forks drift from upstream and get harder to upgrade.

Module manifests, migrations and an upgrade assistant keep your fork upgradeable.

Capabilities

Eight reasons teams build on StackRivet.

From a database table to the delivery package around it, with the engineering you'd otherwise build by hand.

01

AI guardrails

Machine-readable rules for Cursor, Codex and Claude Code. Each module states its boundaries, permissions and test requirements, and the generator produces context AI tools can follow.

02

Governed code generation

From one table: backend, frontend, permission seed, OpenAPI annotations, test samples and module context. You get a merge-ready delivery package, not loose snippets.

03

Upgradeable customization

Module manifests, versioned migrations and versioned generator templates, plus a breaking-change list. Pro adds upgrade-assistant basics and customization-diff scanning; Enterprise adds upgrade PRs.

04

Asset Service for object storage

Community supports Local, S3-compatible and Aliyun OSS storage, private signed downloads, metadata and MIME checks, and download authorization. Upload routing follows /assets/capabilities: Local and OSS use quota-enforced server transit; S3 can advertise Content-Length-bound direct and multipart paths. Additional storage work is Roadmap or explicit contract scope.

05

Enterprise delivery kit

A private-deployment SOP, a delivery checklist, a security baseline, an SBOM, backup and restore notes, and an ops checklist.

06

Reliability baseline

Modular-monolith boundaries, default-deny security, traceId, Actuator, Micrometer, an optional OpenTelemetry profile, dependency scanning and a clear high-concurrency path.

07

Redesigned Element Plus

StackRivet design tokens and runtime overrides replace the default blue, the 4px radius and the template shadows, so the admin doesn't look like a stock template.

08

Engineering governance

Layering, code standards and test gates are written as rules and enforced in CI with ArchUnit, Maven Enforcer, ESLint and Playwright.

What you get

A complete engineering base, not just a starter.

AreaIncluded
Backend Spring Boot modular monolith, Spring Security, MyBatis-Plus, Flyway
Frontend Vue 3, TypeScript, Vite, Element Plus with StackRivet design-system overrides
Access control RBAC, menu / button / API permissions, basic data permissions
Code generation Entity, Mapper, Service, Controller, DTO/VO, frontend page, OpenAPI, tests
Asset Service Local/S3/OSS, private signed downloads, capability-routed uploads
Observability traceId, Actuator, Micrometer, optional OpenTelemetry profile
AI engineering AI-readable rules, module boundaries and generated context
Governance Architecture standards, review checklist, ArchUnit / CI gates
Delivery Docker Compose, Dev Container, CLI doctor, SBOM and release checklist
Who it's for

Teams shipping real Java systems.

  • Java teams starting new business systems.
  • Software companies and outsourcing teams delivering many similar projects.
  • Enterprise IT teams standardizing Spring Boot and Vue applications.
  • Developers using Codex, Cursor or Claude Code on production Java projects.
Get started

Start with a base your team can trust.

Generate governed modules, and let AI work inside clear architecture, security and testing rules.