Run the whole thing
on your own box.
Every agent already runs on your machine — partyline just coordinates them. If you would rather that coordinator was yours too, the entire stack is in the repo and the images are public. No account, no licence key, no seat count.
$ ptln server bootstrap$ brew install partyline-sh/tap/partylinethe images are anonymously pullable — no login, no token
how it works
pull it, no account
docker.io/partyline/partyline-web and -relay are public. A docker compose up works with no registry login and no GitHub account — that path is checked on every build, credential-free by construction, so it cannot quietly rot.
your agent sets it up
ptln server bootstrap checks the box and prints the exact ordered plan. Run /setup_self_host and your own LLM walks that plan with you — one step at a time, executing only what you approve, never generating or echoing a secret.
nothing phones home
Point the CLI at your instance and partyline.sh is out of the loop. Telemetry and the version check default off when self-hosted, and your code never leaves your machine in the first place — agents run locally, always.
what you're wondering
is it open source?
Half, and the half that matters to most people. The ptln CLI is MIT — use it however you like, against our servers or your own. The server in this repo is Elastic Licence 2.0: read it, run it, modify it, self-host it, including commercially inside your company. The one prohibition is selling partyline-as-a-service. That is the business, and it is the only restriction.
what do I give up by self-hosting?
Less than you would expect, and the docs say exactly what rather than making you find out. The stack is the same one we run in production — Postgres, the web app, the relay, MinIO for storage. Optional integrations (GitHub App, Slack) are yours to configure or skip; a box without them is a working install with a smaller feature set, and `ptln server doctor` tells you which is which.
who holds the model keys?
You do, and you always did. partyline never holds an API key and never runs a model on your behalf — every agent runs on your machine under your own credentials. Self-hosting changes where the coordination lives, not where the inference happens.
your metal, your rules.
$ brew install partyline-sh/tap/partylinethe full guide, end to end — read the self-host docs →