Web hosting

Rulebase’s customer-facing web properties run on Cloudflare. This page records deployment ownership, production verification, and rollback steps. See the Cloudflare over Vercel decision record for the migration history and cost impact.

Current hosting

Cloudflare Access remains the control plane for restricted Rulebase properties. The internal docs app is separate from this customer-facing migration and remains protected by Cloudflare Access.

UI deployment ownership

The US and EU apps deploy through .github/workflows/cloudflare-ui.yml.

• A push to release-prod deploys both Worker variants.
• Both variants use the same build. Region-specific API and application addresses are environment variables in the workflow matrix.
• The US deployment targets rulebase-ui.
• The EU deployment targets rulebase-ui-eu.
• GitHub uses CLOUDFLARE_WORKERS_API_TOKEN and CLOUDFLARE_ACCOUNT_ID to deploy. Do not add Cloudflare credentials to the repository.
• The workflow can also be dispatched manually, but its deploy job only runs for release-prod.

The marketing website is connected directly to its Git repository in Cloudflare and deploys automatically from its configured production branch.

Verification and rollback

After a production deployment:

1. Confirm rulebase.co returns successfully and www.rulebase.co redirects once to the apex domain.
2. Confirm both app.rulebase.co and eu.app.rulebase.co return successfully.
3. Confirm the matching US and EU jobs passed in the Cloudflare UI workflow.
4. Check that each app is calling the correct regional API endpoints.

Use Cloudflare Worker version rollback for an application regression. For a routing problem, inspect the custom domain and DNS configuration in Cloudflare before changing application code. Recreating a Vercel project is not the default rollback path.