What you get

Dylaris is open core. This page is the honest split, so nothing on the pricing page surprises you later.

Free and yours, forever

The panel and everything behind it is published under the Apache-2.0 licence at github.com/Bartis-Dev/dylaris-platform. Clone it, run it, fork it, sell hosting with it. No key, no phone-home, no seat count.

That includes:

• The panel itself - the web interface, all of it
• Core - the API, scheduler, auth, RCON, live events
• Node - the agent that drives Docker on each machine
• The modpack builder and publisher, plus the Modrinth browser
• Beam, the desktop file-transfer client, for Windows and Linux
• Server lifecycle, sub-servers, scheduled tasks, the Spark profiler, custom tabs, the shared library, users and permissions, API keys

There is no crippled edition. What we run is the same code you can run.

If you fork it: some of this code talks to things you will not have

The repository is one codebase for two deployments - the one you run, and the one we run - so a fork comes with code for the half you are not running. It is all Apache-2.0 and none of it is a stub, but it is inert without the other side:

• Gateway integration. core/handlers/gateway*.go, core/services/hub_bridge.go and the link/route handling speak to a routing hub and regional edges that live in a separate, closed repository. Without one, these endpoints have nothing to talk to.
• Warp. node/warp_proxy.go is the client half of a WireGuard bridge whose daemon is part of the gateway. The proxy alone does not build a tunnel.
• Store and billing. core/handlers/store.go and the billing lifecycle exist so a storefront can provision and suspend tenants over a shared secret. With no storefront configured, none of it runs and every tenant reads as active.
• Bandwidth accounting. The traffic aggregator counts what the edges report. No edges, no numbers - the usage page reads zero, which is correct rather than broken.

You can delete all of it, and the panel still works. It is easier to leave it: it is gated on configuration that you simply do not set.

What we run, and charge for

The gateway is the part that gives a server a clean domain on :25565 with no open ports, absorbs attacks, and hides the address of your machine. It is a separate system: regional edges, a routing hub, the WireGuard bridge (warp) that pulls a machine behind NAT into the fleet, and the relay that carries file transfers without revealing where they land.

It is not open source today, and it is in testing. We have not settled what it becomes: a paid managed service, a licence for people who want to run their own edges, or both. If you want to run edges yourself or need details now, ask us - we would rather talk than guess.

Without it, Dylaris runs standalone in ip_port mode: players connect to your-ip:port. Everything else works exactly the same.

Beam, the desktop app

Free, and part of the open-core repo. It lists every server your account can reach - all of them, if you are an admin - and browses and transfers their files without an SFTP server anywhere in the picture.

How it connects depends on where you are and whether you run the gateway:

• On the same network as the node, it takes a direct certificate-pinned connection at full local speed.
• Self-hosted, from outside, it connects to the node's own address - the same one players already use, so nothing is exposed that was not already public. Still certificate-pinned, never plaintext.
• With the managed edge, that hop is replaced by a relay, and the node's address is never handed to the client at all.

Builds exist for Windows and Linux. There is no macOS build yet. See Files and Beam.

The mobile app

Planned, not built. It will be a paid, one-time purchase in the app stores - we are saying so now so nobody budgets for a free one. The price is not decided.

Self-hosters will be able to use it against their own installation; it is a client, not a subscription to us.

Summary