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.
• Plugin, world and item tools. Edit Lua plugins, install worlds and add custom items from the panel instead of a folder on someone’s PC.
• 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.

Both run the same software and the same world. The difference is who keeps it alive, and what it depends on.

Uptime

A PC server exists only while that PC is on, awake and connected. It stops for Windows updates, a restarting router and the week you are away. A hosted server does not depend on your hardware or your internet.

Players

A PC server is capped by your home upload speed and competes with the game you are playing on the same machine. A hosted server is capped by its own plan.

Privacy

Hosting on your PC means giving your home IP to everyone you invite. Players of a hosted server connect to the host instead.

Management

Local means text editors, copied folders and terminal restarts. Hosted means a console and an editor in the same browser tab.

Cost

A PC server costs electricity and a machine you already own. Hosting costs a plan, or nothing on the free one.

Running on your own PC is not a wrong choice. It is the fastest way to see a private server working at all, and it is fine for a small group on a good connection. The question is whether the server is for people who are not you. If it is, the beginner guide walks through both routes.

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

If a server goes down at midnight, you can open the panel, read the console, fix a plugin, and restart it from your phone over mobile data. Nothing to install and nothing to keep up to date. That is the reason FyreflyHost’s panel is browser-based rather than a downloadable tool.

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. Live console, 3 custom items and 5 Marketplace plugins. One configuration backup. Renew every 3 hours to keep it running; stops after an idle hour.

Plus

One server. No idle sleep, 10 custom items and Lua plugin editing with reload. Shops, recipes, drops, news, wiki and the social portal. Three configuration backups.

Pro

One server. 50 custom items, item-pack publishing and the Discord bot, up to 25 Lua plugins, ten configuration backups.

Max

One server. Edit and delete server files in the browser, unlimited custom items and Lua plugins, 25 configuration backups.

If you have never run a private server, start on Free. Move up when a specific limit is the actual problem:

• Plus when you want the server running with nobody online, or want to write plugins. Lua plugin editing is the first tool the free plan does not have, and it comes with the community editors: shops, drops, news and the social portal.
• Pro when you want 50 custom items, to publish item packs, or the Discord bot. This is the plan content-heavy servers need.
• Max when you manage a lot of files directly, or run a large plugin collection.

A server that is short on 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 pricing page has the current prices and compares every feature side by side.

Every paid plan comes two ways: a 30-day plan you renew while you need it, or a one-off permanent purchase that does not expire. Permanent plans are sold in limited numbers, and the pricing page shows when one is sold out.

You pay in Indonesian Rupiah by QRIS, which banking and e-wallet apps in Indonesia can scan. The price is confirmed in your billing page before you pay anything, and changing plan keeps the server’s worlds, configuration and installed plugins.

The full terms, including acceptable use and suspension, are in the Terms of Service.

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.

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. Every plan can hold custom items, and paid plans raise the cap and the texture storage: 3 items on the free plan, 10 on Plus, 50 on Pro and no cap on Max.

If you already run a private server, its worlds, plugins and custom items move across. The usual order:

1. Stop the old server cleanly so its worlds are written to disk and not half-saved.
2. Create the server here and note its connection details.
3. Bring your worlds in from the Worlds page in the panel.
4. Upload your plugins and watch the console for load errors: plugins written for another server often need small changes.
5. Reconnect your players using the connection guide.

Plan for a short gap. Tell your players the server is moving, and expect players on mobile to need a fresh setup before their first connection works.

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.

New to all of this? The beginner guide covers what you are actually setting up, and the free plan page covers what you can do before paying anything.