Latest
Ptah 0.25.0 Release: From Native YDB to a Provider Platform
A visual guide to the releases since our Ptah 0.13.0 post: provider engines, safer schema changes, and clearer limits in Ptah 0.25.0.
Read the guideGuides and examples
Compare your database with the schema you want. Generate SQL migrations, review the changes, and apply them.
Your database + desired schema to SQL migration to review to apply
Latest
A visual guide to the releases since our Ptah 0.13.0 post: provider engines, safer schema changes, and clearer limits in Ptah 0.25.0.
Read the guideDuckDB is now in the Ptah Playground. Preview schema changes, detect drift, and try versioned migrations in your browser without installing anything.
Choose a database migration tool by its source of truth, review workflow, drift check, database coverage, and deployment model.
Compare Atlas and Ptah by the database jobs they solve: plans, approvals, migrations, drift, OCI distribution, plugins, and rollout boundaries.
How we extracted YDB into a Ptah plugin, from semantic ownership and release decisions to lock failures, performance, model identity, and parity.
Build a database plugin on Ptah's provider API, or use the official YDB, Spanner, and DuckDB plugins. See the capabilities and a complete DuckDB example.
Use Ptah's official DuckDB plugin to inspect an embedded database, generate reviewable SQL migrations, apply them, and verify the result.
Run the same PostgreSQL change with Liquibase Community and Ptah, then compare edited history, rollback, and checks for changes made outside the changelog.
We ran Ptah Operator and SchemaHero on one cluster: stale plans, destructive changes, drift, failed statements, approvals, and PostgreSQL coverage.
Compare two PostgreSQL schemas, such as staging and production, with one Ptah command. Read every difference as SQL and review it before anything runs.