Great news! We're introducing Data Sample — a feature that lets you add example data rows directly alongside your table definitions in DBML. Now your documents can show not just schema, but actual data, making them far more meaningful and useful for team communication.

Here's a simple DBML example:

Table plans {
  id int [pk]
  name varchar
  price decimal

  // define inside table definition with implicit column list
  Records {
    1, 'Free', 0
    2, 'Pro', 8
    3, 'Team', 15
  }
}

// OR define outside table definition
Records plans(id, name, price) {
  1, 'Free', 0
  2, 'Pro', 8
  3, 'Team', 15
}

Define sample data right in DBML, and your documents instantly comes alive. You can import SQL INSERT INTO statements to auto-populate records, and export back to SQL for database seeding. This keeps your reference data and schema definitions in perfect sync across docs and deployment.

Why it matters:

• Your documents explain themselves — team members see actual data shapes and values, not just column definitions.
• Lookup tables finally have a home — define plans, roles, and other reference tables with their data, all in one place.
• Catch schema problems early — real data reveals missing columns, type mismatches, and broken relationships before migration.
• Convert existing data seamlessly — import SQL statements and auto-convert to Records for instant visualization.
• Seed your database faster — export sample data to SQL and deploy immediately.

Available Now: Data Sample is available on all plans starting today. Check out the feature in action at our Live Demo →

📚 Read the full syntax docs →

Try it out and let us know what you think!

Great news! We've added support for Check constraints, allowing you to set rules on your table fields to enforce data quality—such as ensuring quantities are above zero or ratings stay within a range.

Here's a simple DBML example:

Table orders {
  id integer [pk, increment]
  price decimal [not null, check: `price > 0`]
  discount decimal [not null, default: 0, check: `discount >= 0`]

  checks {
    `discount < price` [name: 'valid_discount']
  }
}

Previously, these had to go in notes, which meant they could disappear during SQL imports or exports. Now, define them right in DBML, import and export with accuracy, and view them in your ER diagrams and docs for clearer sharing.

It's a simple way to make your databases more reliable and your documentation more informative. Update your docs now and start applying Check constraints!

📚 Read the full docs →

We hope these enhancements improve your database design and communication experience. Try them out and let us know what you think.

You know that moment when you're reading database documentation and thinking "Is this documentation up to date?" 🤔

We just solved that.

We're excited to announce Wiki Changelog – a collection of features that show schema changes directly in your documentation pages.

Stay in your flow. Know what changed. When it changed. Who changed it.

🕒 Recent Activities & Entity Last Update​

Get a quick glance at recent schema updates directly in your wiki pages. See at-a-glance timestamps on each table, field, and schema component so you can instantly assess how current your documentation is without digging deeper.

🔄 Entity-Specific Changelog​

Drill down into the evolution of individual tables, table groups, or fields. Each entity now has its own changelog so you can track specific changes over time and understand how particular parts of your schema developed.

🔍 Wiki Diff View​

Compare any two versions without leaving your documentation using Wiki Diff View. From here, you can toggle between familiar documentation style or raw code view.

💡 Why You'll Use It​

• Debug issues: When something breaks or data looks wrong, quickly see what changed in specific tables or fields recently.
• Share with teams: Point teammates to recent changes during discussions or code reviews.
• Review before changes: Check recent activity on tables or fields before making your own modifications.
• Track compliance: See who made what changes and when for audit trails.
• Plan migrations: Understand change patterns before planning major schema updates.

🚀 Available Now​

Wiki Changelog is rolling out to all dbdocs users starting today. Check out the features in action at our live demo: Ecommerce - dbdocs.io or visit any of your existing documentation pages.

If you have any feedback for us, feel free to share it in this community post.

We’re excited to introduce browser-based editing for dbdocs projects! Powered by dbdiagram.io’s editing features, this update offers a seamless experience for creating and managing your database documentation.

Edit projects directly in the browser​

• From your dbdocs project site, click Edit (via dbdiagram).
• Your project opens in an online editor powered by dbdiagram.
• Make changes, save your draft, then Publish to update the live docs.

Instantly create new projects​

• Start a new dbdocs project with an online editor powered by dbdiagram, no CLI required.
• When ready, publish it to your dbdocs workspace.

Paid features still apply​

• Paid dbdocs users can continue to use their paid features, such as table groups and header colors, while editing in the online editor.
• You now no longer need to buy subscriptions for both dbdiagram and dbdocs to use paid editing features. Instead, you can buy them separately based on your needs:
  • Purchase dbdiagram if you only need to create ERDs.
  • Purchase dbdocs if you require both ERDs and web-based database documentation.

🤔 Why the Change?

• This update makes it easier for more people — from junior developers to product managers — to collaborate on database documentation. Whether you're proposing schema changes or just adding notes, you can now do it all in the browser.
• This update is also part of a larger vision: bringing dbdocs and dbdiagram closer together to bring you a powerful data modeling experience.

Experience browser-based editing and let us know your feedback!

We’re thrilled to announce some big changes to our pricing plans at dbdocs.io, designed to better serve both individual users and teams like yours.

Here’s what’s new:

• 🌟 New Personal Pro Plan at $20/month: The old Pro plan ($60/month) has been replaced with a more affordable Personal Pro plan for individuals to create and share database docs with advanced features.
• 👥 New Team Plan at $60/month: For teams, we’ve introduced the Team plan at the same price as the old Pro plan, now with enhanced collaborative workspace features.
• 🤔 Why the Change? The old Pro plan, while feature-rich, was too expensive for individual users and lacked advanced team collaboration tools. We’ve addressed this by introducing the affordable Personal Pro plan for individuals and the Team plan with new features to streamline team workflows.
• 🚀 Free Upgrade for Existing Pro Users: If you’re on the old Pro plan, you’ve been automatically upgraded to the Team plan at no extra cost, so you can enjoy these new team features right away!

To help you understand the differences, here’s a quick comparison:

You can check out all the details on our pricing page.

Have questions? Reach out to us at [email protected]. We’re here to help!