Deployment Overview
Two paths.
Cloud (managed)
Use the hosted Vibecontrols at app.vibecontrols.com + graphqlworkspaces.burdenoff.com. You install only the agent on your dev machines. Backend, web UI, tunnels, and all infra run in our cloud.
Pick this if: you want zero ops and are OK with data in our region.
Self-hosted
Run the full stack in your own infrastructure:
- Backend service module (the Vibecontrols backend) on your container platform
- Postgres + AGE extension
- Redis (cache + streams)
- Web app (the Vibecontrols web app) on S3 + CDN
- Optionally your own
frpsfor VibeTunnels
Pick this if: strict data residency, your own auth integration, or air-gapped requirements.
What's shared (regardless of mode)
- Agent install:
npm install -g @vibecontrols/agentruns the same way - CLI:
npm install -g @vibecontrols/cli - Both modes use OAuth2 device-code for user sign-in