Skip to content
BETA · SELF-HOST IT TODAY

Run Minecraft on
hardware you own.
Free and open source.

The whole panel is free and open source: servers, modpacks, files, users, scheduling, profiling. Run it on a VPS, a NAS or the PC under your desk, and nothing phones home. Want a clean domain instead of an IP? Our managed edge adds no open ports, no SRV record, always :25565. Take a free subdomain from us, or point your own domain at the edge with a CNAME and a TXT record and keep your branding - that part is a paid service, and it is optional.

Open the PanelView the source
Self-host

Run the open-core stack on your own box: Core, Node and Panel. No phone-home, your data, free to run today.

Read the docs →Deep dive
Bring your own node

Got a server or a gaming PC? Bring the hardware to our managed Minecraft edge. No router config and no public IP needed, so it works behind CGNAT too.

How BYON works →
No SSH requiredOne docker compose up -d on the machine, then everything happens in the panel.REST API + per-user keysLinux-native, runs on WindowsWindows/Docker Desktop is perfect for a BYON home server on your gaming PC (you and your friends). For production, Linux is recommended: hard disk limits (they need xfs/ext4 project quotas) and CPU pinning are Linux-only. BYON needs x86_64, no ARM.Open source, self-hostableThe panel, Core, the node agent and the Beam desktop app are published under Apache-2.0 today. Self-host all of it. The managed edge is the one closed part.
Where the line is

Two halves. Only one of them is ours.

Free and yours

The panel, all of it

Published under Apache-2.0. Install it on a VPS, a NAS or the PC under your desk and keep it. No account, no key, no phone-home, no feature held back.

  • Servers, sub-servers, console and RCON
  • Modpack builder, publisher and Modrinth browser
  • Files, backups, the shared library
  • Users, granular permissions, scoped API keys
  • Scheduled tasks, live metrics, the Spark profiler
  • The Beam desktop app, Windows and Linux

Players connect to your-ip:port, and you forward a port like anywhere else.

We run this

The protected address

A clean domain on :25565 in front of your machine. This is the part that costs bandwidth and filters traffic, so it is the part we charge for. It is optional.

  • No open ports, no public IP needed
  • Your real address is never visible to a player
  • Junk and malformed connections dropped at the edge
  • Your own domain: a CNAME plus one TXT record
  • Works behind NAT and CGNAT, so a home PC qualifies

Closed source. DYLARIS is a hosted service: the platform software is public on GitHub, we run the gateway, and a self-serve offering is not planned. Ask us.

Integrated modpack builder Modrinth
Modpack Workflow

Browse. Build. Publish. Play.

Search Modrinth from inside the panel, drop mods into a versioned modpack, and publish it to Modrinth or export it as an .mrpack, all from one project. Then create your server straight from that modpack, and players launch it right from the Modrinth launcher to play.

One panel, end-to-end modpack pipeline

Cached Modrinth proxy, in-panel mod browser, versioned modpack builder, draft/beta/release channels, collaborator sync, AES-encrypted PAT storage, and an .mrpack server installer with host allowlist and override handling. Publish to Modrinth, export an .mrpack, and deploy to your own fleet from the same project, no jumping between tools.

In-Panel Mod Browser

Search the full Modrinth catalogue from inside Dylaris. Cached proxy keeps results fast, supports loader and version filtering, installs with a click via the Node queue.

Search Modrinth without leaving the panel

Versioned Modpack Builder

Build modpacks like a real release pipeline: draft, beta, release. Frozen versions are immutable. Collaborators sync to Modrinth's member API automatically.

Beta channels, frozen releases, collaborator sync

Modpack-as-a-Server

Take any Modrinth .mrpack, yours or someone else's, and deploy it as a fully managed server. Host allowlist, override handling, automatic loader chaining.

Your modpack and your server, same project
Capabilities

Everything you need, in one panel.

Modpacks, server lifecycle, scaling, operations, all first-class and native to Dylaris.

Free and yours

