Schema migrations

How the platform applies declarative app schemas while keeping data scoped to each tenant.

The platform applies schema.json from each revenexx App to your tables. It computes a safe diff, applies additive changes, and keeps your data scoped to its tenant automatically.

How it works

  1. Read the desired state from schema.json in the app repository.
  2. Compare it with the current schema.
  3. Generate the changes for additive and compatible edits.
  4. Apply them in a transaction and verify constraints.
  5. Refresh the generated API so it matches the new schema.

Default rules

  • Tenant boundaries are enforced automatically — your data is scoped to your tenant.
  • Schema is declarative, and git history is the migration history.
  • Unsafe destructive changes are blocked unless an explicit migration strategy exists.

Deploy flow

Bash
git push origin main
# 1) CI validates manifest.json and schema.json
# 2) The platform computes the schema diff
# 3) The migration is applied transactionally
# 4) Tenant scoping and grants are updated
# 5) The generated API is refreshed
Was this page helpful?