render.yaml

# Render blueprint for the operator console.
#
# One service, one disk. The console is the only part of Interlock that
# belongs on a network: the proxy speaks MCP on stdio and runs wherever the
# agent runs, which is the operator's machine or their own infrastructure, not
# ours.
#
# The disk is the point. The ledger is the exactly-once guarantee, and a
# container filesystem that resets on deploy would throw it away — every
# restart would look like a fresh install with no memory of what it had already
# paid. `synchronous = FULL` fsyncs to this volume on every state change, so it
# must be a real disk and not a tmpfs.
services:
  - type: web
    name: interlock-console
    runtime: node
    plan: starter # the free plan has no persistent disk, which this cannot do without
    region: singapore
    buildCommand: corepack enable && pnpm install --frozen-lockfile && pnpm run build
    startCommand: node packages/gate/dist/bin/interlock-console.js --mandate ./examples/mandate.yaml --host 0.0.0.0

    # 503 until boot recovery has settled intents left in flight by a killed
    # predecessor. Render will hold traffic off the instance until it is ready,
    # which is exactly what the code path is for.
    healthCheckPath: /health

    disk:
      name: interlock-ledger
      mountPath: /var/interlock
      sizeGB: 1

    envVars:
      - key: NODE_VERSION
        value: 22.13.0
      - key: INTERLOCK_DB_PATH
        value: /var/interlock/interlock.db
      # Generated by Render and never in this file. It is the only credential
      # the console has, and it guards every decision the ledger holds.
      - key: INTERLOCK_CONSOLE_TOKEN
        generateValue: true
      # Deliberately absent: RAZORPAY_KEY_ID and RAZORPAY_KEY_SECRET. This
      # deployment reads a ledger; it does not hold a rail credential, so a
      # compromise of the public surface cannot move money.