Kuberina
Naughtian
Your operational pain is real, and a lone operator deserves a real answer. Tools small enough to audit in a day, with no consensus to babysit, that leave your infrastructure intact the day you walk away.
The tools
Section titled “The tools”One operator cannot baby-sit a Vault cluster, guard a fragile tfstate, and
pray each night that Consul avoids a split-brain. Each tool here takes one of
those burdens and settles it for good. Each does one job, stands on its own,
and attaches to assets you already own. Compose them the way you chain grep
and awk, or use one and ignore the rest.
Helvilette
Kallisto
A read-only secrets resolver on localhost. It speaks the Vault KV-v2 API over one encrypted file on an S3-compatible bucket. Your request path keeps working while Vault is sealed, failing over, or mid-upgrade, and while the bucket is down. Adopting it is one environment variable. So is removing it.
Why this exists
Section titled “Why this exists”The capabilities that keep infrastructure calm, such as secret rotation, reconciliation loops and reviewed placement, usually arrive bundled inside an enterprise suite, a paid tier, or a platform team you do not have. Small organisations patch around the gap with duct tape that looks fine from outside and rots from within, and learn to leave running things untouched.
Naughtian brings those capabilities to a single operator. The approach can be blunt and the pace deliberate. The goal is to end the pain permanently, with no extra payment asked to make it stop.
The letter from NaughtThe manifesto behind every project here: minimalism over pragmatism, inert software, and zero hostage infrastructure.
What every tool promises
Section titled “What every tool promises”- You can read all of it. The codebase is small enough to audit in a day. An operator needs no certification to run it, and an ordinary AI agent can follow it.
- It holds no state worth fearing. At rest the software is inert, so backup and restore are yours to do at will. It leans on distributed consensus as little as it can, because the most resilient consensus protocol is none.
- It hides nothing and decides nothing for you. Every action is observable, and the final call stays in human hands.
- It takes no hostages. Remove any tool and your playbooks, manifests and Vault-speaking applications keep working. Your assets come back to you.
Vault manages your secrets, and someone still has to manage Vault. Anything that needs a quorum to keep running cannot be the bottom of the stack, because losing a vote stops everything built on it.
The day-2 problemWho operates the operators, why quorum disqualifies a system from being the foundation, and what Naughtian does and does not solve.
Where each one sits
Section titled “Where each one sits”Kuberina decides where workloads go before anything runs. Helvilette keeps the machines underneath converged on their desired state. Kallisto serves the secrets those workloads need from the same machine, without a round trip to the root of trust. When any of them fails, the layers around it keep working.
The stack, layer by layerHow the three tools compose, what each one deliberately does not do, and where the boundaries sit.
Research
Section titled “Research”Every design is argued in public before it is built, so its reasoning can be questioned and broken by anyone. The papers carry the mathematics, the benchmarks and the argument, including what has not yet been measured.
Kuberina: Maritime Stowage-Inspired Combinatorial OptimizationProblem formulation, the three-phase FFD/GA/CSP pipeline, and results on a 620-node, 2,714-pod benchmark.
Operator ExperienceThe cost of diagnosing a system under pressure, treated as a measurable design property.
Kalena (proposal)Online resource reclamation and opportunistic co-scheduling on the slack Kuberina leaves behind.
Whitepaper templateThe interview-question framework used to write every paper in this collection.
Your pain, your answer
Section titled “Your pain, your answer”These tools are one answer to pain that someone faced directly. It may not fit yours. The source is open for that reason: bring the operational stories these projects cannot yet resolve, fork a repository and reshape it, or build what is missing.
I have recognized my pain. Where is my solution? If nobody built it yet, I will create it myself.
Kalena, Kaeliir and Ginnungagap are the next answers in progress, and will appear here as they become real. Their names come from the same saga as the rest. See names and mythology.