Cloud Providers

By default, reflex deploy runs your app on Reflex Cloud's managed infrastructure. If your organization has connected its own cloud account, you can instead deploy the same app — with the same reflex deploy command and the same managed lifecycle (logs, scaling, history, rollbacks) — into your own cloud account. Today this is supported for Google Cloud (GCP), where your app runs on Cloud Run in your GCP project.

An organization admin connects the GCP account once, from the Reflex Cloud dashboard under Organization → Cloud Providers. You provide a service-account key, your GCP project number, and a region; Reflex validates that the service account has the permissions needed to deploy Cloud Run services and push images to Artifact Registry before storing the (encrypted) credentials.

Once connected, check availability from the CLI:

This reports whether GCP is connected, whether your plan allows GCP deploys, and the connected project and region. List all connected provider accounts with:

When your org has GCP connected, reflex deploy asks where you want to deploy:

Choose reflex-cloud for Reflex's managed infrastructure or gcp for your connected Google Cloud account. To skip the prompt (for example in CI), pass --provider:

You can also pin the provider in your cloud.yml / pyproject.toml so every deploy targets the same place:

When you deploy to GCP, the region and machine sizing come from the connected GCP account, so --region and --vmtype are ignored.

An app remembers its provider between deploys. You can switch it at any time by choosing a different provider on your next reflex deploy (or with --provider). Switching a deployed app tears down its resources on the previous provider and requires a redeploy to come back up on the new one — reflex deploy performs that redeploy as part of the switch. In interactive mode the CLI warns and asks for confirmation before switching a deployed app.

Deployment descriptions and rollbacks work the same way on both providers — see App management.