for the people who keep it all running

The craft changes. The care doesn’t.

AI is changing how software is written, shipped and run: agents already open pull requests and change cloud infrastructure alongside people. Picaporte Labs is a small software studio in Spain making tools for that shift: few, sharp, and honest about what they don’t do. The first is kubelatch.

What we make.

kubelatch

Kubernetes permissions with an end date.

Your cluster already knows who signs in. kubelatch adds the rest: how long each permission lasts, what it allows and a record of every request, for people, CI pipelines and AI agents alike. Every credential has an owner and an expiry, and can be revoked instantly.

In public preview. Free for up to 2 clusters and 5 people, with 24 hours of audit and no time limit.

Four things we hold to.

  1. Honest about boundaries

    A tool should say what it does not do, on the page where you decide whether to use it. kubelatch’s manual has a section for exactly that: what kubelatch doesn’t cover.

  2. Private by default

    No telemetry and no cookies. Our sites count visits with Umami on our own server, without keeping your IP address. License keys are verified offline; the only call kubelatch makes to us is a daily version check that carries no identifier, and one setting turns it off.

  3. For people and agents

    AI agents already work alongside people. Our tools give each one, person or agent, its own identity and its own limits; an agent’s writes can wait for a person’s approval, and everything is on record.

  4. Your infrastructure, your data

    Our tools run where you run them: kubelatch installs in your own Kubernetes with a Helm chart, and works air-gapped with local accounts or an identity provider inside your network. Your clusters, credentials and audit stay with you.

One person, for now.

Sergio Jurado, platform engineer

I make kubelatch, and I’m the one who answers when you write.

Picaporte Labs is where I make the tools I want to use myself: small, honest about what they don’t do, and in two languages.

From the blog.

All posts

Write to us.

Anything about Picaporte Labs goes to hola@picaportelabs.com, and anything about kubelatch to hello@kubelatch.com, in English or Spanish. A vulnerability goes to security@kubelatch.com, as the security policy describes.

Picaporte Labs on GitHub and LinkedIn.