Paseo Hub

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.

Automations from every source

Triggers watch for events across your tools and start agents on your connected daemons.

Mentions in channels and threads.

Reply in the same thread to steer the running agent, or open the session in Paseo.Read Slack docs

Configure in the dashboard or ship as code

Set up triggers in the browser or commit YAML files to your repository and deploy from the CLI.

Dashboard and run activity

Pick a daemon and working directory in the browser. Hub checks which providers, models, and modes the daemon offers as you configure a trigger.

  • Triggers: Create, edit, or pause automations in form or YAML view.
  • Live checks: See which providers, models, and modes the connected daemon offers.
  • Run activity: Inspect deliveries, routing outcomes, outputs, and errors.
.paseo/triggers/slack-help.ymlYAML
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
$ paseo hub deploy --dry-run
$ paseo hub deploy

Architecture

Shared with your team, locked to your machines

Hub connects to the daemons you already run. Your team shares triggers and history while your code stays on your machines.

Automation sources

GitHub
Linear
Slack
Discord
Schedules
Webhooks

webhooks, mentions, and schedules

Hub

Self-hosted or hosted

the same RPCs the app and CLI use

Your connected daemons

MacBook Pro
Hetzner VM

direct connection or encrypted relay

Paseo clients

Desktop
Web
Mobile
CLI

Opt-in execution

The hub.execute permission is off by default on every daemon and granted per machine.

Scoped triggers

Event triggers support sender allowlists and resource filters. You can set GitHub permissions for each step and scope the Slack and Discord tools.

Team visibility

Owners, admins, and members share daemons, triggers, run history, and routing outcomes.

Runs the agents you already have

Hub discovers the providers on each connected Paseo daemon. You can run Claude Code, Codex, OpenCode, Pi, and custom providers, including those from plugins.

Claude Code
Codex
OpenCode

Pricing

Self-host or hosted

Run the open-source Hub yourself under Apache 2.0 or use the hosted service. Hub dashboard members and pending invitations count as seats.

Self-hosted

Free/ Apache 2.0
  • Run with npx @getpaseo/hub or Docker Compose
  • GitHub, Linear, Slack, Discord, schedules, and webhooks
  • Provider apps you create and control
  • Apache 2.0 open source
Self-host docs

Free

$0/ month
  • 50 agent runs a month
  • 1 seat
  • GitHub, Linear, Slack, Discord, schedules, and webhooks
  • Daemons run on your machines
Get started

Pro

$15per seat / month
  • Unlimited agent runs
  • No seat cap
  • Paseo operates Hub
  • GitHub, Linear, Slack, Discord, schedules, and webhooks
  • Daemons run on your machines
  • Same projects, workflows, and activity
Get started

FAQ

What is Paseo Hub?
Paseo Hub is a separate service that sits above your Paseo daemons. Connect one or more daemons to automate agent runs from GitHub, Linear, Slack, Discord, schedules, and webhooks, and share them with your team. Paseo works on its own without Hub.
Why is Hub a separate service instead of part of the daemon?

The 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.

Can I run it myself?
Yes. Run 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.
What do I need to run it?
You need Node.js or Docker and a running Paseo daemon. Hub walks you through connecting your daemons and provider apps.
Is there a hosted version?
Yes. The hosted service runs the same open-source Hub software that you can self-host. Hub dashboard members and pending invitations count as seats.
Can Hub run code on my machines?
Only on daemons where you grant the hub.execute permission. Enrolling a daemon does not enable execution by default, and you can revoke the permission from the machine at any time.
Do I have to move my team to a new tool?
No. Hub runs from GitHub, Linear, Slack, Discord, schedules, and webhooks on the daemons you already use. When you want to inspect or steer a run directly, open the live session in Paseo on desktop or mobile.
Which agents does it run?
Hub runs the providers configured on your connected Paseo daemons, including custom providers from plugins. Agents use the subscriptions, models, and skills on those machines.
What else is planned?

These capabilities are not built yet, and are listed so you know where Hub is heading.

  • Provisioning remote daemons for your team
  • Sharing settings and skills across a team
  • Additional provider integrations
How do I get started?
Self-host Hub with 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.
⌂ 换网址