
Hey, welcome home.
The behind-the-scenes home for our servers. Come on in.
Continue with Discord →Our servers
All our shared worlds, with a little room to grow.
Glad you’re here.
Good friends, late-night builds, and a world to come back to.
Let’s keep our little corner running smoothly.

Pick a place to play
Dashboard
A little care for your shared world
Server resources
What keeps this world running

—
—
—
- Image
- —
- Persistent volume
- —
Files stay in your data volume when the container is recreated.
Meet you in-game
The connection details for this server
Make it feel like home
Configuration, plugins and all the little details
A few tweaks, a little personality
Open server.properties, edit text files or upload a plugin.
Edit files while the server runs. Apply changes with a supported plugin reload or a server restart.
Look after your world
Save a copy before your next big change
Download a backup
Archive the stopped server’s data volume.
Delete container
Requires a stopped server. Game data and databases are retained.
Live console
Recent output · refreshes every 5 seconds
Loading logs…
Type a command like say Hello World, list, or whitelist add Player. A leading / is optional.
File Manager
Your builds, plugins and settings live here.
Files can be edited and uploaded while the server runs. Use the plugin’s reload command when supported, or restart to apply changes. Uploads and downloads up to 1 GiB per file; text editing up to 8 MiB. Folders must be empty to delete.
| Name | Size | Modified | Actions |
|---|
Databases
MariaDB · compatible with MySQL clients and game plugins
Each database gets a generated password, persistent storage, 512 MiB memory and 1 CPU. Connections stay on a private Docker network; no database ports are published. Maximum 5 per server.
Network settings
Add, change or remove published ports. Host port is what players connect to; container port must match the game or plugin configuration.
Stop the server first. Saving recreates the container with your existing data, JVM settings and database connections, and leaves it stopped. Container ID and logs change. The game must be configured to listen on each container port; router forwarding is configured separately.
Blank bind address publishes on all host interfaces. Use 127.0.0.1 for host-local access. Port conflicts with other services may be reported when you start the server.