Getting Started
Dylaris runs Minecraft servers on your own hardware. A web panel drives a Go API, which drives one or more node agents, and each node talks to its local Docker daemon. A "server" in Dylaris is a managed Docker container with its storage, networking and lifecycle handled for you.
There are three ways to use it, and they are not tiers of the same thing. Pick the one that matches what you already have.
1. Self-host everything
Free, open source, Apache-2.0. You run the whole stack on a machine you control: a VPS, a home server, a NAS, a spare PC. Nothing talks to us, there is no account and no limit.
This is the complete panel: servers, modpacks, files, users, scheduled tasks, RCON, the profiler, the library. See Prerequisites.
Players reach your servers at your-ip:port. That works, it just is not pretty,
and it exposes the address of the machine.
2. Bring your own node
You keep the hardware, we run the control plane and the protected address. Your machine joins over an encrypted tunnel, so it needs no port forwarding and no public IP - a home PC behind a router works.
Players connect to a domain on :25565. Your real address is never exposed.
See Bring your own node.
3. Route only
You already run a server somewhere and do not want to move it. Point a protected address at it and change nothing else. See Route only.
Which one is for you
| You have | Start with |
|---|---|
| A VPS and you want full control | Self-host |
| A home PC or NAS and no static IP | Bring your own node |
| A running server you are happy with | Route only |
| You just want to look around | What you get |
Options 2 and 3 are paid, and both need your store account joined to your panel account before anything you buy takes effect. That is Connecting your account, and it is the step people miss.
What this costs
Self-hosting is free and always will be. The managed address is the part we charge for, because it is the part that costs us bandwidth and attack absorption. What you get draws the line precisely.