Self-hosted
Free/ open source
- You operate Hub
- Provider apps you create and control
- Open source
Isee Hub
An optional service that sits above your daemons and gives them extra capabilities.
Run it yourself or use the hosted service.
Triggers, running on your machines
Mention the bot in GitHub, Slack, or Discord and an agent starts on your daemon.
GitHubIssues, PRs, and reviews.
SlackChannels and threads.
DiscordChannels and threads.
#engineering
M
moboudra09:41
@paseo-bot show me the latest P0 issues
paseo-botBot09:41
Three P0 issues are open:
- #2811Terminal output drops under load
- #2804Relay reconnect loop on Android after sleep
- #2799Worktree cleanup leaves stale branches
M
moboudra09:43
@paseo-bot create a pull request for the first one
paseo-botBot09:48
Ran on macbook-pro. Opened getpaseo/paseo#1234 with a fix for the terminal writes.
3 files changedtests passed
Runs the agents you already have
The Hub ships no agent of its own, so your team works with the providers, subscriptions, and skills already configured on your daemons.
Works with your existing infrastructure
The Hub connects to the daemons you already run, and your apps keep connecting to those same daemons.
Triggers and teammates
GitHub
Slack
Discord
Your team
Future integrations
webhooks and mentions
Hub
Self-hosted or managed
the same RPCs the app and CLI use
Your daemons
MacBook Pro
Hetzner VM
direct connection or relay
Isee apps
Desktop
Web
Mobile
CLI
Choose how to run Hub
Both options use Isee daemons to run agents on your machines.
Hosted
€15per seat / month
- Paseo operates Hub
- Managed GitHub, Slack, and Discord triggers
- Daemons run on your machines
- Same projects, workflows, and activity
FAQ
+What is the Hub?
A separate service that sits above your Isee daemons. You connect one or more daemons to it and it gives them GitHub, Slack, and Discord triggers, with collaboration features planned. Isee works fully without it.
+Why is it a separate service instead of part of the daemon?
The daemon stays one lean executable on one machine. The Hub talks to daemons over the same RPCs the app and the CLI use, so anyone can build their own hub on top of Isee.
It also has a different job. The Hub is meant to be exposed to the internet, shared with a team, and run multi-tenant. None of that belongs in a single machine daemon.
+Can I run it myself?
Yes. Run
npx @getpaseo/hub and complete setup in the browser. The source is available on GitHub, and the self-hosting guide covers more involved deployments.+What do I need to run it?
Node.js and a running Isee daemon. Hub guides you through connecting the provider apps you want.
+Is there a hosted version?
Yes. The hosted service runs the same Hub software you can self-host.
+What else is planned?
Not built yet, listed so you know where this is going.
- Provisioning daemons for your team
- Sharing settings and skills across a team
- More integrations
+Do I have to move my team to a new tool?
No. The Hub works in the Slack or Discord your team already uses, and on the daemons you already run. When the work gets serious you switch to the Isee app on those same daemons.
+Which agents does it run?
Whichever ones your daemons have configured, with your own subscriptions and skills. The Hub ships no agent of its own.
+Can the Hub run code on my machines?
Yes, on the daemons you connect to it and nowhere else. That is the whole point of triggers, and it's why access to the beta stays small and trusted.
+How do I get access?
You can self-host today or sign in to Hosted Hub to start a free trial.