Security and testing ship with every feature
Strict tenant isolation is the thing we care most about, so testing and security ship with every feature. A look at our latest hardening pass.
PicoPaaS is a strict, multi-tenant mini-PaaS for throwaway apps: one Docker image, some env vars, an optional small database and bucket, and you are live. The thing we care about most is strict tenant isolation. If one app can touch another, nothing else matters. So testing and security are not a bolt-on for us. They ship with each feature.
Tests that have to earn their keep
We recently pushed backend branch coverage to about 91% across roughly 990 tests. Coverage alone is a vanity number, so the tests are also mutation-checked: we deliberately break the code and confirm the tests notice. If a test still passes against broken code, it is not really testing anything.
That work found real bugs, and we fixed them. A handful of genuine defects surfaced, including two where an administratively-suspended app could wriggle back to life, plus some places where we tightened behavior to fail safe. Finding your own bugs before users do is the whole point of the exercise.
Pentesting ourselves
We also ran a self-pentest against our isolation. It confirmed no cross-tenant holes. It did flag that our in-cluster controller held broader Kubernetes permissions than it needed. That was defense-in-depth rather than a reachable hole, but we do not like leaving slack in the permissions of something that powerful.
We narrowed it to least privilege: the app controller can now only act inside individual app sandboxes, not cluster-wide. We added an admission guard on top, then verified the change live by deploying and tearing down a throwaway app on the real platform.
The culture
We are a small dev/test platform, not a bank, and we will not pretend otherwise. But we actively try to break our own platform, with test apps built to misbehave, and every feature gets that scrutiny before it counts as shipped. You can try it yourself at picopaas.xyz.