 ██████  ███████ ███    ███ ██ ██    ██ ███    ███
██    ██ ██      ████  ████ ██ ██    ██ ████  ████
██    ██ ███████ ██ ████ ██ ██ ██    ██ ██ ████ ██
██    ██      ██ ██  ██  ██ ██ ██    ██ ██  ██  ██
 ██████  ███████ ██      ██ ██  ██████  ██      ██

Osmium is in active development — see what has shipped on the releases page

A terminal Minecraft server manager.

Create, run and maintain Minecraft servers and the mods they run — from a full-screen interface, or from a single command.

$ curl -fsSL https://osmiummc.com/install.sh | sh

A Minecraft server needs Java, which Osmium does not install. See Installation.

A terminal recording of a server being created, two mods installed with their dependencies resolved, and the server started.

Features

Server lifecycle

Create servers, run them, and inspect what they are doing, from one place.

Mod and plugin management

Modrinth-backed installs, with dependencies resolved and every download verified.

Version migration

Move between loaders and Minecraft versions without disturbing world data.

Reproducible configuration

A manifest and a lock file describe a server precisely enough to rebuild it.

Administration

Operators, bans, whitelists, backups and server properties, managed in place.

Local by design

No account, no telemetry, no background service. One static binary.

The Manage Servers screen showing the server list, the actions menu and a running server's console.

The Osmium create wizard asking which server software to use, each option with a one-line description.

Why Osmium

A Minecraft server is a jar, a directory of mods whose versions survive only in their filenames, and a process someone has to keep alive. Administering one by hand is workable until the version has to change, the server has to move, or somebody asks what is actually installed on it.

Osmium keeps the whole server described in two files and gives every operation one place to happen. The description is exact enough to rebuild the server elsewhere, file for file.