> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openbunny.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Fully remote

> Deploy all components on servers for always-on operation.

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

<Steps>
  ### Deploy the cloud

  Deploy to Vercel, Railway, or your hosting platform. Configure Supabase and run migrations.

  ### Deploy the service

  Deploy to a VPS (e.g., DigitalOcean, Hetzner). The service needs to stay running to process channels.

  ```bash .env theme={null}
  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
  ```

  Use a process manager like `pm2` or `systemd` to keep the service running:

  ```bash theme={null}
  pm2 start npm --name openbunny-service -- run start
  ```

  ### Configure push notifications (optional)

  Set up APNs (iOS) and FCM (Android) credentials in the cloud environment for mobile push notifications.
</Steps>

## 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