One install. Dvina, its data and its search index run on your own cluster, with your own storage.
Dvina for Government
Public service, kept local.
From a ministry to a city hall, every office asks one assistant. It runs on your own servers, inside your own network, under controls your security office can sign off on.



Deployment
Your servers.
Your rules.
Dvina runs inside your own network, on servers your department already trusts. Every question, every file and every answer stays on them.
One install puts Dvina on your own cluster, in your data center or in the cloud you already use. Closed-network installs, on request.

Your own network. Your proxy, your certificates, your registry mirror, under your own network’s rules.
Your own models. Connect the models you host, over your network, with your department’s certificates.
Every office
One assistant.
Every office.
From the secretary’s office to the grid control room, every team asks the same Dvina, reading only what it’s allowed to, under one set of rules.


On the drive in, Eleanor reads one page on the night’s reports, drawn from what her policy office shared.
Across the public sector
Wherever the public
is served.
A rail depot at 5 AM, a hospital ward at 2, a committee room at 11: the same Dvina, on your own servers.
- Ministries and departments
- City halls
- Courts
- Parliaments
- Defense and alliance bodies
- Central banks
- Financial regulators
- Tax and customs
- Statistics offices
- Public health
- Public hospitals
- Energy and utilities
- Ports, rail and airports
- Space and research agencies
- Public broadcasters
- Universities
- Emergency services
Models
Answers that
never leave.
Hal asks on his 11 PM round, and the answer comes from models on your own servers, over your own network, with your agency’s certificates. Or set a rule that no data leaves, and only your own models answer.

Only your own models answer.
Choose No data out, and web search and connected apps stay off. Or choose Region rule, and only models in the region you name answer.


Set once, for everyone.
Your sign-in, required. Single sign-on through your department’s identity provider, two-step verification, sessions that end, and sign-in only from your own networks.
Only what IT approves. Choose which apps and tools people can connect, and turn computer use, the browser or uploads off for everyone.
Kept as the law requires. Keep chats, files and memory from 30 days to seven years. A legal hold on one person, former staff included, or on everyone stops every delete until it’s released.
Audit
Who did what, when.
When your inspector general asks who changed a sharing rule, it’s already written down. Sign-ins, policy changes, sharing and assistant actions go into an append-only audit log. Export it as CSV or JSON, or stream it to your security tools.
Good questions.
Can we run Dvina without your cloud?
Can we run Dvina in our private cloud?
Can we use the models we already run?
How long can records be kept?
Bring Dvina to your agency.
Talk with our team about deployment, data residency and rollout.
Talk to salesKeep exploring.







































