Dev Tools & Micro-SaaS
Stack Exchange · 2025-08-18
APIs have Swagger; databases need the same — schema as a tracked file with nice docs
API 有 Swagger，数据库 schema 也想要个『存进 Git 就能看』的工具
At a glance · 30-second read
- WhoStack Exchange · 2025-08-18 · 1 replies
- The askAPIs have Swagger; databases need the same — schema as a tracked file with nice docs
- The openingSwagger for databases: export JSON schema from a live DB, render visual docs, diff history in Git. Open core plus team tier.
What was actually said
“Swagger presents a JSON API schema nicely. What tool does the same for a database schema stored as JSON/XML? I want to track schema changes with Git only.”
— Stack Exchange · 2025-08-18 · softwarerecs.stackexchange.com/questions/93630/what-…
Background and pain
The pain
Schema changes live in tribal memory and migration scripts; with no textual source of truth, reviews can't see what the tables became.
A buildable angle
The opening
Swagger for databases: export JSON schema from a live DB, render visual docs, diff history in Git. Open core plus team tier.
How to validate it
- Read the whole thread and note the recurring scenarios — repetition is the density of the need.
- Search existing tools around "database / schema docs" and check which single step they actually cover.
- Put up a one-line landing page, share it back to Stack Exchange, and see whether anyone asks about pricing.
Existing options
Flyway/LiquibaseDBML/dbdocs
More threads on this pain
- How are teams sharing context across Claude Code, Codex and Cursor?Cursor Forum · 2026-05-06
- Turn 'correcting my AI coding agent' into a reusable skill libraryHacker News · 2026-10-13
- Hand-written Postman regression suites can't keep up with API changesStack Exchange · 2026-10-13
- Paid plans still hit limits: want a VS Code AI assistant without strict usage capsStack Exchange · 2026-07-13
- Switching coding agents means re-explaining your project from scratch every timeHacker News · 2026-10-21
From the thread · top comments
Open the source thread