Your data does not have to leave the building.
Where the data sits is decided by your rules, not by our stack. We deploy the agents, the speech models and the telephony where the rules allow, including on servers that never touch the internet.
Zingaro AI deploys on the client’s own servers, air-gapped where required, into the client’s private cloud account, or on infrastructure Zingaro runs. The client chooses; the work is the same.
On your servers. Your private cloud. Or ours.
On your servers
Air-gapped where required.
We install on machines you own, inside your network. Where the rules demand it, the system runs with no outbound connection and updates are carried in by hand. Your team keeps the keys.
Data stays inside your network
Your private cloud
We deploy into your account.
We deploy into your own cloud account, in your region, under your access controls. The data stays in your account. We get the access you grant, and nothing more.
Data stays inside your account
Ours
Managed, fastest to start.
We run it on infrastructure we operate. The right choice when the data is allowed to leave and you want the pilot running this month.
Managed by us, on our terms
In banking, insurance and healthcare, the rules decide where the data sits. We built for that first.
The same stack. Only the boundary moves.
| On your servers | Your private cloud | Ours | |
|---|---|---|---|
| Agents and the review queue | Inside your network | In your account | On infrastructure we run |
| Speech models | Served on your machines | Served in your account | Served by us |
| Voice platform | Installed on site | Installed in your account | Managed by us |
| Phone lines | Your lines or ours, over SIP | Your lines or ours, over SIP | Ours |
| Recordings and documents | Never leave your network | Never leave your account | Held only for the work, on terms we agree |
How it goes when the data cannot leave.
- 01
Scope
What runs, what it needs, and who on your side can grant access.
- 02
Install
We bring the stack in. Where the rules demand it, on a machine with no outbound connection.
- 03
Pilot
The same fixed-scope pilot, on your machines, on your data.
- 04
Run
Weekly report as usual. Updates arrive on a schedule you set, carried in by hand if they must.
What we need from you
- A machine sized to the workload. We specify it after scoping.
- The network rules: what may connect to what, and what may not.
- A person who can grant access, and take it away.
What you keep
- The keys. Access is yours to grant and revoke.
- The recordings and the documents, inside your boundary.
- A log of every run, for your auditors as much as for us.
Tell us where the data has to sit.
Twenty minutes is enough to say whether we can deploy there.
A pilot starts within 5 working days of agreed scope · Nothing upfront · No seat licences