CepatEdgeOwn your maintenance stack

Self-hosted docs for institutions and small teams — Workers, Pages, Durable Objects, and R2 without the enterprise billing trap.

Guides for operators

Getting started, deployment, domains and cookies, runbook, API, and configuration for a self-hosted instance.

System map, principles, ADRs, and runtime notes — how the edge stack is put together and why.

Maintenance workflows and cache contracts so product behavior stays predictable across roles.

Security overview, retention and privacy, plus clear ownership for runtime, secrets, backups, and support.

SPA architecture, permissions, TanStack Query, and i18n — how the Pages app is structured.

Study-case stubs and the product origin story for institutions evaluating a reference deployment.

Audience	Start here
Institutions / orgs	Security, Guides, About, Cases
Small teams	Getting started, Deployment, Workflows
Study cases	Cases
Contributors	Architecture, Frontend, Lifecycle — plus `maintainer/` in the repo for phases, systems maps, and agent rules

Section	What you will find
About	Vision, public roadmap, ownership
Why this exists	Product rationale
Guides	Getting started, deploy, runbook, API, configuration
Architecture	System map, principles, ADRs
Lifecycle	Maintenance workflows and cache contracts
Security	Security overview, retention and privacy
Workflows	Development and deployment processes
Frontend	SPA architecture, query, i18n, permissions
Cases	Study cases / reference deployments
Journey	Origin story