MultiVibe exposes the same inference routes under /v1 and at the root for clients that expect either style. In the shipped Compose profile, the public :1455 socket is served directly by the native Rust edge; Node.js remains on loopback 127.0.0.1:1456 for the dashboard UI, OAuth, static assets, and the dashboard resource routes that have not yet migrated. Rust owns dashboard session authentication, the outer admin access guard, health, the read-only API key and application-policy inventories, and all public inference routes. Compatibility endpoints for Ollama- and LiteLLM-style discovery are also available.

macOS

Open the latest release and choose the disk image for your Mac:

• darwin_arm64.dmg for Apple Silicon (M1 or newer)
• darwin_amd64.dmg for Intel

Open the DMG, drag MultiVibe Host to Applications, then launch it. The app is signed with Developer ID, notarized by Apple, and runs from the menu bar. Its menu-bar label shows aggregate remaining OpenAI weekly and five-hour capacity when available. Opening it presents a native account overview with per-account quota windows, reset times, and health without exposing account tokens to the interface process.

Linux

Download the Linux amd64 release assets and follow NATIVE-MULTIPART.txt when the archive is split into several parts. After reconstructing and extracting the archive, run:

./install.sh

The installer verifies the release and supported NVIDIA hardware before it starts the Host. It installs for the current user and does not require root. On systems with a user systemd manager it also enables the signed automatic update timer. The timer checks hourly but the updater itself schedules one network check every 10 to 14 hours with a local random offset.

Windows

Download the windows_amd64.zip release, extract it to a temporary directory, then run PowerShell as the current user:

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

The installer verifies the complete bundle and the local NVIDIA driver before it changes the machine. It requires Windows amd64 and a GPU with compute capability 7.0 or newer, installs without administrator privileges, and registers a per-user Start Menu shortcut, login entry, multivibe:// protocol handler, and scheduled update task. The native Win32 tray menu starts and stops the Host and opens the local dashboard. Application files are kept under %LOCALAPPDATA%\Programs\MultiVibe Host; private state and logs remain under %LOCALAPPDATA%\MultiVibe.

PowerShell 5.1 or newer is required. The Windows updater verifies the signed feed and ZIP contents, stops only MultiVibe processes whose executable paths belong to the managed installation, and restores the previous version if the new Host does not pass its health check.

Docker and Unraid

The current Host release workflow publishes the same verified Linux bundle to GHCR as both an immutable version and the rolling latest tag:

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

For reproducible deployments, use the versioned tag or immutable digest shown in the matching latest GitHub release. Additional Docker Hub, Homebrew, NAS and Windows distribution packages are documented in the distribution guide. These channels require publication and platform validation before being advertised as available.

For Unraid, see the installation and Community Applications submission guide. The template is available for manual installation; a public store listing still requires Community Applications acceptance.

Docker Compose and Unraid setup are documented in Provider Host container.