Modrinth Mod Browser

Search the full Modrinth catalogue by loader and MC version and install with one click. A cached proxy keeps results fast.

Modpack Builder

Build modpacks as a real release pipeline (draft, beta, release) with frozen, immutable versions.

Spark Profiler

Start and stop Spark profiling from the panel; report URLs are captured from the console over SSE and a history tab keeps every run.

Multi Sub-Server Slots

One server entry holds many sub-servers (vanilla, survival, creative, modded) and switches between them in place.

Live Console & RCON

An in-panel RCON terminal with full command access, streamed live over SSE, plus an external API surface for bots and automation.

Player Management

Kick, ban, op and pardon from the panel. Online sessions are tracked live over SSE, so the list never lies.

File Browser

A native per-server file browser bound to the server UUID. Edit, upload, move and download over SFTP or Beam.

Scheduled Tasks

Cron-style restarts, commands and broadcast messages per server. Set them once with a live cron preview and forget.

Docker-Isolated Servers

Every server runs in its own container with hard RAM and CPU limits, hard disk limits on Linux with xfs/ext4 project quotas, and per-server Java (8, 17, 21, 25). One noisy server can never starve another.

Beam Desktop App

A free, open-source desktop client for server files (Windows and Linux). On your own network it connects straight to the node at full speed; elsewhere it relays without ever exposing the node IP. No port 22.

Backups & Restore

Scheduled or on-demand backups with include/exclude patterns, retention limits and one-click restore. Back up a whole server or just one sub-server.

Granular Permissions

Over 70 fine-grained capabilities across server, owner and panel scopes. A build-time test proves every protected endpoint is gated, and sessions and API keys run through the exact same check.

We run this

The gateway exists so that nobody ever learns where your server actually is. Players reach it on :25565 at our edge, and Beam moves your files through the same gateway instead of an open SFTP port - from the internet both are relayed, so the machine behind them keeps every port shut and never appears in a DNS record. Edges run several to a region, which is what spreads the load and what lets players keep playing while we update one.

It is closed source. DYLARIS is a hosted service: the platform software is public on GitHub, we run the gateway, and a self-serve offering is not planned. Ask us if that matters to your plans. Without it, everything above still works - players just connect to your-ip:port.

Edge Routing & Custom Domains

Multi-region edge routing with TLS termination and custom domains. Players connect to a clean address, always ending in :25565, with no exposed backend IP.

Multi-Region Fleet

Nodes and edges announce their own region, and scheduling keeps servers and live sessions inside it, from one VPS to a global fleet.

Minecraft-Aware Edge (Layer 7)

The edge reads every connection’s Minecraft handshake first. Garbage, malformed packets, stalled connections and requests for addresses that do not exist are dropped there, and each IP is rate-limited, so what reaches your server is well-formed Minecraft traffic for its own address.

Warp NAT Bridge

Pull NAT’d home machines and off-site VPSes into the fleet over a hub-and-spoke WireGuard overlay: self-enrolling, no port forwarding.

Relayed File Transfer

File traffic takes the same road as players: Beam moves it through the gateway instead of an open SFTP port, so the node keeps 22 and 25520 shut and never appears in a DNS record.

Seamless Edge Updates

Run more than one edge in a region and live sessions move to a sibling before one restarts. Players keep playing through an update instead of being kicked to the server list.

Bring your own node

Run a server from your closet,
your VPS,
your friend's basement.

Got a server or a gaming PC but don't want to wrestle with ports, firewalls and networking? Bring the hardware, Dylaris does the hard part. Your machine joins the fleet and the panel treats it like any other node, even behind NAT with no public IP.

Under the hood it is Warp, a hub-and-spoke WireGuard overlay. Nodes self-enroll with a scoped key and come online automatically. No manual key exchange, no tunnels to babysit.

You bring
Any machine
Networking
No router config
Setup
One Docker stack
See BYON pricing
Fleet Topology
Home PC
behind NAT
VPS
off-site
DC Node
datacenter
WireGuard tunnel
one fleet · one view

