Skip to main content
Fully remote mode deploys the service on a VPS or server alongside the cloud application. Users interact exclusively through the cloud web UI or mobile app.

​
What you get

  • 24/7 channel processing without a local machine
  • Cloud web UI with Kanban board, team management, and calendar
  • Mobile app with offline-first sync and push notifications
  • Multi-tenant team isolation

​
Setup

1
Deploy the cloud
2
Deploy to Vercel, Railway, or your hosting platform. Configure Supabase and run migrations.
3
Deploy the service
4
Deploy to a VPS (e.g., DigitalOcean, Hetzner). The service needs to stay running to process channels.
5
BACKEND=remote
REMOTE_API_URL=https://your-cloud-url.vercel.app
REMOTE_API_TOKEN=obk_your-token-here
REMOTE_TEAM_ID=your-team-uuid
OPENROUTER_API_KEY=sk-or-v1-your-key
6
Use a process manager like pm2 or systemd to keep the service running:
7
pm2 start npm --name openbunny-service -- run start
8
Configure push notifications (optional)
9
Set up APNs (iOS) and FCM (Android) credentials in the cloud environment for mobile push notifications.

​
When to use this mode

  • Production deployments that need to run continuously
  • Teams where no one wants to run the service locally
  • When you need mobile app support with push notifications