Always reachable. Never the data.
Authorisation, identity checks and the out-of-band instruction that changes the connection state travel outside your data path.
Offline. Authorised. Connected. Offline again.
Your data stays on dedicated hardware. Access follows a controlled cycle that introduces the physical path only for an approved session, then removes it.
The cycle
Five steps, every product. Offline by default.
LUV, Vault, Storage and Enterprise follow the same connection cycle. A path is created only for an authorised session, then removed again. The access pattern depends on your product.
Two paths
The instruction and the data never share a route.
Offline is the secure state. You set it up once, then every access session is controlled. There is no standing path to attack.
Present only for the session.
The route from your network to your dedicated storage exists because an approved session needs it, and is removed when the session closes.
Access patterns
One physical model, four ways to open it.
The trigger changes by product. The behaviour does not: no standing path, a deliberate connection, approved use, then back offline.
LUVControlled windowDefined, approved access windows for low-use, high-importance data.
VaultOn demandIdentity-verified, on-demand access to dedicated professional or personal storage.
StorageWorkflow drivenScheduled or on-demand workflows using SFTP, API or approved data movement.
EnterpriseEngineeredPolicy-governed access designed around the larger environment and operating model.
Before first use
Set it up once. Control every session after.
Three things are settled before normal access begins.
- 01Design and configureDefine the protected data, capacity, access frequency and control model that suit how the information is actually used.
- 02Choose the physical deploymentA managed Firevault Bunker, a Tier 3 data centre, or for larger Storage and Enterprise architectures, your own premises.
- 03Register and onboard identitiesEstablish verified users, multi-factor authentication and permissions.
The four physicals
What sits underneath every session.
The cycle works because the foundations are physical, not policy.
- Physical storageDedicated drives with RAID 1 resilience. Never shared.
- Physical ownershipOne user, one Vault. Never pooled.
- Physical controlNo standing connection. Every session logged.
- Physical securityHeld in a Firevault Bunker, a Tier 3 data centre.
Online when you authorise it. Offline when you do not.
A secure physical state to return to. Access becomes a deliberate event, not a permanent network condition.