Field notes | Minaki

We run it on ourselves

We don't ask you to run anything we won't. MinakiLabs runs Minaki on every machine it owns — our own servers, the TunnelNet network that carries our customers' traffic, our mail, the production suite you sign in to, even the family Minecraft server. If it isn't good enough for our machines, it isn't good enough for yours.

Across MinakiLabs, 7 of the servers we run have the Minaki agent installed. That number comes straight from the suite — we never type it in by hand.

Running it on our own servers is also how we find its rough edges before you do. When something it does is wrong, annoying or alarming for no reason, we hit it first, on our own machines — and we fix it. These are the notes from that.

What the fleet found

Short, dated, honest entries. Every one is something that actually happened to us. No invented customers, no quotes we put in anyone's mouth. When real customers want to say something, we'll add it with their permission.

Day one: our Minecraft server set off the alarm — and it was us

October 2026

On the first day we had break-in watch running across our own machines, it did exactly what it is built to do: it flagged a burst of failed password attempts on one of our servers and warned us that someone was trying to force their way in.

The server was the family Minecraft box. The someone was us — fat-fingering a password while logging in over our own network.

Nothing was under attack. But a tool that cries wolf on its first day is a tool people switch off. So we taught break-in watch to recognise the machines you own and the normal ways you log in, and to weigh those before it raises an alarm. Now, when the failed logins come from somewhere that looks like you, it says this is probably you instead of you're under attack — and it saves the loud warning for when it really isn't.

Honestly, we wish we'd had this years ago, the first time a real server of ours got hammered and we found out days later. Catching our own clumsy login on day one is a small thing. Catching it before it ever reached a customer is the whole point.

How we write these

A field note only goes here once the thing it describes has actually happened to us and we can stand behind it. We describe what we found and what we changed; we don't name our servers, publish their addresses, or map how our systems fit together. And you'll never see a made-up customer or a quote we invented. When someone who uses Minaki wants to say something here, it will be their words, with their permission.