For the public sector
Sovereign by architecture. Accountable by name.
Public infrastructure answers to more than an SLA: it answers to auditors, courts, and citizens. Infraware runs entirely inside your boundary and turns every operational change into a signed, reviewable record, the kind of paper trail your oversight bodies already know how to read.
Sovereignty · one picture
Sovereignty
Sovereignty is not a clause. It is a property.
Data residency guaranteed by contract can be renegotiated, subpoenaed, or breached. Residency guaranteed by architecture cannot: there is nothing to renegotiate.
Everything, the agent, the console, the record, deploys inside the boundary you already control: your cluster, your datacenter, your jurisdiction. Choose an in-boundary model and the system operates with zero external processing, disconnected from the internet entirely. Foreign cloud dependence becomes a decision you make, not a condition you inherit.
We are an EU company (Infraware Srl, Italy). But the stronger claim is architectural: there is no channel back to us at all, so our jurisdiction never touches your data.
Accountability
Every change is an administrative act, with a name on it.
In public administration, an unattributable change is not an incident, it is a liability. The question is never only what happened, but who decided.
Nothing mutative runs without a named person signing it, and every approved execution writes a record: who approved, on what evidence, what ran, what happened. When the audit office, a parliamentary question, or a court asks how a system changed, the answer is a document, not a reconstruction from shell histories.
The record lands in your own log storage, under your retention rules, beside your existing security logs. It survives us: cancel the contract and the paper trail stays yours.
NIS2
Evidence for your obligations, not a badge.
We will not tell you a product makes you compliant; your auditors would not accept the sentence anyway. What a product can do is generate the evidence your obligations keep asking for.
- Incident handling. Every investigation produces a timestamped, evidence-linked report, whether or not a human was awake for it.
- Access control and accountability. Read and write principals are separate; write access exists only behind a named approval, under the write principal your own configuration scopes.
- Supply-chain hygiene. Versioned images you pull deliberately, nothing self-updates, dependency-locked builds. Images are not signed and ship without an SBOM.
Map these to your Article 21 measures with your compliance function; our security posture is public and we answer questionnaires with the same sentences you read here.
Procurement
A shape procurement can sign.
Public money needs numbers that hold still and dependencies that can be named in one page.
Licensing is flat and scoped to your infrastructure: no per-seat counting across departments, no usage metering that turns a budget line into a forecast. At runtime the outbound connections are the model endpoint, which you own, and, unless you mirror it, the registry for the executor image. No telemetry means the data-protection impact assessment describes a system that sends us nothing.
Security review happens with people, not PDFs: we walk your team through the architecture and the parser design live, on the record.
Asked by public entities
Four questions, answered.
Can it run fully air-gapped?
Yes. Once running it calls only the model endpoint you configure and the registry holding the executor image that approved commands run in. Mirror that image and serve an open-weight model in your cluster, and it calls nothing at all. The install pulls our images and the executor image, all of which you can mirror into your registry, and one setup hook fetches operating-system packages: we give you that list before install so you can mirror it too. The same product, not a degraded mode. The egress story →
Does citizens’ data ever reach a foreign model provider?
Only if you choose one. The model endpoint is your configuration and your contract; run the model inside your own boundary and no external processing exists at all. Where it runs →
Could Infraware be compelled to access our deployment?
There is no channel to compel. No control plane, no remote access path, no telemetry. A legal order cannot open a door that does not exist. Verify the boundary →
Which certifications do you hold?
None yet, and we will not imply otherwise. What we ship today is the evidence layer: signed decisions, per-execution records, versioned images you pull deliberately. Audit & accountability →
How to start