# 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 connect with. It is open source and self-hosted, installable on Unraid.

Canonical page: https://ourlocalhost.com/app/6780/infrarust

## Description

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.

## Health score

60/100 (Good), based on 4 of 5 factors.
- Maintained: 100 (last commit 1 day ago)
- Popular: 48 (242 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)
- Security check: 20 (1 serious finding, CI, tests)

## Security check

1 serious finding: Uses wasmtime 49.0.1, which has a known critical vulnerability.
Automated checks on commit 92d8319, 5 Nov 2026. Not an audit.

## Links

- Unraid: https://ca.unraid.net/apps/infrarust-0vzen9h0y03sih?q=infrarust
- GitHub: https://github.com/Shadowner/Infrarust
- Official website: https://infrarust.dev/
- Documentation: https://infrarust.dev/configuration/

## 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.

---
Source: Our Local Host (https://ourlocalhost.com/app/6780/infrarust), the self-hosted and open-source app directory.
