Self-hosted OpenAPI and Swagger documentation portal
Most teams start with Swagger UI served by each service. It works until you have twenty services: twenty addresses, twenty versions of the page, no common search and no history. SelfDocHub replaces that with one portal that lists every service, lets you search across all of them and keeps the history of each specification. It runs on your own server, so internal APIs never leave your network.
One portal for every service#
Every service you register becomes a tile on the services page. You can group services into blocks with names and icons (for example Payments, Identity, Internal tools), and arrange each service by hand into folders, tags and text pages. Readers and editors see only the services of their teams, so a contractor can be given one service and nothing else.
Each operation gets its own page with the description, request parameters and body, responses, examples and a Try-It panel. Addresses are stable and shareable, so a link to an endpoint in a pull request or a chat message keeps working after the next release.
Publish from CI with one request#
A service publishes its specification with a single call and its own upload token:
curl -X POST https://docs.example.com/api/v1/services/billing-api/spec \
-H "Authorization: Bearer $DOCS_UPLOAD_TOKEN" \
-H "Content-Type: application/json" \
--data-binary @openapi.json
SelfDocHub checks the document, stores an immutable copy as a new version, computes what changed against the previous
version, rebuilds the merged documentation and can notify your team. Re-publishing identical content creates nothing,
so it is safe to run on every build. You can also use branches (?branch=feature-x) to preview documentation for a
feature before it is merged.
Search, navigation and structure#
- Full-text search across all services, including the text pages you write yourself.
- A left menu with folders, tags and endpoints in the order you choose, and favorites for the endpoints you use daily.
- Markdown overlays that replace the description of a service, tag, endpoint or even a single parameter without touching the source specification, and survive the next publish.
Runs where your code runs#
SelfDocHub is a single static binary with the web interface embedded. There is no separate database to install, patch or scale: users, teams and metadata live in an embedded SQLite file, and the documents are plain files in the same data directory. Install it with Docker Compose behind Nginx and TLS, or run the binary directly on Linux. A backup is a copy of one directory.
What it costs#
The Free plan includes a license for one installation, up to 3 services and 2 users, which is enough to evaluate it with your real specifications. Paid plans raise the limits and add SSO, notifications and larger MCP quotas. The price does not grow with the number of people who read the documentation. See pricing.
