Skip to main content

Deployment Overview

Two paths.

Cloud (managed)​

Use the hosted Vibecontrols at app.vibecontrols.com. You install only the agent on your dev machines. The backend, web UI, tunnel brokering, and everything else run as a managed service — there is no infrastructure for you to operate, patch, or scale.

Pick this if: you want zero ops and are OK with data in our region.

→ Cloud setup

Self-hosted​

Run the full stack in your own infrastructure:

  • The Vibecontrols backend API on your own container platform
  • A relational database and a cache/event service (versions and sizing are specified in the release package)
  • The Vibecontrols web app on your own object storage + CDN
  • Optionally your own frps server for VibeTunnels

Pick this if: strict data residency, your own auth integration, or air-gapped requirements.

→ Self-hosted setup

What's shared (regardless of mode)​

  • Agent install: npm install -g @vibecontrols/agent runs the same way
  • CLI: npm install -g @vibecontrols/cli
  • Both modes use OAuth2 device-code for user sign-in

Next steps​