Large servers

One server for a huge crowd.

When your community outgrows our plans, we build a server around it: one address, the whole crowd together. Past our largest plan (200 players), each server is built for the peak you expect, load-tested at that number, and quoted for that build.

Hosting fewer players? See the plans.

One address

Players join the same address however many of them there are. No lobby servers to hop between, no “server 3 is full”.

Everyone together

Players aren't split into separate copies of your world. Anyone can find anyone else, trade with them, and travel anywhere.

Grows with you

We resize the server — and the quote — as you grow, while the address and the world stay exactly the same.

What decides capacity

Where your players are matters more than how many

Any format

Everyone in one place

A huge crowd in the same spot at the same time. A single lobby, a launch, a concert, a finale — it doesn't matter how players are spread across the world.

  • Single-lobby events
  • Launch events
  • Everyone in one spot

Quoted per build

Even bigger

Spread across the world

When players are spread across the world rather than packed into the same chunks, one server holds even more of them. That fits SMPs, survival worlds and minigame networks, where people are in different places doing different things.

  • SMPs
  • Minigame networks
  • Survival worlds

Quoted per build

Built as a project

The biggest communities

For the largest networks and launches, still on one server and one address. Built as a project, with the world layout planned alongside us.

  • Large networks
  • Seasonal launches
  • Global events

Quoted per build

A bigger peak means a bigger build, and the quote follows it — there is no flat rate that makes extra players free. These formats are how we plan a build, assuming a render distance of 8 chunks; the capacity we commit to comes from load-testing your own setup.

What changes the numbers

Player count is only half of it

Render distance

These formats assume a render distance of 8 chunks; Minecraft's own default is 10. Every extra chunk means more of the world loaded and kept live around each player, so asking for more than 8 lowers what a server of a given size can hold — how far depends on how much higher you go.

Plugins

Which plugins you run and how heavy they are. Some add almost nothing; others do real work for every player online, and with a crowd that size it adds up fast.

Redstone and farms

Whether redstone is on, and how much of it runs at once. Large farms and always-running clocks do work on every tick while their area is loaded.

The guarantee

20 TPS, tested before you launch

20 TPS is the full speed Minecraft runs at. We don’t promise it from a spreadsheet — we prove it on your setup first.

  1. 1

    Tell us your setup

    Peak player count, the format (one event, an SMP, a minigame network), render distance, the plugins you plan to run, and how much redstone you expect.

  2. 2

    We build, test and quote it

    We build a server to your setup, load-test it at the player count you asked for, and price that build — before it goes anywhere near your players.

  3. 3

    You get 20 TPS, guaranteed

    Once it passes, your server is guaranteed to hold a full 20 TPS for as long as it stays within the setup we tested. Change something that moves the numbers — a higher render distance, more players, a heavy new plugin — and we re-test first.

Large servers are quoted individually, from the peak you expect and how the server will be used. The limits we test against are written into your agreement, so both sides know exactly what the guarantee covers.

Get a quote

Tell us about your server

The more of this you can tell us, the faster we can size, test and price it:

  • Peak player count, now and where you expect to be
  • Format: one event, an SMP, a minigame network
  • Render distance you want
  • Plugins you plan to run
  • Redstone: on or off, and how much

Or email [email protected]

Back to the plans