One static binary
CGO-free, built FROM scratch. SQLite + a volume are the only state.
gotifacts
Self-host static sites by host-based routing, browse them in a dynamic portal, and publish over a simple HTTP API.
What is gotifacts?
Section titled “What is gotifacts?”A single, self-hosted Go service that hosts static sites by host-based
routing and serves a dynamic portal to browse them. You publish sites over
an HTTP API; gotifacts stores them on a volume with a SQLite registry and
serves them at https://<slug>.<group>.<base>.
It runs behind any reverse proxy you provide (nginx, Caddy, …) for TLS and SSO/forward-auth. It serves plain HTTP on one port, never TLS, and enforces its own authorization.
Two-plane auth
A browser portal behind forward-auth/SSO, and a machine ingest API behind scoped API keys.
Publish from anywhere
CI, the Claude skill, or the OAuth-protected MCP connector.
No hardcoded hosts
Domains, paths, and limits are all configurable.
Find your way around
Section titled “Find your way around”These docs follow the Diátaxis framework.
TutorialsLearning-oriented: get a working instance and publish your first site.
How-to guidesTask-oriented recipes: deploy, configure a proxy, scope keys, connect Claude.
ReferenceInformation-oriented: env vars, the HTTP API, the CLI, conventions.
ExplanationUnderstanding-oriented: architecture, the auth model, the threat model.