Created by

Understand your BEAM system.Instantly.

Voyager is a modern runtime inspector for Erlang and Elixir. Explore supervision trees, inspect processes and debug BEAM applications through a modern interface and MCP.

Why Voyager?

The BEAM runtime already provides some of the most powerful introspection tools available in any programming ecosystem - tools like Observer, recon and the Erlang runtime itself expose everything from supervision trees to memory usage.

The problem isn't the capabilities. Many of these tools have steep learning curves, outdated interfaces, or require switching between graphical apps, shell commands and docs just to answer a simple question.

Voyager brings these powerful capabilities together into a single modern interface - making runtime introspection faster, more approachable and easier to understand.

Node MetricsProcess StateErlang TracesVoyagerONE INTERFACE

Features

Everything you need to see inside a running BEAM node in one place.

F-01

Interactive supervision tree

Explore your application's supervision hierarchy through an interactive visualization. Understand how your system is structured and navigate thousands of processes with ease.

F-02
pid<0.312.0>mailbox4 msgsstatusrunningreductions18_402

Process inspector

Inspect process state, mailbox, dictionary, links and runtime information without jumping between shell commands.

F-03
MEMORYSCHEDULERS68%LOAD

Node overview

See the health of your node at a glance with memory usage, scheduler information, process counts and other runtime statistics.

F-04
local@nodeprod@10.0.4.1

Remote node support

Connect to local and remote BEAM nodes in seconds using Erlang distribution.

F-05
READ-ONLY

Built for production debugging

Designed to inspect running production systems safely while minimizing runtime overhead.

F-06
AppSupervisorWorkerPort

Learn OTP visually

Voyager makes abstract BEAM concepts tangible. Explore supervisors and processes interactively instead of reading docs or digging through source.

F-07

MCP integration

Expose Voyager through the Model Context Protocol, allowing AI assistants to inspect and reason about your running BEAM applications.

MCPLLM

See Voyager in action

A quick walkthrough of Voyager exploring a live BEAM system.

Coming soon

Future capabilities in development - queued for launch as Voyager expands its view into the runtime.

F-08

Tracing

Capture and inspect runtime events without modifying your application code. Follow process interactions and investigate complex production issues.

F-09

ETS Explorer

Browse ETS tables through a modern interface. Inspect table contents, metadata and statistics without writing shell commands.

F-10

Runtime Charts

Visualize memory usage, scheduler activity and other runtime metrics over time. Spot trends and anomalies snapshots can't reveal.

F-11

AI Assistant

A dedicated agent equipped with BEAM-specific skills, curated prompts and rich runtime context, so your favorite LLM reasons about your system.

F-12

Memory Allocators

Understand how memory is allocated inside the BEAM VM. Explore allocator statistics and identify potential memory bottlenecks.

F-13

Sockets Explorer

Inspect active network sockets, their state and associated processes. Gain deeper visibility into your application's networking layer.

F-14

Ports Inspector

Explore open ports and external connections used by your application. Understand how your node talks to the outside world.

Pricing

Individuals, small companies, and non-profits use Voyager for free. Larger for-profit organizations need a Company License.
Read the license.

For individuals and companies of up to 10 people

Free License

  • Full product access
  • Free 90-day evaluation period
Download

Required for companies of 11+ people

Company License

  • Same functionalities as Free License
  • Commercial use at company scale
  • Prioritized support
  • Private Slack or Discord
Contact us

FAQ

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:

  • an individual (including for commercial use),
  • a for-profit organization with up to 10 employees, or
  • a non-profit or not-for-profit organization.

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:

  • only your own personnel use Voyager,
  • the client gets no direct or indirect access to it,
  • Voyager itself is not resold, hosted for, or made available to the client, and
  • what you deliver is the results and work product, not Voyager or access to it.

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.

NEWSLETTER

Be among the first to try Voyager

Join the newsletter to receive development updates and sneak peeks of upcoming features.

We are Software Mansion

You might know us from Elixir Stream Week, Global Elixir Meetups, or from projects like Popcorn and Membrane. But that’s not all we do.

We help teams build exceptional software - from developer tools to production-ready applications. Let’s talk about how we can support your next project.