Documentation as code
A good fit when the team wants to describe a database model in DBML and publish web-based documentation from that code.
Alternative · dbdocs
dbdocs alternative for private database teams.
dbdocs is useful when documentation lives as DBML code. Taavik is useful when the live database, schema changes, operational queries, and scheduled exports need to sit in one private workspace.
Docs as code vs scan-based docs
The source of truth is the key difference.
dbdocs starts from DBML files that describe the database structure. Taavik starts from scans of the actual database metadata, then renders documentation and records changes over time.
Live database scan
A good fit when the team wants documentation generated from the database that already exists inside a private network.
Update DBML or scan metadata
Docs-as-code works when the code stays current. Scan-based docs work when the live database is the reference.
Documentation plus operations
Taavik keeps docs close to saved SQL queries, scheduled exports, and run history.
What changes in Taavik
Documentation is generated from scans and connected to work.
Manual notes stay useful
The generated metadata can refresh while the team keeps its own descriptions and operational notes.
Read the guidePrivate agent scan
The agent scans metadata from inside the network and the workspace renders the documentation.
See how it worksOperational SQL
The same workspace holds the SQL that support, finance, and operations teams reuse.
See shared SQLChoosing
Use dbdocs when DBML is the workflow. Use Taavik when the live database is the workflow.
Taavik is built for teams that already have private databases and want documentation, query reuse, and scheduled exports to follow the database as it changes.
Try it
Keep docs and operational SQL in the same Taavik workspace.
Generate documentation from metadata scans, then connect it to saved SQL and recurring exports.