Deployment Overview

Subscriberbot is deployed on the Burdenoff platform. Two paths exist: managed cloud (alpha + production) and local development.

Managed (cloud)

Use the hosted Subscriberbot at app.subscriberbot.com. The backend, web UI, GraphQL gateways, and everything else run as a fully managed cloud service — there is no infrastructure for you to operate, patch, or scale.

Environments:

Environment	Purpose	URL
Alpha	Pre-release validation	https://alphaapp.subscriberbot.com
Production	Live service	https://app.subscriberbot.com

Pick this if: you want zero ops and are OK with your data residing in the managed region (India).

Local development

Run the relevant services on your local machine:

• App shell: bun run dev in subscriberbot-app (port 5237)
• Backend service: bun run dev in wspace-subscriberbot-svc (port 3291)
• State services: docker compose up -d in wspace-subscriberbot-state (Postgres 5291, Valkey 6291)
• Gateways: run wspace-public-gateway (port 4003) and global-public-gateway (port 4000)

Pick this if: you are developing features, running E2E tests, or debugging.

What's shared (regardless of mode)

• CLI install: npm install -g @subscriberbot/cli runs the same way
• SDK install: bun add @subscriberbot/sdk / pip install subscriberbot-sdk
• Both modes use OAuth2 device-code for user sign-in
• Both modes use the same GraphQL schema and RBAC directives

CI/CD pipeline

push main → build-push (container image → registry via OIDC)
             ├─▶ hive-publish (staging + production schemas)
             └─▶ continuous delivery rolls the new image tag
                  └─▶ alpha, then production

CI authenticates to the container registry with short-lived OIDC credentials — no long-lived keys. Releases are tagged, so production rolls the exact image alpha validated.

Next steps

• Backend Service — local operations, monitoring, and health checks.
• Environment Selection — endpoint matrix for all environments.

Environment selection

All production operations target the production environment. Alpha is for pre-release validation. Local is for development only. See Environment Selection for endpoint details.