Adding servers, removing them, hardware refreshes, rebalancing, data tiering, software updates, hardware maintenance... all of these tasks can be done while the cluster is running and serving data at full speed.

On prem on your own servers, on the public clouds or on Kubernetes. Read more

Quobyte runs on virtual machines or bare metal instances, with local drives or cloud block storage. Learn more about our recommended cloud instances.

Synchronous quorum protection ensures data is stored on multiple servers and protects against data loss, unavailability or split-brain situations. Learn more about how Quobyte protects your data

Erasure coded files offer high performance access at very low space overhead. Learn more about how Quobyte protects your data

Policy-based recoding of files transforms replicated files to erasure coding or to wider erasure coding schemas, e.g. for archival.

The automatic file layout store small files on flash (with replication) and automatically switches to erasure coding on hard drive as the file grows. This gives you the perfect combination of high performance and price without tiering.

End-to-end cheksums do what NFS doesn't: Protect your data throught its entire lifetime, while in transit and at rest. Read more

Quobyte allows you to configure various failure domains (racks, clusters, rooms...) and what level of protection you need for your data to sustain the loss of entire failure domains.

ACLs in Quobyte are unified, i.e. Quobyte translates automatically between the different ACLs like POSIX, NFSv4 or Windows. You don't have to manage different ACLs for every platform. Read more

Quobyte supports LDAP for the management layer, for the file system (client side translation) and for access keys.

Access Keys in Quobyte can be used for S3 access but also for secure multi-user and multi-tenant access on shared machines with Kubernetes, Linux or Hadoop. Read more

X.509 certificates ensure only authorized users and machines can access the Quobyte storage. Read more

TLS can be enabled globally or only for specific networks, e.g. for access from outside a cluster. Read more

End-to-end-encryption ensures that no data leaves the client machine in clear text. Data is encrypted at rest and in transit. Read more

Full isolation of tenants with self-service and optional hardware isolation. Read more

Volume mirroring is based on a near-instantaneous mirroring of metadata and data to one or more remote Quobyte clusters for disaster recovery.

Synchronization of Quobyte volumes at regular intervals or triggered on demand, e.g. to hydrate cloud clusters.

Synchronize files in both directions between two Quobyte volumes with last-writer-wins semantics. Offers consistency similar to object storage.

Full control over how and where files are stored, immutability, tiering, caching or encryption. Read more

Automatic policy based tiering of files between storage media, pools or clusters. Read more

Admins can configure policies to automatically make files immutable after creation or to prevent deletion forever or for a pre-defined timespan.

Automatically expire (and delete) files and object based on policies or user-configurable metadata.

Quobyte provides several Quality-of-Service classes for IO and metadata operations, as well as fairness between IO and metadata operations within a QoS class.

Devices in Quobyte can be tagged to form pools (which can be overlapping) and to provide full hardware isolation, e.g. for tenants, volumes or users or to fulfil legal requirements like HIPAA or MPAA regulations.

Client configuration such as prefetching, caching, metadata caching are configured through policies and automatically applied on all clients. Changes to policies are picked up by clients within seconds. No need for local configuration on the client machines.