Skip to content
Infraware.dev

Built by people who answer for production.

Infraware builds a governed operations engine. Small team, no venture funding, and 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
Open source
rotelle, Apache-2.0

Backed by

  • NVIDIA Inception program member
  • TEF Foundation
  • Google for Startups

Engineering principles

These are the brand.

Parse errors reject.

Anything the system can’t parse with certainty is refused. Uncertainty never fails open.

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, gated.

A Rust workspace behind CI gates, format, lint, and test suites on every merge. The failure simulator we test with is public.

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 investigating agent works the same way, so it carries his name. Virgil watches, traces, and briefs; his name is on the investigating steps of the loop. SIGN is a person. Production is a decision, and a decision has a name on it, which is why the last 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 founders

A standing 45-minute architecture call, answered by an engineer, not a queue.

You've read the mechanism. Now watch it run.

Read what we write about →