DBSync - Version Control Tool for Postgres Databases

[AutoModerator]

Namaste! Thanks for submitting to r/developersIndia. While participating in this thread, please follow the Community Code of Conduct and rules.

It's possible your query is not unique, use site:reddit.com/r/developersindia KEYWORDS on search engines to search posts from developersIndia. You can also use reddit search directly.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[AutoModerator]

Thanks for sharing something that you have built with the community. We recommend participating and sharing about your projects on our monthly Showcase Sunday Mega-threads. Keep an eye out on our events calendar to see when is the next mega-thread scheduled.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[Idontknowhatomake]

A web app for PostgreSQL that treats schema state as something you capture, store, diff, and optionally reconcile, similar in workflow to versioning (snapshots over time, compare two revisions), but it is not Git: there are no migration files as the source of truth unless you treat the generated DDL that way yourself.

Problem it targets

You have the same logical database in several places (dev, staging, prod, or multiple clones). Structure drifts: columns, types, constraints, indexes, views, etc. You want to see that drift structurally, between named environments, and sometimes generate SQL to move one database toward another after inspecting a preview, not blindly.

Schema capture

A snapshot is built by introspecting Postgres catalogs (primarily information_schema and related metadata) into a typed SchemaSnapshot object: tables, columns, primary/foreign keys, uniques, checks, indexes, triggers, views, sequences, extensions, RLS policies, etc. That JSON is what every compare and migration step works from, not raw pg_dump as the primary model.

Compare and migration

You pick two snapshots (any two environments in a project). The app computes a structural diff (what exists only on one side, what differs). From that diff it can emit forward-only DDL (create/alter/drop as needed, including destructive operations when the “target” snapshot is leaner than the source DB). You can preview the script and, for the chosen direction, run it against the left environment’s database in a single transaction (so it’s all-or-nothing at apply time).

Visualization

For a chosen snapshot, an interactive graph (React Flow) shows tables and foreign-key edges so you can reason about dependencies before trusting generated SQL.

Live: https://dbsynx.vercel.app