Private team-owned context
Keep internal documentation tied to the team's real environment instead of treating the schema as a disconnected public artifact.
Private documentation workflow
Internal database documentation that stays attached to real metadata.
Use DataPilot when documentation needs to stay private, searchable by the team, attached to real database context, and connected to the same workspace used for SQL review, reports, exports, and governed follow-up.
This page is not about a public ERD canvas
If you need a free ERD diagram generator and a visual documentation workflow, use DataPilot ERD. This page is for teams that need internal documentation tied to private database context and broader governed workflows.
Metadata stays close to the workflow
Documentation, SQL review, exports, and delivery can stay connected to the same operating layer.
Catalog and AI documentation support
Browse schemas, inspect tables and columns, and use AI-assisted documentation where appropriate with a review step.
Governed internal use
This is for internal teams, internal context, and trusted workflow continuity.
When the team needs public visual exploration, point people to the SQL to ERD tool, the database schema visualizer, the ERD without foreign keys, and collaborative ERD review. If the goal is internal documentation continuity, keep it inside DataPilot.
Teams that want diagram-led references without exposing internal context can also use database documentation with diagrams.