Parse errors reject.
Anything the system can’t parse with certainty is refused.
Uncertainty never fails open.
Company
Built by people who answer for production.
Infraware builds a governed delegation platform for infrastructure operations, with one conviction: in this category, the audit trail is the point. Every write answers to a named person, and that part never gets automated away.
- Company
- Infraware Srl
- Where
- Sassari, Italy
- VAT
- IT03049070901
Backed by
Member of
European cloud programs
Leadership
Named, like every signature in the record.
In a pilot you work directly with them and with the engineers who built Infraware, not a ticket queue.
-
Francesco Niccolò Garau
Co-founder and CEO
Leads strategy, sales and partnerships. Previously led teams building AI-driven products for startups and enterprises.
-
Alan Chen
Co-founder and CTO
25+ years in cloud infrastructure. Previously CTO at InfinyOn. Critical infrastructure in aerospace and defence.
-
Laura Emilia Hellqvist, PhD
Co-founder and COO
Multi-million international contracts in critical industries across Europe, Asia and the Gulf.
Open source
rotelle, our Kubernetes failure simulator.
Apache-2.0, in your own cluster. Six reproducible failures, on cue. It is how we demo, and how every pilot is accepted.
Engineering principles
These are the brand.
The human is the feature.
Every write carries a named approver. We automate more only as the
record proves it safe.
No black boxes.
Alert rules are readable JSON. Runbooks are editable text. Reports
show their evidence.
Compiled, tested, checkable.
A Rust workspace with format, lint, and test suites. The failure
simulator we test with is public, so you can run it too.
Why Virgil
In Dante’s poem, Virgil is the guide. He walks ahead of the traveller through every level of a world that has gone wrong, names what is there, and explains how it came to be that way. He goes everywhere the traveller goes, except across the last threshold, which is not his to cross. That step the traveller takes alone.
Our agent works the same way, so it carries his name. Virgil does the work and proposes the change; his name is on the first step of the loop. Sign is a person. Production is a decision, and a decision has a name on it, which is why that step is always yours.
Engineering choices
Why Rust?
Three reasons.
The command parser and the allowlist are the product’s spine, the layer that decides what a proposed command is allowed to become. We wanted the compiler in the room when that layer changes, not just a test suite.
Compiled binaries in distroless images mean no readable source in your cluster and no shell in our service containers, a smaller attack surface, and our intellectual property stays ours.
And the runtime footprint stays small and predictable, which matters when you are a guest in someone else’s production cluster.
Direct contact
Talk to the people who wrote it.
hello@infraware.dev · security@infraware.dev
Talk architecture with the foundersA standing 45-minute architecture call, answered by an engineer, not a queue.
How to start