Introduction

When to use this guide

• You are building an MVP, internal tool, or early-stage product.
• You want a production-ready baseline with low operational overhead.
• You do not currently need strict enterprise compliance controls from a full AWS stack.

Prerequisites

• Product requirements for web backend/frontend are defined.
• Team has access to Fly.io and Cloudflare accounts.
• You are ready to follow setup and deployment pages in sequence.

Default stack

• Fly.io — app servers, Postgres, Redis (Upstash), and S3-compatible object storage (Tigris)
• Cloudflare Workers — hosting an SPA or static frontend
• Mailgun or Resend — email delivery

What you will implement

• Account setup for Fly.io and Cloudflare.
• Local tooling setup (flyctl, wrangler).
• Backend deployment on Fly with Postgres, Redis, and object storage.
• Frontend deployment on Cloudflare Workers.
• CI/CD and runtime configuration management.

Verify

• Backend is deployed and reachable on Fly.
• Frontend is deployed and reachable on Cloudflare.
• Database migrations run successfully during deploys.
• CI pipeline can deploy a new revision without manual intervention.