Dvina can run in our cloud, on your own servers, or on a small server in your office. Every way gives you the same Dvina. What changes is where it runs, where your data stays and which models answer.
Enterprise Cloud
We host and run it, with your company's controls from day one.
- Getting started: live in days.
- Your data: stays in the EU.
- Network: over the internet, encrypted.
- Models: ours, or the ones you choose.
- Controls: every enterprise control, like single sign-on, policies and the audit log.
It's the fastest way to start.
Enterprise Sovereign
Dvina installs in your own cluster, under your control, for institutions that keep everything in house.
- Where it runs: your own cluster, in your data center or in the private cloud you already use.
- Getting started: one install, then your team runs it from there.
- Your data: stays in your data center. Dvina, its data and its search index run on your cluster, with your own storage.
- Network: your own network, with your proxy, your certificates and your registry mirror. Closed-network installs, on request.
- Models: your own, on your servers, connected over your network with your own certificates.
- Controls: every enterprise control.
Sign-in and licensing connect to Dvina.
A server in your office
For a small business, a studio or a startup, Dvina can run on a Mac Studio or an NVIDIA DGX Spark in your office, with local models that run right on it. What you ask, upload and connect stays on your own network, so client files that can't leave the office don't have to.
You don't need your own server to start. Start free in the cloud, and move to a server in your office when files must stay in the building.
Government
Dvina runs on your agency's own servers, inside your own network, or in your agency's private cloud, under the rules your security office sets. Every question, every file and every answer stays on them, in your agency's own country. Connect the models you already host, with your department's certificates. See Dvina for Government.
Choose where your data may go
Admins choose a Data policy in Settings › Model:
- Standard: your models first, and Dvina's fill in the rest.
- No data out: only your company's own models are used. Web search, connected apps and maps are off.
- Region rule: only models in the region you name are used, Dvina's included.
Good to know
- Nothing your people write, upload or connect trains a model.
- To plan a deployment, talk to sales. We'll set up a demo and a plan that fits your company.
If your server can't reach Dvina's licensing
When Dvina runs on your own servers, it checks your plan with Dvina. If it can't, nothing changes at first:
- After 3 days: Admins and billing admins see one quiet row in Settings and in Plan & Usage: Billing unreachable since and the date. It says when the Livespace turns read-only if the connection doesn't come back. Everything else works as usual.
- After 30 days, by default: The Livespace turns read-only, and the row says Read-only: billing unreachable since and the date. Everyone can still read and export. Changes, like new messages and edits, are off until the connection is back.
As soon as Dvina is reached again, everything works again on its own. If Dvina refuses your installation's credential, admins see Billing refused this installation's credential; ask whoever runs your installation to check it.