Version history: see, undo and restore changes

Sovaria records your project's configuration on a timeline, like commits in git. A commit is written automatically whenever a policy, table, function, project setting, bucket or API key changes — from the console, the CLI, the SDKs or Sovariq. Your app's data rows are not part of the timeline; they are covered by backups.

#What a change did

In Version History, pick a commit. Each item it touched is listed in words — "column note added (text)", "allowPublicSignup: false → true", "rule changed" — next to that item's own previous version, not simply the previous commit (which is usually about something else). Expand an item to see before and after.

#Undo one change

Undo this change puts back exactly what that commit changed and nothing else. You see the plan first: the items that go back, items that changed again since (undoing puts back the older version of those too), and who would gain or lose access afterwards. A schema change is undone by running its migration's down SQL; if a migration has no down SQL, the undo is blocked and says which one.

#Go back to an earlier point

To return the whole project configuration to a moment in time, show the restore plan, then apply it. Changes are made through the normal API with your own permissions, so policies and plan limits still apply and the restore itself becomes a new commit.

# What the project looked like then (policies/, schema/, functions/, settings/, storage/, keys/)
sov chrono state --at 2026-10-15T09:00:00Z --prefix policies/ --names-only

# Show the plan, confirm, apply
sov chrono restore 2026-10-15T09:00:00Z

#Branches

Branches let you record experimental configuration separately from main and compare them. main is append-only: history is never rewritten there, and rewriting another branch's history needs a project admin.

sov chrono timeline-list
sov chrono timeline-history --help

#Production notes

• Restores and undos run with your permissions: a developer can't restore a change they couldn't make by hand.
• Secrets are never stored on the timeline — only that a key or secret exists, not its value.
• Point-in-time recovery of database data is a separate, plan-dependent feature; see Plan limits.