If you’ve ever had to debug a BEAM node you know it can be a painful process. Parsing raw data, or dealing with clutter often gets in the way of solving the actual problem.
We wanted to build something that makes this process easier for everyone. So we created Voyager - a tool designed to make navigating BEAM ecosystem easier.
Why you should use Voyager:
Easy connection: Connect to any node securely directly or via an SSH tunnel.
Real-time dashboard: Gain instant access to important metrics like memory breakdown, uptime, and IO in a clean UI.
Supervision tree: Explore your app’s structure and connections with an interactive graph.
Desktop app: A comfortable, dedicated app - not another browser tab.
MCP integration: Use AI to investigate your node data.
This is where we’re at, but there are more features on the way: tracing, ETS inspections, and runtime charts are already on the roadmap. We are currently in a pre-launch phase and looking for early adopters.
Hey, Voyager will be open source. We may offer paid add-ons in the future (for teams and enterprise use cases), but the core product will remain open source.
“Early access” just means we’re currently in a closed alpha while we gather feedback before the public release.
I replied to the email but got a delivery failure notification for the Google group.
I work locally on Linux (NixOS btw), and so will look out for when it’s available there. The project I’m most interested in monitoring/inspecting will be running on FreeBSD in production, but I expect that not to matter?
Looks nifty, I’ll give it a shot when it’s available on Linux. Can you expand on the stack it’s built with? My only concern is if it uses electron and possible NPM supply chain attacks esp as it connects to servers.
Thanks! Linux is on the roadmap - good to know there’s demand for it. There’s a chance that it will be released this week
We’re not using Electron - it’s based on Tauri using the OS-native webview. Inside it we run a LiveView release, so essentially all logic lives in Elixir on your local BEAM node and the browser layer is just a thin rendering surface. npm is build-time only for us (esbuild + Tailwind)
The whole flow of connecting to nodes is similar to Livebook.