Belong.net Logo
Belong AI Deploy

Belong AI Deploy

Launch your own AI agent on your own cloud in minutes — sign in, pick your messaging apps, and deploy.

Overview

Belong AI Deploy sets up a private AI agent that runs on your own cloud account. Connect it to Telegram, WhatsApp, Slack, or another supported channel, then operate it through a Tailscale-private dashboard. You keep the infrastructure, data, and AI-provider relationship under your control.

Choose the path that fits how you work:

The hosted path is designed for setup without a terminal. The public self-host beta is a developer path and currently uses a source checkout plus four credentials. See Open Source for the exact boundary and support matrix.

The guided hosted deploy

  1. Sign in with DigitalOcean — one click, your server is ready
  2. Sign in with ChatGPT — one click, your AI is connected
  3. Connect Telegram — paste one token
  4. Click Launch — your agent is live in about 60 seconds

See the Quick Start for the step-by-step walkthrough.

How it works

flowchart LR;

subgraph You[Your devices]
  D[Phone / Laptop<br/>Tailscale]
end

subgraph Cloud[Your cloud server]
  DASH[Dashboard]
  AG[AI Agent]
  GW[Gateway]
  DB[(Private memory DB)]
  AG --- GW
  AG --- DB
  DASH --- DB
end

M[Telegram / WhatsApp / Slack]

D -- private network --> DASH
M -- optional webhooks --> GW

style You fill:#e1f5fe
style Cloud fill:#f3e8ff
  • Your dashboard and agent are private — reachable only through your own Tailscale network, not the public internet.
  • Messaging webhooks are optional and, when enabled, only open a single HTTPS route for the channel you chose.
  • Your agent stores long-term memory in its own private database, so it remembers context across conversations.

Hosted support

Cloud

ProviderAuthNew deployments
DigitalOcean (default)OAuthActive
OVHcloudSigned API tokenActive; production control plane
Google CloudOAuthActive beta
AWSAPI keyActive beta
ScalewayAPI keyActive beta
Microsoft AzureDisabled; retained compatibility only

See Cloud Providers for details.

AI

ProviderAuthDefault model
ChatGPT (default)OAuthGPT-5.5
ClaudeOAuthClaude Opus 4.8 (1M)
GeminiAPI keyGemini 3 Deep Think
KimiAPI keyKimi K2.6

Image generation and voice-note transcription ship preconfigured. See AI Providers.

Agent runtimes

RuntimeShapeStatus
Hermes Agent (default)Lean single-agent runtimeBeta
OpenClawMulti-agent gateway and browser runtimeBeta

Both runtimes are available in the public repository and the hosted wizard. Their channel support differs; the wizard shows only compatible combinations.

Messaging

PlatformSetup time
Telegram (default)~30 sec
Slack~3 min
WhatsApp~5 min

See Channels.

What you can do after deploy

Once your agent is live, open the management dashboard over your private network to:

  • Chat & review — read every conversation in a threaded view, search, and star important ones
  • Automate with tasks — trigger actions on keywords, schedules, or webhooks (welcome greetings, FAQ auto-replies, daily summaries, and more)
  • Tune your agent — set its personality/system prompt, switch models, and manage conversation cleanup
  • Run more agents — deploy multiple independent agents on one server, each with its own model and channels

Server sizes & cost

PlanAgentsApprox. costSpecs
Starter1–4~$24/mo2 vCPU, 4 GB RAM
Growing5–8~$48/mo4 vCPU, 8 GB RAM
Power9–16~$96/mo8 vCPU, 16 GB RAM

Most people should start with Starter — you can resize later from your cloud provider's dashboard. Your AI usage is billed by your provider (or covered by your existing subscription when you use OAuth).

Deploying programmatically

Teams that want automation instead of the sign-in wizard can provision agents with a REST API or a local MCP server (deploy from CI, manage a fleet from your editor, or batch-launch an agent per customer). See Enterprise & API.

Next steps

Copyright © 2026