About Starlab

Starlab makes small developer tools and guides for one job: shipping a small app on a single server and being able to recover it when something goes wrong.

How we work

• We run it before we say it. Scripts and chapters are executed in clean containers. Failure cases are tested as carefully as the happy path.
• We publish the limits. Every product page has a "not tested" list, because what a tool has not been checked against matters to anyone about to rely on it.
• We measure. Where a claim can be a number (failed requests during a deploy, seconds to recover, events per second) it is a number, with the setup that produced it.
• We fix what the tests find. The handbook and the kit both changed because their own tests broke the first drafts. The changelogs say so.

What we do not do

We do not publish customer reviews we do not have, invent logos or testimonials, or promise results on your hardware. Our numbers come from one machine and one setup, and the pages say that.

Products

See the products, the blog and the free tools. For how claims are checked, read how we verify.