Infrarust

Infrarust is a high-performance Minecraft reverse proxy written in Rust that routes players to the correct backend server by the domain or subdomain they…

  • Game Servers
  • Network Services
  • Tools & Utilities
Infrarust is a high-performance Minecraft reverse proxy written in Rust that routes players to the correct backend server by the domain or subdomain they connect with. It supports multiple proxy modes ranging from raw TCP relay to full Mojang authentication interception, auto-discovers Docker-managed Minecraft containers via labels, and ships with a built-in web dashboard providing real-time event streaming and log viewing. No per-server configuration files are required.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

60/100 Good

Maintained
100last commit 1 day ago
Popular
48242 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
201 serious finding, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
242
Open issues
7
Last commit
2026-11-20
Latest release
v2.0.0-beta.4
License
AGPL-3.0
Activity
steady

Checked yesterday - source: GitHub (Shadowner/Infrarust)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 49 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Use the Docker Compose example If using Docker, run Infrarust with port 25565 open, make your config file available inside it, and give it read-only access to the Docker socket (the file Docker uses to talk to its containers) so it can find your labeled Minecraft container. Without those parts, players cannot connect and Infrarust won't know where to send them. source
  • Tell Infrarust where players connect In the config, set domains to the address players will type and addresses to your real Minecraft server's host:port (for example, 192.168.1.10:25565). If these don't match, players either won't reach Infrarust or will be sent to the wrong game server. source
  • If running it without Docker If running it without Docker, run chmod +x (make it executable), move the file to /usr/local/bin, and verify it with infrarust --help. Without this, Linux won't let you start it and you may not be able to find the command. source
  • MCSM (Unraid template) setup Install the 'mcsm' Unraid template first so it creates the shared 'infrarust' Docker network. Copy config.toml from the MCSM repository (https://github.com/Niki2k1/mcsm/tree/main/Unraid/infrarust) into the Infrarust config folder before the first start. Point a DNS wildcard (e.g. *.mc.example.com) at your Unraid IP and forward port 25565. Enable Autostart for the Infrarust container in the Docker source

Fetched 49 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What Docker setup is required for Infrarust to auto-discover Minecraft containers?

Expose port 25565, make the Infrarust config available inside the container, and give it read-only access to the Docker socket. Infrarust then finds your labeled Minecraft containers; without those parts, players cannot connect and routing does not know where to send them.

How do I enable the Infrarust web dashboard and find its API key?

Add [web] to your config to run the built-in dashboard. It listens on port 8080, and the API key is in plugins/admin_api/config.toml.

What are the steps for installing the Infrarust binary directly without Docker?

Make the file executable, move it to /usr/local/bin, and verify it with infrarust --help. Without this, Linux may not let you start it or find the command.

Should I expect problems with intercepted proxy modes in Infrarust V2?

Infrarust V2 is still in active development. Expect bugs with the intercepted modes client_only and offline.

Can Infrarust plugins be closed-source or sold commercially?

Plugins built against infrarust-api can be closed-source and sold at any price. The Plugin Exception removes AGPL obligations from your plugin code.

Answers sourced from github.com, github.com, github.com, infrarust.dev

Community

Collected 49 days ago - public community threads