From your machine to play.yourserver.com

Connect your node

Start the Dylaris kit (warp, node and link, kept updated by watchtower) with one docker compose up -d on a Linux x86_64 PC, VPS or a friend's box, or on Windows through Docker Desktop. It dials out over an outbound-only tunnel: nothing to forward, nothing to expose. Works behind NAT and CGNAT.

No open ports · outbound only

Create servers in the panel

Spin up Vanilla, Paper, Fabric, Forge, NeoForge or a full modpack from one web panel. Start, stop, edit files, run RCON, schedule restarts, full control, no SSH.

Full control, zero terminal

Players just connect

Take a free subdomain of ours, or point your own domain with a CNAME plus a TXT verification record. No SRV records, no IP addresses, no port numbers. The address always ends in the default :25565.

No SRV, always :25565
No open ports
Outbound-only
Behind NAT / CGNAT
No SRV record
No IPs, no ports
Always :25565
Your domain or ours
Layer 7 Minecraft filter
Full control in-panel
Easy setup
Your hardware
No lock-in

It stays your machine

Dylaris adds just three lightweight containers: the Node daemon, the Link outbound tunnel, and the Warp VPN. The Node then spawns your Minecraft server containers on top. Everything else on the box keeps running untouched, you keep full control, and nothing listens on a public port. Plain Docker is enough for a node or two; Docker Swarm is optional and only pays off when you self-host a larger fleet and want the full multi-node setup.

Node
daemon · spawns MC
Link
outbound edge tunnel
Warp
WireGuard VPN
The edge

A Minecraft-aware edge in front of your server

Players connect to the edge, never to your machine. The edge understands the Minecraft handshake, so it can tell a player from noise before anything is forwarded.

Filtered at layer 7

The edge reads the Minecraft handshake of every connection before your server sees a byte of it.

  • Garbage and malformed packets are dropped at the edge
  • Connections for addresses that do not exist never reach anyone
  • Connections that stall before the handshake are cut after 10 seconds
  • At most 10 new connections a second per IP, and an address that floods is blocked for a minute

Your IP stays private

Your machine dials out to the edge. Nothing on it listens for the internet, so there is no address a player could find, share or attack.

  • Your home IP or node IP is never shown to players
  • No open ports, no port forwarding, no router settings
  • Large volumetric attacks are filtered by the data centres the edges run in

Not Velocity, not BungeeCord

The edge is not a server-network proxy. It is a handshake-aware tunnel that sits in front of whatever you run.

  • It does not log players in or switch them between servers
  • Login and encryption stay between the player and your server
  • Works with Java Edition servers: Vanilla, Paper, Fabric, Forge and NeoForge
  • Already run Velocity or BungeeCord? Keep it, the edge goes in front of it

Behind CGNAT? You can still host.

Many providers no longer give you a public IPv4 address: CGNAT, DS-Lite, fibre and cable plans, Starlink, mobile and 5G internet. Port forwarding cannot work there, which is why a home Minecraft server usually fails. Dylaris does not need an open port or a public IP: your machine connects out, and players join on a normal address ending in :25565.

Hosting behind CGNAT →
How we compare

vs. conventional hosting

Most setups expose a public IP for every server. With the optional Dylaris edge, backends stay portless behind an outbound-only tunnel.

ApproachNo exposed IPBehind CGNATMC protocolRolling updatesFull panelDocker-native
DYLARIS✓✓✓✓✓✓
Traditional Panel Hosting
Each server needs a public IP and an open port, and that IP is where attacks land.
✗✗✗✗~~
BungeeCord / Velocity
A server-network proxy you run yourself. Still needs a public IP and an open port. The Dylaris edge can sit in front of it.
✗✗✓✗✗✗
Cloudflare Tunnel
TCP tunneling only. No Minecraft parsing, players need a client-side tool, no panel.
✓~✗✗~✗
Pterodactyl / Pelican
Panel + Docker orchestration, but servers stay fully exposed.
✗✗✗✗✓✓
Ngrok / frp
General TCP tunneling. No protocol awareness, no filtering, no panel.
✓✓✗✗✗✗

