Positioning
Exaba is software-defined object storage that service providers and operators run on their own hardware. Because it is software rather than a proprietary appliance, partners are free to choose how they deploy it: as a highly available cluster, an edge appliance, an OEM-embedded product, or a self-operated air-gapped install.
Who Exaba is for
| Market | What they do with Exaba |
|---|---|
| Cloud service providers | Offer multi-tenant storage-as-a-service, billed under their own brand. |
| Managed service providers | Run backup and storage services for clients; white-label and multi-tenant. |
| Data-centre operators | Provide branded storage to downstream providers on their own infrastructure. |
| Sovereign & regulated operators | Keep data in-country for backup, archive, and compliance, including air-gapped sites. |
| OEM & technology partners | Package and ship Exaba within their own product, appliance, or cloud offering. |
How Exaba can be deployed
Exaba is the same software in every case; the deployment model is the partner’s choice.
| Deployment model | Description |
|---|---|
| Cluster (HA) | A multi-node, highly available cluster of three or more nodes for production workloads, and the standard deployment for connected sites. Exaba installs, configures, and monitors the cluster as a managed service; your team provides first-line support and owns the customer relationship. |
| Edge | A compact single-node footprint for remote or branch sites, delivered as a virtual or physical appliance. |
| OEM / embedded | An OEM partner packages and ships Exaba inside their own product or appliance, under their own brand. |
| Air-gapped (sovereign) | The partner installs and self-operates Exaba in sovereign or dark-site environments with no outbound connectivity. |
| Docker | A containerised single-node deployment for evaluation and development environments. Not intended for production use. |