Provision the database

Create a Cloud SQL for PostgreSQL instance and a bytechef database. Note the connection name, user, and password, and enable the Cloud SQL connection on the Cloud Run service so the database is reachable.

Deploy to Cloud Run

gcloud run deploy bytechef \
  --image=docker.bytechef.io/bytechef/bytechef:latest \
  --port=8080 \
  --allow-unauthenticated \
  --add-cloudsql-instances=<connection-name> \
  --set-env-vars=BYTECHEF_DATASOURCE_URL="jdbc:postgresql:///bytechef?cloudSqlInstance=<connection-name>&socketFactory=com.google.cloud.sql.postgres.SocketFactory",BYTECHEF_DATASOURCE_USERNAME="<db-user>",BYTECHEF_ENCRYPTION_PROVIDER=property,BYTECHEF_PUBLIC_URL="https://bytechef.example.com" \
  --set-secrets=BYTECHEF_DATASOURCE_PASSWORD=db-password:latest,BYTECHEF_ENCRYPTION_PROPERTY_KEY=encryption-key:latest,BYTECHEF_SECURITY_REMEMBER_ME_KEY=remember-me-key:latest

Use stable values for the encryption and remember-me keys in Secret Manager so stored credentials and sessions survive revision restarts.

Tune the service

• Health checks: point the Cloud Run startup / liveness probe at GET /actuator/health/readiness and /actuator/health/liveness on port 8080.
• Public URL: set BYTECHEF_PUBLIC_URL to the Cloud Run service URL (or your mapped custom domain) so webhook and OAuth2 redirect URLs resolve.
• Startup time: ByteChef runs schema migrations on first start; give the startup probe a generous timeout so the first revision becomes ready.
• Concurrency and instances: because migrations run at startup, deploy a single revision for the first release and any upgrade. If you allow more than one instance, apply the multi-instance settings in Running multiple instances — a shared message broker and cache, and a shared encryption key.

Access the instance

Open the Cloud Run service URL and click Create account to register the first user.

Create the instance

From the Compute Engine console, choose Create Instance and configure:

• Name: bytechef-server
• Region: whichever is closest to your users
• Machine type: e2-medium or larger, per the table above
• Boot disk: Ubuntu 22.04 LTS, 30 GB
• Firewall: allow HTTP and HTTPS traffic

Open the ByteChef port

Cloud Console's HTTP/HTTPS checkboxes open 80 and 443 only, so port 8080 needs its own rule under VPC Network → Firewall:

• Name: allow-bytechef
• Targets: all instances in the network (or a target tag on this VM)
• Source IP ranges: restrict to your own ranges where you can; 0.0.0.0/0 exposes the instance to the internet
• Protocols and ports: tcp:8080

If you terminate TLS on the instance (below), you do not need to open 8080 publicly at all.

Connect and install Docker

gcloud compute ssh bytechef-server --zone=<zone>

curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh
sudo usermod -aG docker $USER

Log out and back in so the group membership takes effect.

Deploy

curl -O https://raw.githubusercontent.com/bytechefhq/bytechef/master/docker-compose.yml
docker compose up -d

That Compose file brings up ByteChef and PostgreSQL together, but ships with fixed default credentials and a fixed remember-me key — use it for evaluation only. For anything durable, point the container at a Cloud SQL instance and supply your own secrets, as in the docker run command in the AWS EC2 guide.

Then browse to http://<external-ip>:8080 and click Create account to register the first user.