Automatic saving
A new version is created automatically whenever a meaningful change happens — no manual checkpoint needed.
Core feature 03
Workspace & Project
Version History
Version History in Qubase is scoped per Project, not per Workspace. Every project keeps its own independent trail of ERD diagrams, database schemas, SQL/DBML scripts, and change history. A change made in one project never bleeds into another project's version history, even if both live in the same workspace — so each team's schema evolution stays cleanly isolated.
Live canvas
The Process of Version History
From your first table to a production-ready schema, every step stays visual, synchronized, and dependable.
Compare versions
Select any two versions to see exactly what changed in tables, columns, relationships, and constraints.
Version timeline
Every version is listed with its number, creator, timestamp, and a short summary of what changed.
Restore instantly
Authorized users can roll the project's database model back to any earlier version.
What you can do
- Browse a full timeline of every version created for a project
- Compare any two versions to spot exact differences
- Keep version history isolated per project, even in shared workspaces
- Audit changes using creator, date, and description metadata
- See who changed what — creator, timestamp, and summary
- Restore the project to a previous version instantly
- Skip manual checkpoints — versions save automatically
- Track added, removed, or modified tables, columns, and relationships