Mirra Sovereign
On-premise, air-gapped
The whole platform inside your own network, with no connection to us and no data leaving the building.
Who this is for
Estates where keeping data on site is not a preference but a condition of the contract: defence and its supply chain, custodial and secure hospital estates, critical national infrastructure, laboratories and clean rooms, and any organisation whose security policy forbids a cloud tenancy outright.
If you are reading this because you would prefer your data stayed in the UK, you probably do not need this. The hosted product already runs entirely in AWS eu-west-2 (London) — see the trust centre — and it will cost you a great deal less.
What it is
The same software, deployed inside your perimeter and operated by you. Mirra is already four separable pieces — the portal, the relay that talks to screens, the screen application itself, and a Postgres database with object storage for photographs and documents — and Sovereign is those pieces running on your hardware or your private cloud, behind your firewall, under your identity provider.
- No outbound connection to us. Not for licensing, not for telemetry, not for updates. Updates arrive as a signed image you choose to install.
- Your identity provider. The hosted product already speaks OIDC for enterprise single sign-on; Sovereign uses the one you already run.
- Your storage and your backups. Photographs, visitor documents, permits and floor plans sit in your object store, on your retention schedule, under your encryption keys.
- Your screens. The screen application is a static bundle served from inside the network. A display never reaches the internet.
What you give up
An air gap is a real constraint and it removes real features. These are the ones that go, and they go for the same reason in every case — each is a request to a server outside your network, and inside an air gap there is no such request.
- The AI assistant, unless you bring a model.The hosted product uses Anthropic's Claude via AWS Bedrock. Air-gapped, that call cannot be made. The assistant can be pointed at a model you run yourself, and that is a conversation about what you already have rather than something we can assume.
- Cloud calendars. Google Calendar and Microsoft 365 are cloud services. An on-premise Exchange, a CalDAV server, or a calendar file published inside your network are all reachable; a Microsoft 365 tenancy is not.
- Weather, travel and news.All of them are somebody else's API.
- Leaving times with live traffic. Same reason — a routing provider is an external service.
- Cloud-only smart home and lighting integrations.Anything that works by talking to a manufacturer's servers stops working. Home Assistant, which runs on your own network, does not.
- Email out, unless you have a relay. Arrival notifications, evacuation roll calls and visitor invitations all need somewhere to post a message. An internal SMTP relay is enough.
- Payments and subscriptions. There is no Stripe inside an air gap. Sovereign is licensed rather than subscribed, which is the other reason the price is a conversation.
What is left is the part most of these estates actually want: the reception desk and the visitor book, the evacuation roll call, permits to work and contractor compliance, room and door panels, wayfinding, digital signage and menu boards, floor plans, and the scheduler that drives what is on which screen and when.
What we would need to know
Enough to give you a number rather than a range. Roughly: how many screens and across how many sites; whether this is your hardware, a private cloud, or a customer's; which accreditation you are working to and who signs it off; whether you want a model for the assistant and what you already run; who operates it day to day, and what you expect from us once it is in.
Price on application
Deliberately. Sovereign is priced on the size of the estate and on how much of the running we do, and any number printed here would be one we had to walk back on the first call. Tell us the shape of the problem and we will tell you the cost of solving it.
Mirra is part of Twinview and is built by the same team, so estate-scale and security-constrained deployments are familiar ground. If the hosted product suits you better, the pricing page has the business plans.