FAQ
Simplyblock is an NVMe-first, software-defined block storage platform built for Kubernetes, OpenShift, private cloud, and service-provider environments. It gives infrastructure teams a low-latency storage layer with snapshots, cloning, multi-tenancy, and operational flexibility across modern stateful workloads.
Simplyblock is shared block storage delivered as software. It is designed for environments that need predictable performance, software-defined operations, and flexible deployment across Kubernetes, OpenShift, private cloud, and related platform stacks.
Simplyblock integrates through a CSI driver, which allows teams to provision and manage storage using Kubernetes-native workflows such as StorageClasses, PersistentVolumeClaims, snapshots, and clone-related automation.
Yes. Simplyblock is designed for low-latency block-storage workloads such as databases, stateful services, VM disks, and private-cloud platform environments where one storage layer often needs to support more than one workload class.
Simplyblock is designed to keep modern block storage aligned to NVMe media, standard networking, and software-defined operations. Teams usually evaluate it when they want lower latency, cleaner day-2 operations, or a better fit for Kubernetes, OpenShift, private cloud, or VMware-exit programs.
No. Kubernetes is a major fit, but simplyblock is also relevant for OpenShift, private cloud, service-provider platforms, database-heavy environments, backup and disaster-recovery storage, and VMware exit programs where one block-storage layer needs to support more than one operating model.
NVMe over TCP gives teams a high-performance block-storage path over standard Ethernet. That makes it attractive for modern platforms that need low latency without depending on proprietary fabrics.
Software-defined storage means the storage intelligence and control plane are delivered in software rather than bound to a fixed proprietary hardware appliance. That gives teams more flexibility in deployment, scale, and operations.
Snapshots and clones are part of the storage workflow, not an afterthought. Teams use them for protection, testing, recovery, and faster stateful platform operations across databases, Kubernetes workloads, and private-cloud services.
Simplyblock is designed for environments where multiple projects, clusters, or customers share one storage foundation. That usually means tenant-aware operations, isolation controls, and encryption features that help providers and platform teams keep environments separate and secure.
Teams often evaluate simplyblock when they need storage that can support an OpenShift, Kubernetes, or private-cloud target platform without carrying older VMware or vSAN operating assumptions forward.
Simplyblock can support OpenShift-oriented storage designs where teams want vSAN-like operational outcomes such as shared low-latency block storage, snapshots, cloning, and VM or stateful-workload support without staying tied to VMware-era storage assumptions.
Simplyblock can support backup staging, replication, and disaster-recovery storage patterns where teams want one software-defined block-storage model across primary and recovery environments.
Low RPO refers to reducing how much data could be lost between failure and recovery. Low RTO refers to reducing how long service takes to recover. Strong resilience design usually needs storage that supports both efficient replication and practical recovery workflows.
Simplyblock is a strong fit for platform teams, service providers, DBaaS operators, OpenShift and Kubernetes teams, and organizations modernizing private-cloud or VMware-era infrastructure.
Yes. Simplyblock is designed for environments that may span private cloud, public cloud, secondary sites, or hybrid deployment models while still needing one coherent storage operating model.
Simplyblock is a good fit when the team needs low-latency block storage, software-defined flexibility, Kubernetes or OpenShift alignment, and a cleaner operating model for stateful workloads. It is most useful when storage needs to support more than one workload type or more than one environment.
Yes. Teams sometimes evaluate simplyblock during Ceph replacement programs when they want lower operational overhead, better NVMe efficiency, and a storage layer that stays aligned to Kubernetes, OpenShift, or private-cloud modernization.