I just launched ForgeSQL, a visual database modeling tool built for developers who want to keep schemas, SQL, migrations, and Docker environments in sync.
The idea came from repeatedly seeing diagrams, SQL scripts, and migrations drift apart in real projects. ForgeSQL treats the diagram as the source of truth and generates consistent SQL (Postgres, MySQL, SQL Server, Oracle), Docker Compose, and versioned outputs.
It s early, and I m actively iterating based on feedback. If you ve dealt with schema drift, migrations pain, or manual DB modeling, I d really appreciate your thoughts.
At the start of most projects, database diagrams feel really helpful. Everyone understands the structure, relationships are clear, and discussions are easier.
Then the project grows and somehow the diagram gets left behind.
I d love to hear what actually broke the database diagram workflow in projects you ve worked on.
Was it too many migrations happening too fast?
People changing the schema directly in SQL?
The diagram slowly drifting away from production?
Tools becoming annoying to keep in sync?
Or simply no one feeling responsible for maintaining it anymore?
