Skip to main content
Vibex ships ready-made release artifacts for the desktop, Android, and the self-hosted server. End users do not need to install Rust, Node.js, or pnpm: the desktop installers are self-contained. Every artifact lives on the same page:

Download the latest release

Open the GitHub Releases latest page and pick the artifact that matches your platform.
Vibex is still in a candidate phase: besides stable builds, releases may be published as -rc.N or -preview.N prereleases. The latest page always resolves to the newest one; use the full release list when you need a specific version.

​
Desktop

The Linux .deb depends on libvulkan1, libxcb1, libxcb-xkb1, libxkbcommon0, libxkbcommon-x11-0, libdbus-1-3, libfontconfig1, and an appindicator library (libayatana-appindicator3-1 or libappindicator3-1). Your distribution’s package manager usually resolves these dependencies for you.
The macOS and Windows installers are currently unsigned.
  • On macOS, Gatekeeper blocks the first launch: in Finder, hold Control and click the app icon, choose Open, then confirm once more. Alternatively, run xattr -d com.apple.quarantine /Applications/Vibex*.app.
  • On Windows, SmartScreen shows a prompt: choose More info → Run anyway.
These prompts come from the missing signing certificate, not from a problem with the installer. Every artifact ships with a matching .sha256 file, and SHA256SUMS collects all the checksums.

​
Release channels

Desktop installers carry a channel identity baked in at compile time, and different channels can be installed side by side without interfering: Each channel has its own SQLite database and configuration. Switching channels does not migrate data, so if you configured Agents and providers on RC, you need to configure them again after installing Stable. The channel is determined by the installer and cannot be switched inside the app.

​
Upgrades

The desktop has built-in signed automatic updates. In Settings → About → Software update:
  • The app checks once about 30 seconds after launch, then every 2 hours on the RC / Preview channels and every 6 hours on Stable.
  • The update manifest is verified with an Ed25519 signature, and the artifact is then verified with SHA-256. A failed check is never installed.
  • The install method depends on the package format: AppImage replaces itself in place; .deb, macOS .app, and NSIS hand off to the system installer and need an app restart afterwards.
Only builds from the same channel are accepted: an RC installer only looks at -rc.* versions. If automatic updates are unavailable, download the new installer manually and install it over the old one.

​
Android

The Android client is side-loaded from GitHub Releases:
  1. Download vibex-<version>-android-arm64.apk.
  2. Allow installs from that source in your system settings.
  3. Open the APK to finish installing (the app ID is ai.vibex.mobile).
Candidate builds cannot upgrade in place over one another. When no release key is configured, every RC release uses a one-time CI signing key, so different RCs are signed differently. Upgrading across versions requires uninstalling the old build first and then installing the new one. Uninstalling clears the locally stored pairing credentials, so you need to pair again.

​
iOS

There is currently no iOS build that can be distributed to end users. The only release artifacts are an unsigned simulator app bundle (ios-simulator.app.zip) and VibexFFI.xcframework, both of which need macOS and Xcode to run or integrate. On-device installs, TestFlight, and App Store distribution are not available yet.
To try it in the simulator, you need macOS, Xcode, XcodeGen, and the aarch64-apple-ios and aarch64-apple-ios-sim Rust targets, then build from source:

​
Self-hosting

Build your own server when you want to work across networks, or when you would rather not keep session data on an always-on personal computer:
  • Self-hosted headless runtime — vibex-server is an authoritative runtime with the same capabilities as your desktop, and it suits a server or an always-on home machine.
  • Self-hosted Relay — a relay that only forwards end-to-end encrypted frames. It performs no business authorization and stores no business data.
Both publish multi-architecture container images (linux/amd64, linux/arm64).

​
Build from source

If you need to change the code, or your platform has no ready-made artifact, see Build from source.

​
Uninstall

The uninstaller does not delete the data directory. To remove everything, read Privacy and recovery first, then delete the data directory for that channel by hand.