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, uploaded from your machine or fetched from a Dropbox or Google Drive link, with imports up to 80% of your plan's disk. We snapshot first and roll back automatically if anything goes wrong. Already paid up at your old host? Raise a ticket once you land and we will take what is left of it off your bill.
Sized to your plan
Imports scale with your plan: up to 80% of its disk. Multipart upload streams direct to encrypted object storage and resumes from the last uploaded part, so a flaky connection doesn't cost you the upload. Or paste a Dropbox or Google Drive link and we fetch it for you.
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 sanity-check, we don't deep-inspect. We verify the archive plausibly contains a world or server for your game and reject it loudly if not, but we can't catch every missing file. Bring an archive that already runs locally.
- We don't auto-detect mod versions. Bring an archive that already runs locally; we won't fix mod-version mismatches for you.
- The cap is 80% of your plan's disk. The rest is headroom for server files, logs, and growth. If your world is bigger, pick a plan with more disk or trim the world first.
- 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.