Your world. Inside your boundary.
“Your world” in the tagline is literal: your ground, your data, inside your boundary. BirunIQ deploys three ways, and the rules that matter hold in all three.
SaaS
Hosted for you, on the same engine as every other deployment. External data flows only through the egress gate, and each tenant can switch external data off for itself.
Sovereign hybrid
For customers whose data must stay under their own control, with external data still behind the gate and the same per-tenant switch.
Air-gap capable
A per-customer build for customers who need a lockout. No runtime call leaves the deployment boundary: no external data, no model API, no CDN font. A delivery is called air-gapped only after it passes verification on that build.
Nothing phones home.
If a dependency phones home on its own, it does not go in.
- 01No telemetry
- 02No licence check
- 03No crash reporter
- 04No font from a CDN
- 05A stored credential is sent only to the provider that issued it
External data, on your terms.
In a connected deployment, external data passes through one gate. Every external feed is listed with its status, and a tenant can switch external data off from the admin console.
Kept apart where it counts.
Row-level security
Each tenant's data is separated in the database itself. The server refuses to start as a role that could bypass it.
Scoped by team
Inside a tenant, access follows the team, not the whole organisation.
One sign-in, two factors
One identity across every edition and the field app, with a second factor at sign-in.
Clean supply chain
Every model, dataset and dependency carries a licence class, and each model a provenance manifest.
Tell us where it has to run.
We'll talk through the deployment your agency needs, including a lockout build.
Request a briefing