Plug & Play
Download Voyager and install it like any other desktop app. There's nothing to configure, on your machine or on the node. If the node runs with distribution enabled, enter its name and cookie and you're ready to go.
Voyager is a modern desktop runtime inspector for Erlang and Elixir.Built for AI-driven debugging, designed for production, with no setup.
The BEAM runtime already provides some of the most powerful introspection tools available in any programming ecosystem. Voyager makes it all easy to reach and lets your AI agent do the digging.
Download Voyager and install it like any other desktop app. There's nothing to configure, on your machine or on the node. If the node runs with distribution enabled, enter its name and cookie and you're ready to go.
Connect to nodes on remote servers straight from Voyager. Enter the SSH host and node name, then Voyager sets up the SSH tunnel for you. Save the connection to reconnect in one click next time.
Voyager ships with an MCP server, on by default. Point Claude Code, Cursor or any MCP client at it, and your agent can inspect processes, read state and mailboxes, and search ETS tables on its own, through read-only, rate-limited tools.
Voyager is designed to inspect live production nodes with as little impact as possible. It only reads, keeps its work on the node small and bounded, and its source is public, so you can check exactly what it runs.
Pinpoint what's misbehaving on a live node.
Or let your AI agent investigate it for you.
Spot bottlenecks and memory hogs early.
Your agent can spot what's worth optimizing.
See the supervision tree, links and monitors as an interactive graph.
Ask your agent to explain what you see.
A quick walkthrough of Voyager exploring a live BEAM system.
Everything you need to look inside a running node, from memory and schedulers to processes and ETS tables.
Memory breakdown, system limits, schedulers and run queues, running applications and OTP versions, refreshed live.
An interactive graph of your supervision hierarchy, with links and monitors drawn as edges.
Rank every process by memory, reductions or mailbox size. The ranking runs on the node.
State, mailbox, dictionary, links, monitors, stacktrace and GC info for any process.
Every table with its metadata, paged records and key lookup. Agents can also search with match specs.
Follow function calls and messages without changing your code.
Live log events from the node, filtered by level and linked to the process that sent them.
Memory, schedulers and other metrics over time, to spot trends a snapshot misses.
Allocator statistics that show where the VM's memory actually goes.
Open sockets, their state and the processes that own them.
Open ports and the external programs and drivers your node talks to.
Connected nodes, the links between them and the traffic on each, so netsplits stand out.
From download to your first look inside a node in four steps, with nothing to install on the node itself.
Enter a node name and cookie, or an SSH host for a remote node. Save the connection for next time.
Browse the supervision tree, processes and ETS tables. See what's happening on the node right away.
Add Voyager's MCP server to Claude Code, Cursor or any MCP client, then ask it anything about your node.
Individuals, small companies, and non-profits use Voyager for free. Larger for-profit organizations need a Company License.
Read the license.
Everything you need to know about the Voyager license, commercial use, and pricing.
No. Voyager's source code is publicly available (source-available), but it is not open source under the OSI definition. Its use is governed by the Voyager License, which includes conditions not found in OSI-approved licenses.
The code is openly available, and individuals and small companies use it for free. To fund ongoing development and maintenance, larger for-profit organizations — those best able to afford it — pay for a Company License. This keeps the project maintained, updated, and healthy for everyone.
Functionally, nothing. It's the same program with the same code. A Company License is not a different product — it grants the right to use Voyager commercially above a certain company size, plus prioritized support scheme.
You are eligible for the Free License if you are:
You can also use Voyager for free while still evaluating whether it's a good fit and not yet using it commercially, regardless of your size.
The 10-employee threshold counts everyone working for your organization, including part-time employees and contractors.
You can use Voyager as an internal working tool to deliver consulting or professional services to a client (e.g. analyzing or optimizing their infrastructure), provided that:
Whether you need a Company License depends on your own company size, not the client's.
Yes, if it runs OTP 27 or later and Erlang distribution is enabled (a name and a cookie). Language does not matter: Elixir, Erlang, and Gleam are all supported. Need older OTP? Tell us what you run.
Yes. You may create public forks and modify the code to prepare contributions (pull requests) back to Voyager. What's not allowed is maintaining a fork as a separate, competing product, or selling/sublicensing your own derivative.
Yes, you may modify the code for internal use to fit your own use case. You may not sell, rent, license, or sublicense a derivative of Voyager, nor offer it as a hosted or "as-a-Service" product.
Yes. You can use Voyager for free while evaluating it, regardless of company size. Once you're no longer eligible for the Free License, the free evaluation period lasts 90 days — after that, if you're a for-profit organization above the size threshold and using Voyager commercially, you'll need a Company License.
Visit the contact page to request a Company License.
Once you cease to be eligible for the Free License, you have a 90-day period during which you can continue using Voyager for free — giving you time to obtain a Company License. You won't be in breach overnight.
Join the newsletter to receive development updates and sneak peeks of upcoming features.