Provision the database

Create an Azure Database for PostgreSQL Flexible Server, add a bytechef database, and allow access from your Container Apps environment (VNet integration or the server's firewall rules). Note the host, username, and password.

Create the Container App

Deploy the image as a Container App exposing port 8080 externally:

az containerapp create \
  --name bytechef \
  --resource-group <resource-group> \
  --environment <container-apps-env> \
  --image docker.bytechef.io/bytechef/bytechef:latest \
  --target-port 8080 \
  --ingress external \
  --secrets db-password=<db-password> encryption-key=<stable-encryption-key> remember-me-key=<stable-remember-me-key> \
  --env-vars \
    BYTECHEF_DATASOURCE_URL="jdbc:postgresql://<pg-host>:5432/bytechef" \
    BYTECHEF_DATASOURCE_USERNAME="<db-user>" \
    BYTECHEF_DATASOURCE_PASSWORD=secretref:db-password \
    BYTECHEF_ENCRYPTION_PROVIDER=property \
    BYTECHEF_ENCRYPTION_PROPERTY_KEY=secretref:encryption-key \
    BYTECHEF_SECURITY_REMEMBER_ME_KEY=secretref:remember-me-key \
    BYTECHEF_PUBLIC_URL="https://bytechef.example.com"

Use stable values for the encryption and remember-me keys, held in Container Apps secrets, so stored credentials and sessions survive revision restarts.

Configure health probes and scaling

• Set the Container App's readiness/liveness probe to GET /actuator/health/readiness and GET /actuator/health/liveness on port 8080.
• Set BYTECHEF_PUBLIC_URL to the Container App's public FQDN so webhook and OAuth2 redirect URLs resolve.
• Because schema migrations run at container startup, keep the app at a single replica during the first deploy and any upgrade. If you scale beyond one replica, 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 Container App's ingress URL and click Create account to register the first user.