GTPS hosting that starts in a browser

A host does not make your private server for you. It gives you somewhere to run the one you build, and the tools to manage it. Concretely, that means:

• A server that stays online. It runs on remote infrastructure, so it keeps going while your computer is switched off, asleep, or on a different network.
• A live console. Server output, in your browser, as it happens. Read errors and follow what the server is doing without attaching to a terminal.
• A file manager. Upload worlds, plugins and textures without setting up an FTP client or learning a file transfer protocol.
• Backups. Configuration snapshots, so a bad plugin edit or a mistimed change is not the end of your world.
• A marketplace. Community-made worlds and plugins you can install in a click instead of sourcing them one download at a time.

The parts that make a host good are mostly the parts that are not exciting: how quickly the server restarts when it needs to, whether your world is actually backed up, and how hard it is to read an error and act on it.

Most panels are desktop applications or web apps that both assume you are at a desk with a mouse. A browser panel is different in a way that matters once you are actually maintaining a server: it works on a phone.

If a server goes down at midnight, you can open the panel, read the console, fix a plugin, and restart it from your phone. You do not need to get to a desk. That is the whole reason FyreflyHost’s panel is browser-based rather than a downloadable tool.

The practical difference: with desktop software, being away from your computer means the server waits. With a browser panel, the distance between you and the server is a network round trip.

One server per account on every plan. The plans do not differ in how many servers you get — they differ in the resources that one server has, and in which management tools are available to it.

Free

One server, 256 MB RAM, 512 MB disk. Live console, one configuration backup, and automatic sleep when inactive.

Plus

One server, 1 GB RAM, 3 GB disk. No idle sleep, Lua plugin editing and reload, three configuration backups.

Pro

One server, 2 GB RAM, 6 GB disk. Custom item and texture uploads, up to 25 Lua plugins, ten configuration backups.

Max

One server, 4 GB RAM, 12 GB disk. In-browser file manager, up to 9,999 Lua plugins, 25 configuration backups.

The step that matters most is the first one. A server that is competing for memory behaves badly in ways that are hard to diagnose — worlds that take minutes to load, NPCs that stall, saves that time out. If your server feels wrong, its plan is the first thing to check. The plans page has the current prices, confirmed in billing before you pay.

Lua plugins are how a private server gets its own behaviour: different crops, a battle pass, custom quests, economy rules. On a server run from a local folder, editing one means finding it on disk, editing it in a text editor, and restarting.

With a browser panel, the edit happens where the server already is. Open the plugin, change the code, save, and reload the running server. The console is in the same view, so you can confirm the change took effect instead of guessing whether it applied.

This is not a minor convenience when you are iterating on something. Changing a value and seeing what it does is the whole process of working on a plugin, and a restart cycle is what makes that loop slow.

A private server earns its keep through custom content: items and blocks the public game does not have, and worlds built around them. Getting that content in is a real part of running a server.

FyreflyHost handles custom item definitions and texture uploads through the panel, and the marketplace has community worlds and plugins you can install directly. The Pro plan and above include custom item and texture uploads; the free plan does not, because it is sized for learning the panel rather than for a content-heavy server.

Most hosts look the same on a pricing page. These are the questions that separate them:

• Can I read the server’s output? A live console is the difference between diagnosing a problem and guessing.
• Can I manage it from anywhere? If the panel only works at a desk, it only works when you are at one.
• What happens to my world if I stop paying? Find out before you need to, not after.
• How many servers per account? Some hosts sell several small servers instead of one properly sized one.
• What does editing a plugin actually require? If the answer is an FTP client, budget for that friction.

If you want the short version, the cloud hosting page covers the same ground from the infrastructure side, and the beginner guide covers what you are actually setting up.