Direct answer
Self-hosting means you manage the machine, internet connection, security and backups. A Minecraft hosting provider normally supplies the hardware, network and often a control panel, but you still maintain your world, plugins and player permissions.
Step-by-step procedure
- Estimate monthly cost using power, hardware, bandwidth, backup storage and the time needed for maintenance, not only advertised RAM.
- At home, check CGNAT, your router, upload bandwidth and whether the machine can remain online. With a host, ask about CPU allocation, storage, backup access and console access.
- Request a test server or trial where available; import a copy of the world and measure MSPT during representative play.
- Verify you can export complete files and databases before committing to either setup.
Common mistakes and trade-offs
Neither arrangement guarantees good TPS. Hosting labels such as “unlimited slots” cannot overcome per-tick CPU limits; home hosting exposes your network and requires reliable patching.
How to verify it worked
Perform a restore test, connect from outside the network, review logs and confirm that a restart recovers the server without manual intervention.
Version and platform differences
If you need a publicly reachable Java server, TCP connectivity and NAT limitations are important; Bedrock/Geyser access may also require a UDP listener.
Official references
These sources were checked for the current MSH revision. Version-sensitive details should always be confirmed against the project documentation for the release you run.
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.