multivibe

Your providers. Your hardware. One AI gateway.

A free, self-hosted gateway for coding agents and AI apps.
Connect provider accounts, route around quotas, and run models on your own supported hardware.

Download MultiVibe Host · Run the gateway · Explore the API · Contribute

_{Current dashboard · Fictional data from the local demo instance}

✨ At a glance

Find your way

⬇️ Download MultiVibe Host

MultiVibe Host is the fastest way to run the complete, security-bounded local Host: gateway, dashboard, private device identity, provider agent, and managed model runtime. Official builds are published together in one verified release.

./install.sh

powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\install.ps1

docker pull ghcr.io/thibautrey/multivibe-host:latest

Updates and release verification

Native macOS, Linux, and Windows installations check an authenticated release feed and, by default, download and install an eligible stable release overnight (02:00–06:00 in the machine's local time), without confirmation. Each installation persists a random start between 02:00 and 05:00 to spread download traffic. Missed windows and busy Hosts defer to a later night, including after wake or restart. Downloads and installation require 30 minutes without requests, WebSocket turns, or jobs; installation rechecks activity after draining. Unknown activity fails closed. Explicit download/install actions bypass the overnight schedule, but installation still requires the quiet period. The updater drains new work, waits for active requests and model operations, verifies the archive with an embedded Ed25519 trust root, stages the replacement, and restores the previous version if the restarted Host does not pass its health check. The dashboard and macOS menu bar can switch between automatic installation, automatic download, and notification-only modes.

Containers never receive the Docker socket and never replace themselves. For generic Docker Compose, install the host-side updater from the verified Linux archive. Unraid users may use the platform's automatic application update mechanism with the published latest tag.

[!NOTE] If GHCR reports that the package is not found, no tagged Host release with Docker publishing has completed yet. Use an official native release or build from this repository instead of installing an unverified third-party image.

[!TIP] Native archives include signed checksums, SBOMs, and GitHub build-provenance attestations. See the verification and installation guide before deploying a Host on shared or production infrastructure.

📚 Documentation

The GitHub wiki contains the user guides, API reference, configuration, architecture, and historical reports.

• Quick start
• Dashboard
• Providers and onboarding
• API reference
• Plugin API reference and migration guide — sandbox, settings, model services, private SQLite storage, completion telemetry, and virtual routing
• Routing and aliases
• Configuration
• Local development

🤝 Contributing

Focused pull requests and issues are welcome. For UI changes, include a before/after description and screenshots. For behavior changes, add or update tests and report the validation commands you ran.

👥 Contributors

Thanks to everyone who has helped improve MultiVibe. This gallery is generated from GitHub's contributor graph and updates automatically.

View all contributors and their commits.

📄 License

The source code in this repository, including MultiVibe Core and its auditable provider-host agent, is licensed under the Apache License 2.0. The license includes an explicit patent grant and permits inspection, modification, and redistribution under its terms. It does not grant access to the hosted multivibe.cloud service, service accounts, credentials, customer data, or Pleiades Solutions trademarks beyond Apache-2.0 Section 6.

⭐ Star History

View the public star history.

AI release notes in GitHub Actions

Host (v*) and Core source (source-v*) releases generate notes before publishing. Configure these repository Settings → Secrets and variables → Actions entries:

The generator calls POST <base-url>/chat/completions. It sends committed release messages, GitHub's PR changelog, diff statistics and a bounded code patch to the configured provider. The key is available only to the notes step, never build jobs. No provider response bodies or credentials are logged. Configure an endpoint that is reachable from the GitHub runner and permitted to process this repository's code.

The baseline is the highest earlier published version in the same tag family whose commit is an ancestor of the new release. Stable releases exclude prereleases; prereleases can compare against earlier prereleases. Drafts, future versions and the current release are excluded. A first release uses its committed history. The full GitHub changelog and comparison link remain available beneath the AI summary. Inputs are bounded and marked when truncated; generated summaries may omit detail.

Download links are assembled from the actual release files, including multipart archives and reconstruction instructions. Unsupported/unbuilt targets are omitted. Existing container installation instructions remain in Host notes. Missing AI configuration, timeouts, invalid responses, or any other notes-generation failure produce a CI warning without failing the release job. The optional step has a three-minute timeout. On failure, Host releases use the original GitHub-generated notes plus container instructions; source releases use their original static release description. Failed or partial notes files are never published.

Run node --test scripts/generate-release-notes.test.mjs to validate without an API key. Both release workflows write release-notes.md outside the signed asset folder and pass it to gh release create --notes-file.