Ship your site.
Skip the ops.

Every site is deployed to Cloudflare Pages via Direct Upload or GitHub Actions (wrangler-action@v4). Static assets are served from Cloudflare's Anycast network across 300+ PoPs globally.

Deploy artifacts are stored in Cloudflare R2 (zero egress fees). DNS is managed through Cloudflare's authoritative DNS. SSL certificates are issued automatically via Cloudflare's Universal SSL.

The portal and API run on Cloudflare Workers at the edge. Auth is custom PBKDF2 sessions in Cloudflare D1 (SQLite at the edge).

On site creation with mode=git, the provisioning Worker calls the GitHub Contents API to inject .github/workflows/evancx-deploy.yml into the customer's repo. The workflow runs wrangler pages deploy on every push to main.

The CF Pages project is always created as Direct Upload — no CF Git integration. GitHub Actions is the delivery mechanism. The org-level CLOUDFLARE_API_TOKEN secret is inherited by all customer repos automatically.

Cloudflare's Anycast network provides inherent redundancy — no single point of failure. CF Pages has a 99.9%+ uptime track record. Static assets are cached at the edge; origin requests only happen on cache miss (rare after first deploy).

TTFB from cache is typically under 50ms globally. Cloudflare's network capacity exceeds 100 Tbps, providing automatic DDoS mitigation with no configuration required.

Custom domains are registered via the CF Pages API (POST /accounts/{id}/pages/projects/{project}/domains). The customer adds a CNAME pointing yourdomain.com → evancx-{slug}.pages.dev.

CF Pages automatically provisions an SSL certificate via its Universal SSL pipeline once DNS propagates. Apex domain support requires either Cloudflare nameservers or registrar-level CNAME flattening.

Every zip upload is stored in Cloudflare R2 at sites/{site_id}/deploys/{deploy_id}.zip. A rollback re-deploys the stored artifact via the CF Pages Direct Upload pipeline, creating a new deployment record with the original git_sha.

Git-connect deployments roll back via git history — no R2 artifact needed. The portal's History tab lists the last 20 deployments with one-click restore.

Uploads are capped at 50 MB per zip (validated server-side before upload). Individual files are limited to 25 MB (CF Pages limit). Up to 5,000 files per deploy.

Bandwidth is unlimited — Cloudflare does not charge for egress on Pages deployments. Storage is 5 GB (Simple 1-site) or 15 GB (Simple 3-site) of R2 artifact storage.