Self-hosted
- Run with
npx @getpaseo/hubor Docker Compose - GitHub, Linear, Slack, Discord, schedules, and webhooks
- Provider apps you create and control
- Apache 2.0 open source
Automate coding agents and share daemons across your team. Every run executes on your own machines.
Run it yourself under Apache 2.0 or use the hosted service.
Triggers watch for events across your tools and start agents on your connected daemons.
Mentions in channels and threads.
@paseo-bot show me the latest P0 issues
Three P0 issues are open:
@paseo-bot create a pull request for the first one
Continued on macbook-pro. Opened getpaseo/paseo#1234 with a fix for the terminal writes.
Set up triggers in the browser or commit YAML files to your repository and deploy from the CLI.
Pick a daemon and working directory in the browser. Hub checks which providers, models, and modes the daemon offers as you configure a trigger.
name: slack-helpon: slack.mention: connection: acme-slack filters: from_users: [U01234567]run: target: daemon: devbox cwd: /workspace/app agent: provider: codex mode: full-access continuation: { mode: conversation } prompt: | Answer with hub.reply, then call hub.finish_execution. <user-prompt> ${{ paseo.prompt }} </user-prompt> outputs: slack.reply: max: 1 required: true
Architecture
Hub connects to the daemons you already run. Your team shares triggers and history while your code stays on your machines.
Automation sources
webhooks, mentions, and schedules
Hub
Self-hosted or hosted
the same RPCs the app and CLI use
Your connected daemons
direct connection or encrypted relay
Paseo clients
The hub.execute permission is off by default on every daemon and granted per machine.
Event triggers support sender allowlists and resource filters. You can set GitHub permissions for each step and scope the Slack and Discord tools.
Owners, admins, and members share daemons, triggers, run history, and routing outcomes.
Hub discovers the providers on each connected Paseo daemon. You can run Claude Code, Codex, OpenCode, Pi, and custom providers, including those from plugins.
Pricing
Run the open-source Hub yourself under Apache 2.0 or use the hosted service. Hub dashboard members and pending invitations count as seats.
npx @getpaseo/hub or Docker ComposeThe daemon stays a single process on one machine. Hub talks to daemons over the same RPCs that the app and CLI use, so anyone can build another service on top of Paseo.
Hub also has a different job. It receives public webhooks, handles team access, and runs multi-tenant. None of that belongs inside a single-machine daemon.
npx @getpaseo/hub or start it with Docker Compose and finish setup in your browser. The Apache 2.0 source is on GitHub, and the self-hosting guide covers production deployments.hub.execute permission. Enrolling a daemon does not enable execution by default, and you can revoke the permission from the machine at any time.These capabilities are not built yet, and are listed so you know where Hub is heading.
npx @getpaseo/hub or sign in to hosted Hub with a free account. Upgrade from Billing inside Hub when you need more runs or seats.