What you get on the platform
One platform. Standard protocols. Strong defaults.
Customers don’t buy storage technology — they buy outcomes. Below is what the platform will do for the applications and operators on top of it. Built on industry-standard, open-source storage technology — the same building blocks that power hyperscale clouds, hardened by us.
Multi-protocol
- BlockNVMe-class low-latency volumes for databases, VMs, and inference workloads.
- ObjectS3-compatible buckets for AI training data, lakehouses, and backups.
- FileParallel file (NFS) and SMB shares — no proprietary client driver required.
Encryption & keys
- At restTwo-layer encryption — self-encrypting drives plus volume-level keys.
- In transitTLS 1.3 across cluster traffic and client connections.
- Key managementCustomer-controlled key broker; per-tenant key namespaces.
Tamper-evidence
- WORM retentionObject-lock retention with policy-driven expiry windows.
- Public-chain anchoringCryptographic proof of integrity verifiable without trusting us.
- Open-source verifierAuditors run the check themselves — no vendor lock on evidence.
Operations
- Single consoleOne UI, one API, one tenancy model across all storage profiles.
- Kubernetes-nativeCSI driver and operator for block, file, and object volumes.
- Air-gap supportSigned-bundle updates; no outbound vendor telemetry by default.
Form factors
- Cloud-scale rackStandard rack servers for AI clusters and audit deployments.
- Ruggedised edgeShort-depth, environmentally-hardened servers for forward and tactical sites.
- GPU-convergedStorage and compute on the same fabric for AI training and inference.
No lock-in
- Open foundationsBuilt on production-grade open-source storage technology, hardened for enterprise.
- Standard protocolsNo proprietary client drivers; your apps connect with what they already speak.
- Hardware portabilityStandards-based hardware management; not coupled to a single vendor.
Engineering principle:
we build on industry-standard, open-source storage technology where it’s proven, contribute upstream rather than fork, and concentrate our own engineering on the unified control plane and operator experience. Deep technical conversation about the stack? Come and talk to us under NDA.