Modpacks are first-class in Dylaris, in both directions: you can run one, and you can build and publish one, without leaving the panel.

Running a modpack as a server

Point the panel at a .mrpack and it becomes a running server. No manual unpacking, no matching the loader version by hand, no separate install step.

Browsing and installing mods

The Modrinth browser is built into the panel. Search, pick a version, install it into a server. It resolves what it needs rather than dropping a jar and hoping.

The builder

The builder is the part most panels do not have. You assemble a modpack in the panel - mods, versions, configs - and it produces a real, distributable pack.

From there you can:

Publish to Modrinth directly, with your own credentials
Keep beta channels separate from stable
Freeze a release so an existing pack keeps working while you keep editing
Let collaborators work on the same pack and stay in sync

The cross-check tells you when a mod in your pack does not match the loader or Minecraft version you are targeting, before your players find out.

Serving to the Technic Launcher

Dylaris speaks the Solder API, so a pack you build here can be consumed by the Technic Launcher without a separate Solder installation.

Delivery has three modes:

core - the panel serves the files itself. Simplest, and it works everywhere.
presigned - files live in your object storage and the panel hands out short-lived signed links. Your bandwidth stays out of it.
public - files are served straight from a public bucket.

One honest limitation: a private pack's zip can be loaded by anyone who has the link. That is inherent to how the Technic Launcher fetches packs, not something Dylaris chose, and no panel can fix it while staying compatible.

The library

Shared storage for jars, modpacks and assets, so the same file is not uploaded once per server. It can sit on local disk across several paths, or on S3-compatible object storage.