Self-hosting

The Partybus core is open source under Apache-2.0 and runs with no proprietary dependencies. Own your data end to end.

Local development

terminal

git clone https://github.com/partybus-ai/partybus
cd partybus
npm install
npm run storage:up      # local MinIO object storage
npm run dev:local       # dev auth provider, no external IdP

Open http://localhost:3000 and create a developer token under Settings.

Configuration

Everything is driven by environment variables. The essentials:

AUTH_PROVIDER - dev locally, auth0 (or your own adapter) in production.
STORAGE_MODE - local (MinIO) or aws (S3-compatible).
S3_BUCKET, S3_ENDPOINT - your object store.
DATABASE_URL - optional Postgres control plane; in-memory fallback if unset.

Production image

The Dockerfileproduces a standalone Next.js server image. Point storage at your own S3-compatible endpoint and supply your IdP's configuration.

terminal

docker build -t partybus .
docker run -p 3000:3000 --env-file .env partybus

Sovereign / air-gapped

For fully isolated environments, swap the auth adapter for your IdP, bring your own KMS, and run object storage inside your boundary. No data ever has to leave your network. The managed cloud features (billing, dedicated tenancy control plane) live in a separate repo and are not required to run the product.