DOCAT

DOCAT is a lightweight server for hosting static documentation projects (MkDocs, Sphinx, mdBook, etc.) and multiple versions of those projects. It provides a simple HTTP API and a companion CLI to push, tag and serve documented sites from a single instance.

Key Features

• Host multiple documentation projects with multiple versions and per-version tagging (e.g., latest).
• Push documentation archives via an HTTP API or the provided CLI tool (docatl) for CI/CD integration.
• Built-in static file serving with a web frontend and full-text search for hosted docs.
• Docker-first distribution (container image) and Dockerfile for easy deployment and updates.
• Frontend is configurable via a simple JSON config (header/footer HTML) and supports serving static files from a mounted volume.
• Simple project claiming and token-based control for modification actions; README recommends protecting write endpoints (e.g., HTTP basic auth).
• Designed to be minimal and easy to operate: focuses on hosting and versioning only, not authoring.

Use Cases

• Host internal or public product documentation with versioned releases for software teams.
• Integrate documentation publishing into CI pipelines to automatically deploy new versions of docs.
• Provide a single, self-hosted docs portal for multiple projects where users can switch between released versions.

Limitations and Considerations

• By default the server allows unauthenticated uploads and modifications until a project is claimed; administrators should secure the API (README recommends HTTP basic auth for POST/PUT/DELETE).
• DOCAT is a host for static documentation only — it does not provide authoring, rendering pipelines, or dynamic content generation.
• There is limited built-in access control and no advanced role-based permissions; for public deployments additional reverse-proxy authentication or network controls are recommended.

DOCAT is a focused, pragmatic tool for teams that need a simple, versioned documentation host with easy CI integration. It emphasizes ease of deployment and minimal configuration while leaving authoring and build workflows to established static documentation tools.