Skip to main content
Version: Next

Cloud Platform Deployment for Platformatic Watt

Use a long-running Node.js/container service with Node.js 22.19.0+ and major 3 Watt dependencies locked in the project. These provider examples need adaptation to the selected account, region, current provider API, and actual health endpoint. Install tools, create resources, set secrets, and deploy only when authorized.

Ensure npm start invokes the local Watt CLI. Configure the Watt 3 root server (or a standalone capability's runtime.server) to consume the provider's port and bind to 0.0.0.0. Use Docker for reproducible builds and retain all app artifacts.

Fly.io​

Installation​

# Install flyctl
curl -L https://fly.io/install.sh | sh

# Login
fly auth login

Configuration​

Create fly.toml:

app = "my-watt-app"
primary_region = "iad"

[build]
  dockerfile = "Dockerfile"

[env]
  NODE_ENV = "production"
  PLT_SERVER_HOSTNAME = "0.0.0.0"
  PLT_SERVER_LOGGER_LEVEL = "info"
  PORT = "8080"

[http_service]
  internal_port = 8080
  force_https = true
  auto_stop_machines = true
  auto_start_machines = true
  min_machines_running = 1
  processes = ["app"]

[[http_service.checks]]
  grace_period = "10s"
  interval = "30s"
  method = "GET"
  path = "/health"
  timeout = "5s"

[[vm]]
  cpu_kind = "shared"
  cpus = 1
  memory_mb = 512

Deployment Commands​

# Launch new app
fly launch

# Deploy
fly deploy

# Set secrets
fly secrets set DATABASE_URL="postgresql://..." SESSION_SECRET="..."

# Scale
fly scale count 3

# View logs
fly logs

# SSH into machine
fly ssh console

Railway​

Configuration​

Create railway.json:

{
  "$schema": "https://railway.app/railway.schema.json",
  "build": {
    "builder": "DOCKERFILE",
    "dockerfilePath": "Dockerfile"
  },
  "deploy": {
    "numReplicas": 1,
    "startCommand": "npm start",
    "healthcheckPath": "/health",
    "healthcheckTimeout": 30,
    "restartPolicyType": "ON_FAILURE",
    "restartPolicyMaxRetries": 3
  }
}

Or use railway.toml:

[build]
builder = "dockerfile"
dockerfilePath = "Dockerfile"

[deploy]
healthcheckPath = "/health"
healthcheckTimeout = 30
numReplicas = 1
restartPolicyType = "on_failure"
restartPolicyMaxRetries = 3

Deployment​

# Install Railway CLI
npm install -g @railway/cli

# Login
railway login

# Initialize project
railway init

# Deploy
railway up

# Set environment variables
railway variables set NODE_ENV=production
railway variables set DATABASE_URL="postgresql://..."

# View logs
railway logs

Render​

Configuration​

Create render.yaml:

services:
  - type: web
    name: watt-app
    env: node
    region: oregon
    plan: starter
    buildCommand: npm ci && npm run build
    startCommand: npm start
    healthCheckPath: /health
    envVars:
      - key: NODE_ENV
        value: production
      - key: PLT_SERVER_HOSTNAME
        value: 0.0.0.0
      - key: PLT_SERVER_LOGGER_LEVEL
        value: info
      - key: DATABASE_URL
        fromDatabase:
          name: watt-db
          property: connectionString
    autoDeploy: true
    scaling:
      minInstances: 1
      maxInstances: 3
      targetMemoryPercent: 80
      targetCPUPercent: 70

databases:
  - name: watt-db
    plan: starter
    region: oregon

Deployment​

  1. Connect GitHub repository to Render
  2. Create new Web Service
  3. Select repository
  4. Render auto-detects settings from render.yaml
  5. Add environment variables in dashboard
  6. Deploy

Vercel​

Vercel's native Next.js deployment does not run a long-lived Watt runtime. Use it only when intentionally deploying the frontend independently. For Watt orchestration, workers, mesh networking, and scheduler jobs, choose a compatible container/Node service.

Independent Next.js deployment​

Create vercel.json:

{
  "buildCommand": "npm run build",
  "outputDirectory": ".next",
  "framework": "nextjs",
  "regions": ["iad1"],
  "env": {
    "PLT_SERVER_LOGGER_LEVEL": "info"
  }
}

Deployment​

# Install Vercel CLI
npm install -g vercel

# Deploy
vercel

# Production deploy
vercel --prod

# Set environment variables
vercel env add DATABASE_URL

DigitalOcean App Platform​

Configuration​

Create app.yaml (for DO App Spec):

name: watt-app
region: nyc
services:
  - name: web
    dockerfile_path: Dockerfile
    github:
      repo: your-username/your-repo
      branch: main
      deploy_on_push: true
    http_port: 3000
    instance_count: 2
    instance_size_slug: basic-xxs
    health_check:
      http_path: /health
      initial_delay_seconds: 10
      period_seconds: 30
    envs:
      - key: NODE_ENV
        value: production
      - key: PLT_SERVER_HOSTNAME
        value: "0.0.0.0"
      - key: PLT_SERVER_LOGGER_LEVEL
        value: info
      - key: DATABASE_URL
        scope: RUN_TIME
        type: SECRET
    routes:
      - path: /

databases:
  - name: db
    engine: PG
    version: "16"
    size: db-s-dev-database

Deployment​

# Install doctl
brew install doctl

# Authenticate
doctl auth init

# Create app
doctl apps create --spec app.yaml

# Update app
doctl apps update <app-id> --spec app.yaml

# View logs
doctl apps logs <app-id>

AWS (Elastic Beanstalk)​

Configuration​

Create .ebextensions/nodecommand.config:

option_settings:
  aws:elasticbeanstalk:container:nodejs:
    NodeCommand: "npm start"
  aws:elasticbeanstalk:application:environment:
    NODE_ENV: production
    PLT_SERVER_HOSTNAME: "0.0.0.0"
    PLT_SERVER_LOGGER_LEVEL: info

Create Procfile:

web: npm start

Deployment​

# Install EB CLI
pip install awsebcli

# Initialize
eb init

# Create environment
eb create watt-app-prod

# Deploy
eb deploy

# Set environment variables
eb setenv DATABASE_URL="postgresql://..."

# View logs
eb logs

Google Cloud Run​

Deployment​

# Build and push to Container Registry
gcloud builds submit --tag gcr.io/PROJECT_ID/watt-app

# Deploy
gcloud run deploy watt-app \
  --image gcr.io/PROJECT_ID/watt-app \
  --platform managed \
  --region us-central1 \
  --allow-unauthenticated \
  --port 3000 \
  --memory 512Mi \
  --cpu 1 \
  --min-instances 1 \
  --max-instances 10 \
  --set-env-vars "NODE_ENV=production,PLT_SERVER_HOSTNAME=0.0.0.0,PLT_SERVER_LOGGER_LEVEL=info"

# Set secrets
gcloud run services update watt-app \
  --set-secrets "DATABASE_URL=database-url:latest"

Azure Container Apps​

Deployment​

# Create resource group
az group create --name watt-app-rg --location eastus

# Create Container Apps environment
az containerapp env create \
  --name watt-app-env \
  --resource-group watt-app-rg \
  --location eastus

# Deploy
az containerapp create \
  --name watt-app \
  --resource-group watt-app-rg \
  --environment watt-app-env \
  --image your-registry/watt-app:latest \
  --target-port 3000 \
  --ingress external \
  --min-replicas 1 \
  --max-replicas 10 \
  --env-vars "NODE_ENV=production" "PLT_SERVER_HOSTNAME=0.0.0.0"

Common Environment Variables​

Typical variables, when referenced by the application's configuration:

NODE_ENV=production
PLT_SERVER_HOSTNAME=0.0.0.0
PLT_SERVER_LOGGER_LEVEL=info
PORT=3000 (or platform-specific)

Health Check Endpoint​

Ensure your app has /health:

app.get('/health', (req, res) => {
  res.status(200).json({ status: 'ok' });
});