Teams ship with AI.
AI ships with Linro.
Infrastructure changes constantly, and increasingly it's AI agents making the changes.
Tools that scan snapshots and flag risk after the fact can't keep up.
Linro enforces intended state across the whole lifecycle instead, from commit to runtime: MCP and pre-commit hooks at commit time, blast-radius simulation that blocks bad changes before they ship, and real-time detection, enforcement and auto-remediation in production.
Most tools tell you what's wrong.
Linro stops it.
We have each been on the receiving end of this problem: Running cloud security at scale, building the platforms underneath it, and shipping in regulated systems where a wrong change isn't an option.
Founded in Berlin in 2026 and built fully remote across Europe, Linro has a platform that's real and working, with plenty still to shape.
The roleYou would be one of our first infrastructure hires, taking day-to-day operation of the platform off the CTO.
Linro enforces policy on other people's cloud infrastructure, so our own has to be reliable, reproducible and auditable.
You own production: how Linro runs for each customer, how it upgrades, and how we know it is unhealthy before a customer does.
What you will doOwn production reliability: SLOs, alerting, on-call and blameless postmortems for the control plane and every customer installation.
Make the install fleet boring: provisioning, maintenance windows and safe auto-upgrades across SaaS and self-hosted installs.
Fix the open reliability work: sensor memory ceilings and OOM visibility, ClickHouse cost and capacity, and the health of Postgres, PGMQ and Temporal.
Evolve the platform: Terraform and Terragrunt, Helm, GitHub Actions with short-lived OIDC credentials, local development (Tilt, Coder), and staging and production environments, with guardrails for humans and AI agents alike.
Produce audit-ready o.