Where the software runs decides where your data goes. Most vendors make that decision for you and call it a default. We make it explicit, because it is a governance decision before it is a technical one.
The software runs on hardware you own. Project content, credentials and vault mappings stay on the device. Provider calls go direct from you to your provider.
Data boundary. Nothing customer-side reaches Haivian Technology infrastructure.
Deployed inside infrastructure you control. You keep network control, key management and data residency.
Data boundary. Content stays inside your cloud boundary. Haivian Technology sees only what you deliberately share.
Haivian Technology runs the environment. For organizations that want the governance without running the infrastructure themselves.
Data boundary. Content processed in an environment operated by Haivian Technology under an agreed data processing arrangement.
For programs where no outbound call is acceptable. Local models only, no provider traffic, no egress at all.
Data boundary. No egress. Capability is bounded by what runs on your own hardware.
Model and quantum provider credentials are yours in every model. Haivian Technology does not resell provider capacity and does not mark up your usage. Where a hosted or private deployment needs credentials to operate, they are held under your control and used on your behalf under an agreed arrangement.
Haivian Technology holds no security certification and makes no regulatory compliance claim. There has been no third party penetration test of the products described on this site. We would rather say that plainly than let a page like this imply otherwise.