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 from Cloud Providers in the organization sidebar. See Bring Your Own Cloud for the setup, credential, and removal steps.

After it is 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. Choose a different provider on the next reflex deploy, or pass --provider, to switch it.

Switching a deployed app removes its resources from the previous provider and redeploys it to the new one. In interactive mode, the CLI shows a warning and asks for confirmation first.

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