Skip to content

When to use Kaiwu ​

Teams running several business applications can share a workbench, identity, roles, dictionaries and notifications. Each project owns its domain code, data and release schedule.

  • Ship product-built frontends without rewrites: Product managers and AI can build a persona-tested mock frontend first in kaiwu-web-starter, lock in rules and scenarios, and hand over via Git and project adopt so backend engineers wire real APIs in the exact same frontend repo. See product handoff.
  • Start a project: Initialize from starter or generate both repositories, then develop your first feature across equipment booking or order lists.
  • Govern multiple teams & environments: Configure project membership and SQL-enforced row scope, sync kaiwu/*.yml from Git, and transfer 6-file config snapshots across staging and production with 3-way diff preview.
  • Reuse enterprise plumbing safely: Adopt idempotent workbench tasks and leased jobs (services), prefix-scoped STS object storage and safe Excel I/O (files), plus first-install support for MySQL or Dameng DM8 (operations).
  • Develop with AI & expose guarded assistant actions: Give the coding agent repository paths, scope, checks and acceptance criteria (sample task), or expose permission-scoped reads and preview-before-write business actions in the project assistant.

Apache License 2.0