Tables, columns, indexes, views
Generated pages show the technical shape of the database so the team does not inspect catalogs by hand for every question.
PostgreSQL documentation
PostgreSQL database documentation that follows schema changes.
Taavik scans PostgreSQL metadata through the on-premise agent and turns it into team-readable documentation with manual notes, object pages, and schema change history.
Metadata scan
Turn PostgreSQL catalogs into living documentation.
PostgreSQL exposes rich schema metadata, but teams still lose context in stale wikis and one-off diagrams. Taavik scans the current structure and keeps the documentation aligned with future changes.
Manual notes preserved
Add business meaning to tables and columns while generated metadata continues to refresh from scans.
PostgreSQL schema changes
Object-level change history shows what moved recently and keeps documentation useful after migrations.
Agent-based scan
The agent runs where PostgreSQL is reachable, so private database environments do not need public database access.
Workflow
Start with the tables that create questions.
Good first targets are customers, accounts, subscriptions, invoices, jobs, audit logs, and integration tables. Generate the baseline first, then add short notes where the schema alone is not enough.
Product
Database documentation
See the documentation layer that stores generated Markdown and manual notes.
ChangesSchema change detection
Review added, removed, renamed, and modified objects after each scan.
AgentPrivate database agent
Understand how scans and query runs are routed from inside the private network.
PostgreSQL
Document PostgreSQL without exposing the database.
Run a metadata scan, generate object pages, and keep documentation aligned with schema changes.