Skip to content
Letting AI assistants help run servers, with a person always in charge
Engineering4 min read

Letting AI assistants help run servers, with a person always in charge

Why I built Airlock: AI can take on real server work, as long as a team member approves anything that matters.

Shohruhxon AsrorxonovSoftware engineer

AI coding assistants have become genuinely good at day-to-day server work: reading logs, checking what’s running, restarting a service that stopped. The question every team asks is how to let them help without handing over the keys to everything.

Airlock is my answer. It sits between the assistant and the company’s servers and turns access into something the team controls:

  • Switched on, not always on. An assistant can only work while a team member has enabled it, for a set amount of time.
  • The right level of access. Some assistants may only look; others may make changes.
  • A person approves what matters. Restarts, updates and anything that removes data wait for a team member to approve them in the app or with one tap in Telegram.
  • Everything is visible. Each session can be watched live and is kept for later review.

The same care for people

Team members get time-limited access tied to their own device, so there are no long-lived keys to lose, and removing someone’s access takes a single click.

Where it’s going

Airlock runs the servers at NDC-CO every day. I’m developing it into a product for any team that wants AI help with operations while keeping people firmly in charge.

Have something to build?

A product, a platform or a stubborn bug. Send me a couple of lines and I’ll reply the same day, usually within a few hours.

Get in touch