We design, code and run our own multiplayer games. Two Minecraft networks, a Roblox studio, and the discovery network that puts them in front of players. Everything in-house, everything still live.
Two Minecraft networks live today, a Roblox tycoon in testing, and one network we retired after six years on our own terms.
Flagship
Our flagship network. Prison, Skyblock, Survival, Dungeons and Cobblemon, every mode written by this team rather than bought off a marketplace. Seasons reset, economies get rebalanced by hand, and one login covers Java and Bedrock.
A semi-vanilla SMP that stayed small on purpose. Custom progression, boss rushes and live events that turn into stories players still bring up a year later. Dense in personality, low on grind.
New · in development
A lucky-block slime tycoon. Buy slimes, merge them, rebirth, and grow a plot that prints goop while you sleep. Twenty-five tiers from a Leafy starter to Galaxy, built by our Roblox team and in closed testing now.
Two further Roblox experiences in production behind Slime Farm. Same rule as the Minecraft side: original ideas, systems designed to hold up past week one, no reskins.
AkumaMC opened in 2019 as an empty server with nobody on it. No audience, no funding, no publisher. We grew it by shipping something every single week and sitting in the Discord at 3am reading the complaints.
Years of that took it from an empty lobby to 1,700 players online at once and over a million unique accounts. We got plenty wrong on the way. We sunset it in 2025 deliberately, with the lights still on. Every mistake on it is a rule now.
Borrowed systems became somebody else's bug to wait on. Everything is in-house now, so a fix takes a night.
We ran economies months past their peak because the numbers still looked fine. They weren't.
The loudest tickets were the ones we deferred longest. Balance passes come out of Discord now.
The bigger it got, the more corporate we let it become. Announcements instead of conversations. We felt the distance.
Not a slogan. Nobody is owed an audience. The day we stop being worth someone's evening, we deserve to lose it.
We build and operate our own titles end to end. Design, code, art direction, servers, moderation. Nothing we run is a reskin of somebody else's plugin pack.
Our games1.4M+ players have passed through our worlds and thousands are in the Discords right now. The community is the product. Staff read the tickets, and balance changes come out of them.
Get in touchWe also run the layer above the games: a network of server-discovery sites that sits on the searches players actually make when they're looking for somewhere new to play.
See the networkEvery season ships off the last one's feedback. Short loop, no roadmap theatre. That cycle is most of what the studio actually is.
Games are half of it. The other half is where players actually start: five single-purpose server lists, one per gamemode, built and operated by us. Live status pings, hands-on testing, a monthly player vote, and a free open-data API on top.
Every mode we run was written here. When something needs to change mid-season it changes that night, not next quarter.
Worlds reset. Economies reboot. Leaderboards go back to zero. Players return for the start line, not the endgame.
Balance passes come out of Discord threads and bug reports. The distance between a complaint and a fix is the whole advantage.
A smaller side of the studio, and a serious one. We take on a handful of software engagements a year, mostly fintech: backend systems, integrations, internal tooling.
Engagements stay small by design. We work directly with founders and engineering leads, scope tightly, and ship the thing that was agreed.
Start a conversationServices that carry real traffic and hold real state. Mostly JVM, Node where it fits, with Mongo, Redis and Postgres behind them. Written to be read by whoever inherits it.
Payment rails, provider APIs, ledgers and reconciliation. The unglamorous half of the stack where being correct matters more than being fast, and where the edge cases are the actual job.
Admin panels, ops consoles and live metrics. If your team is running the business out of a spreadsheet and three Slack threads, this is the part we fix first.
Marketing sites through to logged-in product. We run our own network of high-traffic sites, so this is the same work we already do for ourselves every week.
Bare metal and VPS fleets, CI pipelines, monitoring, and backups that have actually been restored rather than just scheduled. We keep our own game infrastructure up around the clock, so none of this is theory.
Architecture reviews, second opinions, and someone telling you which half of the plan is the risky half before you build it. Short engagements, straight answers.
Everyone here ships. No layer of people between the players and the code.
We hire slowly. If you've shipped real things to real players, take ownership without being managed into it, and want your work played the week it lands, talk to us.
Game project, software engagement, brand collaboration, or a platform partnership. Tell us what it is and we'll tell you straight whether it's a fit.
