render.yaml

# Render free-plan note: Background Worker services aren't available on the
# free plan, so the Celery worker runs inside the same container as the API
# (see backend/Dockerfile's CMD) instead of as a separate `type: worker`
# service. If you upgrade to a paid plan, you can split it back out by
# re-adding a `type: worker` service here with:
#   dockerCommand: celery -A app.celery_app worker --loglevel=info --concurrency=2
# and removing the `& exec` combination from the Dockerfile's CMD.

services:
  # FastAPI HTTP + WebSocket service. Also runs the Celery worker in the
  # background of the same container -- see the Dockerfile CMD.
  - type: web
    name: counterpoint-engine-api
    runtime: docker
    plan: free
    dockerfilePath: ./backend/Dockerfile
    dockerContext: ./backend
    healthCheckPath: /api/health
    envVars:
      - key: GROQ_API_KEY
        sync: false
      - key: GROQ_ORCHESTRATOR_MODEL
        value: openai/gpt-oss-120b
      - key: GROQ_CRITIC_MODEL
        value: openai/gpt-oss-120b
      - key: GROQ_EXTRACTION_MODEL
        value: llama-3.1-8b-instant
      - key: REDIS_URL
        fromService:
          name: counterpoint-engine-redis
          type: redis
          property: connectionString
      - key: NEO4J_URI
        sync: false
      - key: NEO4J_USER
        sync: false
      - key: NEO4J_PASSWORD
        sync: false
      - key: NEO4J_DATABASE
        value: neo4j
      - key: QDRANT_URL
        sync: false
      - key: QDRANT_API_KEY
        sync: false
      - key: QDRANT_COLLECTION
        value: counterpoint_evidence
      - key: ENVIRONMENT
        value: production
      - key: CORS_ORIGINS
        sync: false
      - key: LOG_LEVEL
        value: INFO
      - key: MAX_RESEARCH_CYCLES
        value: "3"
      - key: CONFIDENCE_THRESHOLD
        value: "0.8"
      - key: SCRAPE_TIMEOUT_SECONDS
        value: "20"
      - key: SCRAPE_MAX_RESULTS
        # Confirmed by production OOM crashes (not a guess): raising this to
        # 6 alongside concurrent fetching pushed the free instance over its
        # 512MB ceiling. Reverted to the proven-stable value. Page fetches
        # now block images/fonts/media/CSS at the network layer, which does
        # help, but not enough to afford both a higher count AND
        # concurrency at once -- raise this incrementally on a real
        # instance if you want to push it, not both knobs at the same time.
        value: "4"

  - type: redis
    name: counterpoint-engine-redis
    plan: free
    ipAllowList: []