About Speaway

We got tired of watching good servers fail for boring reasons

Not because the idea was weak. The plugin developer vanished, the host stopped replying, and the textures never matched the build. Speaway exists so that stops being the normal experience.

Why we started

The work was never the hard part

Coordination was. So we stopped coordinating and started building the whole thing.

Every server owner we met was running the same relay race. A freelancer wrote the plugins. Someone else drew the textures. A host owned the machine but not the problem. When something broke, and something always broke on the night it mattered, each of them could point at the other two and be technically right.

The communities paying for all of this did not care whose half it was. They saw lag, a broken store page, textures that looked wrong on Bedrock, and a launch that slipped again. Good projects died with a working idea and a broken supply chain.

So Speaway was built the other way around: one team that owns the whole surface, the machine, the code, the art and the checkout, and that runs its own networks on exactly the same stack. When we hand something over, it has already survived our own players.

“If we would not run it on our own network on a Friday night, we do not ship it to yours.”

The rule everything else here follows from.

How we work

Four things we do not negotiate

These are not values on a wall. Each one costs us something, which is how you know we mean it.

We run what we sell

Our own networks run on the same stack we hand to clients. If a plugin leaks memory or a panel falls over at peak, it happens to us first, and it gets fixed before it ever ships.

One team, not a relay race

Infrastructure, gameplay code, art and payments come from the same people. Nobody gets told the problem lives in someone else's half of the project.

You own the result

Source, assets and access are yours. We build things you could hand to another team tomorrow. That is what makes staying a choice rather than a trap.

Written down, not promised

Scope, response times and refund terms live in the SSLA and the Terms, not in a Discord message somebody remembers differently later.

What we do

Four disciplines under one roof

Deliberately equal in weight. A studio that only does Minecraft plugins is a plugin shop, and that is not what this is.

Server solutions

Setup, hardening, performance work and migrations for live communities.

Plugins & addons

Custom gameplay systems for Java and Bedrock, kept in sync across versions.

MCP & AI tooling

Model Context Protocol servers and automations with real permission boundaries.

Themes & textures

Resource packs, interface systems and brand work that hold together everywhere.

Where we are

We are our own biggest client

The networks below are ours. They are the reason we can say the stack holds under load without asking you to take our word for it.

150,000+players on MinevaniOur flagship SMP, years into its life.
80,000+players on MinebonMinigames behind a single matchmade hub.
4disciplines in houseServers, code, AI tooling and art.
6server brands shipped forLive communities running on our work.
Where we are going

What we are building next

Not a roadmap with dates on it, just the four directions everything we take on has to point towards.

01

Sharpen the internal tooling

Most of what makes a build fast is the tooling around it: converters, generators, deploy scripts. The better that gets, the less every project costs to start.

02

Put AI where it actually helps

Not a chatbot bolted onto a storefront. MCP servers that let an assistant read a report, check a metric or run an ops task through a boundary you defined.

03

Fund the next builders

The Creator programme exists because good ideas usually stall on money and infrastructure, not talent. We want that list of funded projects to get longer.

04

Answer faster than anyone expects

Support is where most studios quietly stop. Ours stays open after launch, and we keep pushing the response window down rather than letting it drift.

Tell us what you are building

Bring the messy version. Half of what we do is working out what the thing actually needs to be before anyone writes code.