The portless edge is optional. Run Dylaris on plain ports today, add the edge when you want it.

Under the Hood

Service-oriented. Single panel.

Core API, Node agents, Gateway routing, Beam file relay, Hub coordination, Warp NAT bridge. Each piece is its own service, each one cleanly composed, and from your view, it's still just one panel.

Control PlaneAPI · scheduling · panel

Core

API, Auth, Scheduling, Modpack Service

43,356 Go
~22 MB img · 60-120 MB RAM

Node

Docker Agent, Server Lifecycle, RCON

10,695 Go
~20 MB img · 40-80 MB RAM

Panel

Next.js Web Console, SSE-driven

26,005 TS
~200 MB img · 80-150 MB RAM
Data Planerouting · file transport · tunnels

Gateway

Edge Routing, TLS, Custom Domains

5,604 Go
~20 MB img · 40-70 MB RAM

Hub

Routing State, Leader Election

1,528 Go
~20 MB img · 20-40 MB RAM

Beam

P2P File Transfer + Desktop Client

2,919 Go
~20 MB img · 15-35 MB RAM

Warp

WireGuard NAT Bridge for Off-Site Nodes

895 Go
~24 MB img · 15-30 MB RAM

Run the Core, Node and Panel on a single VPS and you have a working host. Add Gateway and Warp when you grow into a multi-region fleet, attach Beam when ops teams want bandwidth-capped file transfer, the panel is the same panel.

Line counts from source; image sizes and memory are rough estimates.

Backend
Go
Native-compiled, no runtime overhead: fast, tiny static binaries. One workspace across Core, Node and the edge.
Panel
Next.js + Tailwind
A modern, typed stack for a clean, fast UI. App Router, SSE-driven, no page reloads.
Data
Postgres + Valkey
Postgres for durable state, TimescaleDB for time-series metrics, Valkey (Redis-compatible) for queues and live streams.
Orchestration
Docker + Swarm
Every server in its own container: isolated, resource-capped, no host pollution. One host or a full Swarm, same agent.

Every service, line-count, image size and protocol, laid out with diagrams and code.

Read the full technical deep dive
WHERE WE ARE

Open source today.
Beta, honestly.

The panel, Core, the node agent and the Beam desktop app are published under Apache-2.0, right now, not after a beta. Clone it, run it, fork it. No waitlist, no key, no phone-home. It is still beta, so expect the odd rough edge while we harden it with real users. Everything below is already shipped, not a roadmap promise.

Core API + Server Lifecycle
Done
Docker + Multi-Node Swarm
Done
Modrinth Browser + Modpack Builder
Done
Modpack-as-Server + Spark
Done
RCON + Player Management
Done
Gateway + Beam + Warp
Done
Live SSE + Custom Tabs
Done
First-Run Wizard + Recovery
Done

Bedrock Edition is under evaluation, with no date. Bedrock and other UDP traffic (Geyser, Simple Voice Chat) do not pass through the edge today.

Panel · free

Yours under Apache-2.0

The panel, Core, the node agent and the Beam desktop app are published today. Every feature, no crippled edition: what we run is the code you can run. Your hardware, your data, no strings.

Gateway · Closed

Gateway as a service

The Minecraft-aware edge and NAT bridge are a service we operate, and the part that is genuinely hard to self-run. Closed source. It stays a service: you bring a node or we route to the server you already have, and we run the edges. Running your own is a contract for larger customers with their own ops team, never a self-serve tier. Ask us if that matters to your plans - we would rather talk than have you guess.

App · planned

Mobile app

Planned, not built. Pick our hosting or your own self-hosted domain right at login, the way Bitwarden lets you choose your server. It will be a paid, one-time purchase in the app stores - saying so now so nobody budgets for a free one. Price undecided.