dbdocs

dbdocs turns DBML definitions into browsable, web-based documentation for relational databases. It is best suited to development teams and software agencies that want a shared schema reference they can maintain alongside code. The trade-off is access: new projects are public by default, so private mode requires a paid plan.

Overview

DBML is an open-source markup language for describing database structures. dbdocs publishes those definitions as pages where readers can inspect tables and fields and visualize relationships. Teams can keep DBML locally or in Git and publish it to a project, making the documentation workflow a natural fit for groups already comfortable maintaining schema descriptions as code.

For an existing database, the documented db2dbml command supports PostgreSQL, MySQL, MSSQL, Snowflake and BigQuery. The product covers relational databases and includes a data dictionary and schema history. It is cloud-deployed; teams considering self-hosting can contact the team to discuss their requirements.

Key features

• Browsable schema reference: Readers can move through tables and fields and see relationships between tables, which makes published DBML more useful than a bare schema file for colleagues who need to consult it.
• Code-oriented publishing: Local or Git-based DBML can be published to a dbdocs project. CI instructions include a GitHub Actions example and token-based publishing, supporting an automated publishing workflow.
• Database conversion: db2dbml supports five named sources—PostgreSQL, MySQL, MSSQL, Snowflake and BigQuery—giving teams on those systems a documented route from database to DBML.
• Embedded views: Documentation views can be embedded in Notion, Confluence, Miro or a website, so readers can reach schema references from those destinations.
• Access controls: Projects start public. Free users can add password protection, while paid plans offer private mode. A password is not the same as private access, so teams with confidential schema details should budget for a paid tier or reconsider publishing.
• Security and support: The maker says Holistics is SOC 2 Type II compliant and dbdocs servers are hosted in Frankfurt, EU. Support resources include a contact form and service-status page.

Pricing

dbdocs uses a freemium model, with a free plan and a 7-day trial. The plan limits make the choice less about the basic documentation workflow than about privacy, project count and collaboration.

• Free — free: One user, public sharing and password protection. It is suitable for an individual working on public documentation or a password-protected project, but not for private-mode access.
• Personal Pro — $20 a month: Billed $20/month, or $16/month annually. It is single-user, includes 3 paid projects and allows up to 5 guest viewers per project, with private mode. This fits an individual who needs private projects and limited viewer access; it remains a one-user plan rather than a team editing tier.
• Team — $60 a month: Billed $60/month, or $50/month annually. It includes 3 editor seats, 5 paid projects, unlimited guest or workspace viewers and up to 6 guest editors. It suits teams that need multiple editors and broad viewing access, though the included editor seats and projects are capped.

The cheaper Free plan gives up private mode, while Personal Pro buys privacy without multiple editor seats. Team is the listed step up for shared editing and larger audiences. Choose based on the sensitivity of the schema and the number of editors and projects, not just the headline monthly rate.

Platforms

dbdocs is available on the web and lists Linux, macOS and Windows platforms. Its deployment is cloud-based, so those platform listings should not be read as a self-hosted deployment option.

Who it's for

Internal development teams and software development agencies are the clearest fit, particularly when they already use DBML or want to maintain schema documentation in Git and publish it through CI. It is less compelling for teams that require private access on a free tier, need more than the included seats or project counts, or require a standard self-hosted deployment.

Pros and cons

• Pro: DBML files can be maintained locally or in Git and published to a web project, aligning schema documentation with a code-oriented workflow.
• Pro: Import support spans PostgreSQL, MySQL, MSSQL, Snowflake and BigQuery, and embedded views can be placed in four named destinations.
• Pro: Private mode is available on paid plans, with a Team tier that includes unlimited guest or workspace viewers.
• Con: New projects are public by default; password protection on Free does not provide the private mode reserved for paid plans.
• Con: Personal Pro is single-user, and Team's included 3 editor seats and 5 paid projects may constrain larger groups.
• Con: Cloud deployment is the standard model; self-hosting requires a discussion with the team rather than a listed plan option.

Alternatives

Browse database documentation tools if you want to compare this category more broadly.

• MySQL is a freemium option with a free plan and Community Edition; consider it when a database platform, rather than a DBML-to-web documentation workflow, is what you need.
• dbForge Studio for PostgreSQL has a free Express plan with basic functionality and a limited feature set, plus a Standard subscription at $89.95 a year. Consider it when PostgreSQL-focused database tooling is the priority.
• Consider it when those design and synchronization capabilities are a closer fit.
• DBX is free and open source, community-built, and maintained in a public repository. Consider it if an open-source project with that community-maintained model better suits your preference.
• Taavik has a free plan with one database server, two members, 25 saved queries and 50 query runs per listed period. Consider it when those query-management limits match your needs better than DBML-based documentation.
• tbls is free, open-source software distributed as a single-binary CLI. Consider it if that packaging and open-source model is preferable.
• SchemaCrawler is free and open source, with bundled JDBC-driver distributions under GPL v3 and commercial-use licensing terms that can apply. Consider it if a free, open-source option is your starting point and its licensing terms suit your use.
• DataDocs has a web-based free plan with unlimited users, one data source, 25 assets and weekly refresh; its Growth plan is $25 a month with two data sources and 100 assets included, then $0.25 / asset. Consider it when those data-source and asset limits fit the documentation you need.

Verdict

Choose dbdocs if your team wants a shareable, web-based reference built from DBML and values Git or CI publishing, database conversion and embedded views. Its strongest reason to buy is that code-centered workflow; its clearest reason to look elsewhere is the public-by-default model and paid-only private mode, especially if confidential schemas or self-hosting are requirements.