KamuHub platform documentation
Documentation for developers and coding agents building on and integrating with the KamuHub platform. It is self-contained: an agent working in an unrelated repository should be able to complete an integration from these pages without reading platform source code.
(Looking for the Finnish end-customer guide for the Kotisivukamu product? It lives under Kotisivukamu-opas.)
For agents
A machine-readable index of this whole site is generated at
/llms.txt. Fetch it first to discover
pages.
Platform map
Production runs on Fly.io under *.kamuhub.com.
| Service | What it owns | Entry point |
|---|---|---|
| kamuhub | The single front door: unified dashboard + BFF, platform authz (RBAC grants) and billing | app.kamuhub.com |
| kamuid | Identity: users, organizations, membership, KYC. The OIDC issuer every service logs in through | accounts.kamuhub.com |
| kamusites | Developer-facing websites service | via kamuhub |
| kamustatus | Uptime monitoring + error telemetry (see KamuStatus integration) | via kamuhub → Monitor |
| kamuforge | Self-hosted Forgejo git hosting for project repos | git.kamuhub.com |
| kamucdn | CDN serving live customer sites | — |
| kamudns | DNS management | via kamuhub |
Cross-cutting rules:
- Auth: everything authenticates through KamuID OIDC. The shared org key is
kamuid_org_id— one non-divergent id used by every service. - CLI: the
kamuCLI drives the platform from a terminal (kamu auth login,kamu status …,kamu clone …). Agents on a VM should use a scoped access key (export KAMU_ACCESS_KEY=...) instead of an interactive login. - Git:
kamu clone <project>clones from the platform forge and installs a credential helper, so plaingit push/git pullwork afterwards.
Integration guides
- KamuStatus: uptime + error telemetry — wire a service or website so its errors, health, and heartbeats show up in the kamuhub dashboard.