Open weights, a European region, and a deployment you control
A public body and a defence supplier ask the same two questions before anything else: where does the data go, and who else can read it. Everything after that is detail.
Munito AI runs open models on European infrastructure, keeps no prompts or outputs by default, and trains on nothing you send. Where that is not enough, the whole platform runs inside your own cloud account or on-premises.
Open weights are the procurement argument
A closed model is a dependency you cannot inspect, cannot move and cannot keep running if the vendor changes its terms. Open weights change each of those:
| The question | What open weights answer |
|---|---|
| Can we inspect what we deploy? | The weights are published; so are the evaluations |
| Can we leave? | The same model runs elsewhere, including on your own hardware |
| Will the model disappear? | A published checkpoint does not get deprecated out from under you |
| Can we run it in a closed network? | Yes, on-premises, with no call to an external service |
We hold no weights of our own, so we have nothing to defend. When a better open model ships, the catalogue changes.
Where it actually runs, stated plainly
Managed capacity runs in the EU on infrastructure we rent and operate. The sub-processor list names every company in that chain by region, and it includes the European regions of large cloud providers. If your rules say that is not enough, the answer is not a better paragraph from us: it is a deployment inside your own perimeter.
Run the platform in your own cloud account, or on-premises in your own data centre, with your network and your controls. Your team keeps one API across each choice, so a pilot on managed capacity moves behind the firewall with no rewrite. See Enterprise.
What the workloads look like
| Workload | What it does |
|---|---|
| Document and case files | Turn scanned correspondence and forms into structured records |
| Internal knowledge | Answer a question from your own procedures, with the source passage |
| Translation | One model reads and writes the languages of your country and your union |
| Drafting | Prepare a reply or a summary that an officer reviews and signs |
Open models read and write the languages of Europe, so one deployment serves a multilingual service.
What we do not claim
We hold no national security accreditation, no defence clearance, and no sovereignty label from any member state. Our SOC 2 audit and ISO 27001 certification work are in progress, and neither is finished.
What we have today is a documented data policy, a DPA that applies with no signature, a published sub-processor list, posted prices, and a deployment you can put inside your own perimeter. If your tender needs a certificate we do not hold, we will tell you before you spend time on it.
Procurement, without the theatre
Posted prices mean a budget line you can write before a negotiation. A DPA that forms part of the Terms means no signature round. A named region means an answer to the residency question in one sentence, provable from the munito-region header of any response.
For an EU-funded or a national programme, the exit question matters as much as the entry one: open weights, a standard API and a portable deployment mean the exit plan is short.
Start
- Bring the paperwork to your review
- Read where each region keeps what
- See the deployment choices
- Talk to an engineer about your rules, your languages and your network