Visual schema designer for teams using managed MySQL or Postgres

The specific moment: a backend developer needs to explain to a product manager why adding a new feature will require three table changes, or a new engineer joins and needs to understand how the data model works. There is no diagram. The database lives in RDS or Aurora and the native console shows nothing visual — just lists of table names. Users specifically name this: 'the lack of a GUI to visualise and create an architecture diagram' is a direct complaint, not a derived one.

This gap is structural in an interesting way. The managed database vendors (AWS, Aiven, Alibaba) are in the business of running databases, not modeling them. Schema design tools that do exist tend to live in the world of enterprise ERD software aimed at data architects — they're expensive, desktop-based, require exports and imports, and are purchased by a completely different buyer than the developer actually running the managed database. Nobody has built the lightweight, always-in-sync version that connects directly to a live managed database instance and keeps the diagram current as migrations run.

The recurring cost of not having this is subtle but real: onboarding new engineers takes longer, cross-functional conversations about data structure require someone to manually draw diagrams in Figma or Miro that go stale the moment a migration runs, and architectural decisions get made without anyone having a clear picture of existing relationships. This recurs every sprint, every new hire, every product review.

This is a business and not a feature because AWS has no incentive to build it — it doesn't affect uptime, cost, or retention at the infrastructure level. And the ERD tool vendors don't connect to live databases dynamically; they're built around design-then-deploy workflows, not already-running-in-production workflows.

What to build

Build a web app that connects to a live PostgreSQL or MySQL database via read-only credentials, auto-generates an interactive entity-relationship diagram from the live schema, lets teams annotate tables and columns with plain-English descriptions, and re-syncs the diagram automatically when migrations are detected — shareable via a link without requiring the viewer to have database credentials.

Where to start

Target teams already using GitHub for migrations via tools like Flyway or Liquibase — you can hook into the migration file history to show a changelog of schema evolution alongside the diagram, which is a capability no native console offers and something every team with more than six months of history immediately wants.

The hard part

Getting to 'always in sync' is technically straightforward, but convincing a team to give even read-only credentials to a third-party service requires either a self-hosted deployment option or SOC 2 compliance early — both are expensive for a pre-revenue product, and skipping them cuts you off from any customer with basic security requirements.

How it makes money

Free for a single database connection and read-only diagram; paid plans at $30-50 per month per workspace for annotation, changelog history, and multiple database connections — billed to the team, not per seat.