One of the main reasons I started building ForgeSQL was seeing how database diagrams slowly stop reflecting reality.

They usually start accurate, but over time:

• tables change through migrations

• relationships get added or removed

• multiple people touch the schema

• the diagram no longer matches what s actually in production

I m curious to hear from you:

Hey everyone

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?

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?

I m working on ForgeSQL, a tool to design database schemas visually and generate SQL automatically.
The goal is to keep diagrams useful even as projects grow, instead of being abandoned after the initial design phase.

I ve also started experimenting with AI to suggest database relationships from the visual model.
If you work with databases, I d love to hear your thoughts or feedback.

https://www.producthunt.com/p/fo...

In many projects, diagrams are very helpful at the beginning, but tend to be abandoned once the schema stabilizes and development speeds up.

From your experience, what usually causes this shift?
Is it maintenance cost, lack of trust, tooling limitations, or something else?

I m interested in real-world reasons, especially in medium to large systems.

ForgeSQL now uses AI to suggest and generate database relationships from a visual model.

From your experience, would you trust AI at this stage, or prefer full manual control?
What would make this actually useful in real projects?