Skip to main content
Xano is one platform to build, run and govern AI-built software. This section covers the govern part: the rules your team sets once, so that every change, from every person and every coding agent, reaches production the same way. Those rules live in places you already review. The project in git says what the backend is. The CI workflow says which checks a change must pass. The release flow says how a change reaches production: a build that came up on an ephemeral and passed its tests is stored as a release, and only a release is promoted or deployed to a tenant. Nothing an agent writes on your machine reaches production by any other route. AI code governance on xano.com describes the approach. The pages below are the commands and settings that put it in place.

​
What the Xano SDK enforces

Every refusal exits with a code a script or an agent can branch on, and --yes waives a confirmation, never a refusal.

​
The pages in this section

Schema changes

Tables are shared by every Xano branch. Change them in steps that keep their data.

Drift

Find edits made in the Xano editor, and bring them back into git.

Rollback and recovery

Serve the previous release again, and recover a run that stopped partway.

CI/CD

A complete GitHub Actions workflow: checks, previews, and releases on a tag.

Git, locks & merges

What to commit, xano.lock conflicts, renames, and the review checklist.

Agent guardrails

What a coding agent runs on its own, and what waits for your approval.

​
Next

Schema changes: the one kind of change a Xano branch cannot stage.