#Hub

A daemon runs agents on one machine, for you. Clisbot Hub is the layer above your daemons. Connect your daemons to it, and it gives them what they cannot do on their own:

• Channels. Connect eight integrations: Slack, Telegram, Discord, Google Chat, Feishu/Lark, Zalo Official Bot, Zalo Personal and WhatsApp. Setup and capabilities vary by channel.
• Managed access. Grant Members and Teams access to Hosts or Projects, with allowed Agent configurations.
• Automations. Start agents from activity in GitHub, Slack, and Discord.
• Activity. A record of everything that arrived, what it matched, and what ran.

Use your personal channels to continue work away from your desk, or share selected Projects with a team. Your daemons run the agents; Hub routes requests and access. Bots and Group chats also work without Hub.

#Personal Hub or team Hub

	Personal Hub	Team Hub
Runs on	One of your own machines	A server your team operates
Sign-in	None. Your devices pair with a QR code	Members sign in with an account
To start	Bot Connect to a channel…, or clisbot bot start with a channel	Self-hosting; machines join with clisbot hub connect

Bot-only use needs no Hub. Channel setup starts the personal backend automatically; local web remains optional. Clisbot does not run a hosted Hub.

#Several Hubs at once

The Clisbot app keeps every Hub you add beside the daemons you connect directly. A common setup is a personal Hub for your own channels and your company's Hub for work:

   Personal Hub          Company Hub
     ┌───┴───┐           ┌────┴─────┐
  laptop   devbox    work laptop  build server

Daemons from both Hubs appear together in the app. Settings → Hubs chooses which Hub's settings you see. Each daemon belongs to one Hub.

#Start here

Quickstart → How it works → Enroll a daemon.

Then choose Channels and commands, Managed access, or Automations. Read Hub security before giving external requests agent authority.