Deployment & Operations

Foundry deploys to three managed platforms. There is no Docker Compose self-host path in v1 — all deployment assumes a BYO-cloud footprint across Vercel, Convex Cloud, and Cloudflare.

Vercel          → Next.js frontend (SSR, Edge Middleware, OAuth callbacks)
Convex Cloud    → Backend (81 tables, server functions, AI actions, webhooks)
Cloudflare      → Agent Worker (AI analysis) + Sandbox Worker (code execution)

Section map

Production Setup Step-by-step deployment of all four services — Cloudflare Workers, Convex, Vercel, and webhook configuration.

Cost Estimates Monthly cost breakdown by service at evaluation, early production, and scaling tiers.

Rollback Procedures Per-service rollback procedures for Vercel, Cloudflare Workers, and Convex.

Prerequisites

Before deploying, ensure you have:

• Cloudflare account with Workers Paid plan (needed for Durable Objects and Containers)
• Vercel account (Pro recommended for production)
• Convex Cloud deployment provisioned via bunx convex deploy
• Clerk production instance with organizations enabled
• GitHub App configured with webhook URL and OAuth credentials
• Atlassian OAuth app (optional, for Jira/Confluence integration)
• wrangler CLI authenticated: wrangler login
• Anthropic API key with sufficient credits

Tip

Deploy in order: Cloudflare Workers first (you need their URLs), then Convex (needs Worker URLs as env vars), then Vercel (needs Convex URL). Webhooks are configured last since they point to the Convex HTTP endpoints.