BRING YOUR SERVER
TO HOSTD
Upload your existing world, configs, mods, and plugins. We unpack them onto a fresh server (or wipe an existing one and replace) and bring it online. Zip or tar.gz, up to 10 GB. We snapshot first and roll back automatically if anything goes wrong.
Up to 10 GB per upload
Big modded worlds fit. Multipart upload streams direct to encrypted object storage - no panel proxy in the middle, so a flaky connection doesn't cost you the upload.
Auto-snapshot before we touch /data
Replacing an existing server's files takes a daily-retention backup first. If the unpack or restart fails for any reason we restore that snapshot automatically and tell you what went wrong.
Hardened extractor
Path-traversal, symlinks pointing at /etc, and zip-bombs are rejected at the panel layer before anything reaches your volume. Single-file 8 GB, 50 000-entry, and 50 GB-decompressed caps catch the obvious abuse.
Type-to-confirm on existing servers
Wiping a live server's /data is destructive. We require you to type the server's name verbatim and tick a fresh consent box before anything mutates.
Resumable uploads
Drop your wifi mid-stream? Reload the page. The browser remembers where it got to and offers to resume - only the parts you missed get re-uploaded.
Honest about scope
We unpack what you give us - we don't (yet) inspect your world for missing mods or wrong JDK versions. If your archive lacks a server.jar, the boot will fail loudly. Your eula.txt, server.properties, /world, /mods all need to be in there.
How it works
- 1
Pack your archive
Tar.gz or zip your existing /data folder - world, configs, mods, plugins. Anything your server boots from.
- 2
Upload
On the configure flow (new server) or your server's Transfer tab (existing). Direct browser-to-storage upload with progress and resume.
- 3
We snapshot + unpack
For existing servers we take a backup first, stop the container, wipe /data, then unpack your archive in its place.
- 4
Server boots
New server: comes online with your files. Existing server: restarted automatically once the unpack succeeds. Auto-rollback on any failure.
Works with every game we host
What this doesn't do (yet)
- We don't inspect what's in your archive. If it's missing a critical file (server.jar, eula.txt, level.dat) the server will fail to boot and you'll need to upload a corrected archive. A "what's missing?" inspector is on the roadmap.
- We don't auto-detect mod versions. Bring an archive that already runs locally; we won't fix mod-version mismatches for you.
- 10 GB is the cap. If your world is bigger you'll need to trim it (delete old player saves, prune unused chunks) or contact support for an exception.
- Live migration from a running source isn't supported. Stop your old server, package /data, upload. Bring-your-own-archive only.
Ready when you are.
Pick the path that fits.