Skip to main content
JUMP TO:Quick StartCLI CommandsConfigurationPlaywright APIMCP ServerGitHub Actions
Deployment & Sandboxing / Self-Host(33 of 37)

Self-Host

PRE-RELEASE CLOUD. The local CLI needs no Frontguard service. Cloud source is included, but there is no supported one-command production self-host path.

Remember that @frontguard/cli, @frontguard/playwright, and @frontguard/mcp (in local report mode) require zero servers or cloud backends. This page documents the optional packages/cloud-api source for engineers evaluating self-hosted Cloudflare Workers.

Cloud API, Docker Renderer and NPM Distribution Topology
FIG 01 · SELF-HOST EVALUATION TOPOLOGY — CLOUDFLARE WORKER API, D1, R2 CAS & PINNED DOCKER RENDERER

Current status

The Compose build is not a verified clean-checkout flow and fails before the API starts because its package-scoped build context cannot access the repository OpenAPI sync script.

Architecture components

ComponentSource LocationTechnology Stack
Cloud API Workerpackages/cloud-api/Hono HTTP router targeting Cloudflare Workers
Metadata Storepackages/cloud-api/migrations/Cloudflare D1 (SQLite) for runs, baselines, monitors, and SHA-256 hashed API keys
CAS Blob Storepackages/cloud-api/src/routes/cas.tsCloudflare R2 bucket storing content-addressed PNGs under cas/{tenantScope}/{sha256}.png

Before production use

The renderer image is not published yet. Build from source only for local engineering evaluation, and verify migrations, retention, recovery, authentication, and tenant isolation before production use.