macOS
Apple Silicon · macOS 13+
Requires macOS 13 or newer. Move the native app to Applications so future updates can replace it safely.
Download for macOSChoose your machine first. Each option keeps your trips on this computer; only how you open Voyalier changes.
Apple Silicon · macOS 13+
Requires macOS 13 or newer. Move the native app to Applications so future updates can replace it safely.
Download for macOS64-bit · EXE
Use the standard setup app. An MSI package remains available on the release page for managed installs.
Download for WindowsNode 24+ host · browser
Use the browser version on a supported Linux or Intel Mac. Check the setup guide before installing the required tools.
Open setup guideLatest stable installers are resolved from GitHub Releases. The fallback always opens the release page.
macOS is not notarized and Windows may show SmartScreen. Voyalier signs its updater artifacts and publishes SHA-256 checksums; the exact platform warning and optional manual checks are below.
Download the .dmg, open it, then drag Voyalier into Applications. Running
the app from Applications matters because the verified in-app updater needs a
stable installed location to replace it later.
On first launch, macOS may say it cannot identify the developer:
That exception is remembered. Later launches are normal. Voyalier currently ships for Apple Silicon on macOS 13 or newer. Intel Mac users may use the from-source route only if their system meets its Node.js and Rust prerequisites.
Download the setup .exe and run it. If SmartScreen displays Windows protected
your PC, choose More info → Run anyway.
An .msi is published on the same release page for group policy or package-tool
deployment. For one computer, the .exe is the simpler choice.
Build the browser development path locally. It is the same React interface, backed by Voyalier’s loopback-only Axum adapter and local SQLite workspace.
git clone https://github.com/udhawan97/Voyalier.gitcd Voyaliermake bootstrapmake devOpen http://127.0.0.1:5173. This route has no in-app updater; update it with
git pull, then rebuild. See Getting started for
requirements and a full first-run walkthrough.
Apple and Microsoft use paid developer programs and certificates to attach a verified publisher identity to packaged apps. Voyalier does not have that platform identity yet, and the macOS build is not notarized. The warning does not inspect or endorse what the app does; it tells you that platform publisher verification is missing. This is separate from Voyalier’s updater signature, which the installed app verifies before applying an update.
This guide is asking you to make one specific exception for a release you chose from the project’s GitHub page—not to weaken system security or ignore unrelated warnings. Signed and notarized installers remain on the roadmap.
Every stable release publishes SHA-256 checksum files:
On macOS:
cd ~/Downloadsgrep -qF "$(shasum -a 256 Voyalier_*_aarch64.dmg | cut -d' ' -f1)" SHA256SUMS-macos.txt \ && echo "Match — this is the file that was built." \ || echo "No match. Do not open it; download it again."On Windows PowerShell:
cd ~\Downloads$hash = (Get-FileHash Voyalier_*_x64-setup.exe -Algorithm SHA256).Hashif (Select-String -Path SHA256SUMS-windows.txt -Pattern $hash -SimpleMatch -Quiet) { "Match — this is the file that was built."} else { "No match. Do not run it; download it again."}This manual check is optional. After installation, Voyalier verifies downloaded updates against a cryptographic signature before installing them.
Start with Trips and the Blueprint, then use the focused guides for confirmations, visa preparation, offline packs, encrypted storage, optional AI, backup, and updates. If first launch stalls, Troubleshooting keeps the fixes in one place.