Runbooks generated from real infrastructure state
Source syncs create living pages from parsed resources, relationships, notes, and pipeline metadata instead of stale wiki text.
Self-hosted infrastructure documentation that stays in sync
Turn infra code and delivery pipelines into living runbooks.
SyncDoc scans Terraform, Docker, Ansible, Git repositories, and CI/CD workflows, then produces operator-friendly docs, service graphs, and drift visibility in one place.
IaC + CI/CD
Extracts runtime and delivery context from the same repo.
Graph + Pages
Interactive topology plus human-readable runbooks.
Drift-aware
Surface changes before the docs quietly fall behind.
Why teams use it
Built for engineers who need docs they can trust at 2 a.m.
Graph views for infrastructure and delivery flow
Explore how services, environments, deployments, and supporting resources fit together without stitching context across tools.
Drift visibility and operational context
Catch changes, keep docs current, and give operators a clearer starting point when something deviates from the expected shape.
One repo, multiple signals
SyncDoc reads the code your team already ships.
Modules, resources, variables, outputs, and stack relationships.
Compose services, images, networks, volumes, and Dockerfiles.
Inventories, playbooks, roles, group vars, host vars, and host topology.
Mixed repos can also extract GitHub Actions and GitLab CI so deployment flow sits beside the infrastructure it changes.
How it works
Sync source. Build graph. Generate docs. Stay current.
Add a repository, let SyncDoc inspect what it contains, and use the resulting graph, search, runbooks, and drift events as your operational reference layer.
- 1. Add a repo Git is the umbrella path for infra plus CI/CD repos.
- 2. Sync and parse Connectors extract resources, dependencies, environments, and jobs.
- 3. Generate docs Pages and diagrams appear alongside a live service dependency graph.
- 4. Watch drift Stay ahead of changes and keep operator context fresh.
Deployment model
Ready to sit on the same VM as the app.
Containerised website
This landing page is packaged as a standalone static Docker service, so it can live beside the app without changing your backend/frontend containers.
Traefik at the root domain
The prepared routing targets syncdoc.dev on the existing Traefik
instance, while the app stays on app.syncdoc.dev.
Cloudflared unchanged
Your tunnel already forwards the apex domain to Traefik, so exposing the site is mostly a matter of enabling the website container and root-domain route.
Preview first