Platform Guide

Gemba Flow supports multiple deployment platforms. Your choice is stored in .claude/PROJECT.md and read by the devops-engineer and system-architect agents.

Supported platforms

Platform	Best for	Free tier	Preview envs
Render (default)	Full-stack web apps, APIs	Yes	Built-in
Cloudflare	Edge computing, static sites	Yes	Workers
Vercel	Frontend apps, Next.js	Yes	Automatic
GCP (Cloud Run)	Containerized apps, serverless backends	Yes	Manual

AWS support is not on the current roadmap. If you need to deploy to AWS, the framework is platform-agnostic in principle — you’d swap render.yaml for the equivalent AWS infrastructure-as-code (CDK, Terraform, or CloudFormation) and replace the Render-specific deploy / preview / rollback workflows. The four-step switch procedure below still applies, but the new platform’s specifics are on you.

Default: Render

The template ships configured for Render. render.yaml defines the service with preview environments enabled. deploy.yml deploys to Render on merge to main. preview-deploy.yml manages preview environments. rollback-production.yml rolls back via the Render API.

Switching platforms

Update .claude/PROJECT.md with the new platform.
Replace the platform-specific workflows: deploy.yml, preview-deploy.yml, preview-cleanup.yml.
Update render.yaml / vercel.json as needed.
Update repository secrets in GitHub settings.