Managed servers, in preview

When I started HiveScale, the deal was simple: you bring the boxes, we handle the boring backend. That has not changed. But the single most common question we get is some version of “I just want to try this, do I really have to rent a server first?” As of this week, the answer is no.

What shipped

You can now provision and autoscale game servers on managed cloud capacity without leaving the dashboard. Create a network, pick a region, set a min and max instance count, and we keep the right number of servers warm as players queue up.

Everything else you already know still applies. Managed servers register themselves, join matchmaking, and carry player data exactly like the boxes you run yourself. There is no separate code path: a managed server and a bring-your-own server are the same server to the rest of the platform.

Why it took a while

The honest reason is that we did not want to become a worse version of a cloud provider. The goal was never “rent you a VM.” It was to make the path from “signed up” to “players are connected” as short as possible, and renting a VM is only step zero of that.

So a managed server is not just a box. When you spin one up, it boots a pre-warmed image with the SDK already wired to your network, registers on first heartbeat, and shows up in your activity feed before the dashboard finishes its spinner. That last part only works because of the live feed we shipped two weeks ago.

What is still rough

This is a preview, and it shows in a few places. Images are currently HYTALE-flavoured placeholders while we finish the Minecraft templates, regions are limited, and per-network spend reporting is still on the roadmap rather than in the product. We would rather ship it narrow and honest than wide and vague.

Try it

If you have been waiting for a way to kick the tyres without renting anything first, this is it. Create a network, pick “managed” when you add a server, and you should be connected within a couple of minutes.