Teams running TrueNAS, FreeNAS, or other ZFS-based storage systems often need a way to provide Kubernetes PVC lifecycle management without replacing their existing storage hardware. democratic-csi is an open-source CSI driver project that provides Kubernetes storage integration for these systems, supporting iSCSI, NFS, SMB, and — experimentally — NVMe/TCP as protocols for backing Kubernetes PersistentVolumes.
The project fills a genuine gap: before democratic-csi, teams with TrueNAS or ZFS-based storage had limited options for Kubernetes-native volume management. The driver handles dynamic provisioning, volume deletion, resize, and snapshot operations through the CSI API. The question of when to use it — and when to move beyond it — depends on the maturity and scale requirements of the environment.
How democratic-csi Works
democratic-csi implements the CSI gRPC API and translates Kubernetes volume lifecycle operations into API calls or CLI commands against the target storage backend. For TrueNAS backends, it uses the TrueNAS REST API to create ZFS datasets or zvols, configure iSCSI targets, NFS exports, or SMB shares, and map those back to Kubernetes PersistentVolumes.
The driver supports multiple transport protocols. For block storage, iSCSI is the most mature and widely used. NFS and SMB serve file-mode workloads requiring ReadWriteMany access. An experimental NVMe/TCP driver was added more recently, though production readiness of the NVMe/TCP backend has lagged behind the iSCSI implementation.
Deployment typically uses Helm. The driver runs as a DaemonSet and StatefulSet in the cluster; configuration is provided via a ConfigMap that specifies the backend driver type, API endpoint, and credentials for the TrueNAS API.
Use Cases and Supported Backends
democratic-csi works best in homelab, small enterprise, or on-premises environments where the team already has TrueNAS or ZFS-based storage and needs Kubernetes PVC management without replacing the storage platform.
Supported backend types include:
- TrueNAS SCALE and CORE via the REST API
- FreeNAS (legacy, pre-SCALE versions)
- Generic ZFS over SSH for other ZFS-based systems
- Synology NAS (via NFS or iSCSI, limited feature set)
The driver’s strength is breadth of backend support. Its limitation is that support quality varies by backend — TrueNAS SCALE is the most actively maintained target, while less common backends may lag on feature support or bug fixes.
🚀 Ready for sub-millisecond latency and enterprise SLOs beyond democratic-csi? Simplyblock provides a purpose-built NVMe/TCP and NVMe/RoCE CSI driver with multi-tenant QoS, instant snapshots, and production-grade support — for teams that have outgrown community-maintained drivers. 👉 Learn about the simplyblock CSI driver
Limitations of democratic-csi in Production Environments
democratic-csi is community-maintained software. This has practical implications for teams evaluating it for production:
No commercial support: There is no SLA-backed support contract. Issues are resolved through GitHub, community forums, or by the team’s own engineers. For regulated industries or applications with strict uptime SLAs, this is a meaningful constraint.
Variable feature velocity: Feature development depends on community contributions. NVMe/TCP support, multi-tenancy, and advanced QoS features have lower velocity than in commercially supported drivers.
Backend dependency: Performance and reliability depend on TrueNAS or the underlying ZFS system. democratic-csi does not provide an independent data plane — it orchestrates operations through the backend’s own API. This means latency, IOPS, and durability are bounded by the TrueNAS hardware and ZFS configuration.
Limited multi-tenancy: Access controls and performance isolation between namespaces or tenants are handled at the ZFS dataset level. This is functional but limited compared to purpose-built multi-tenant storage platforms.
| Factor | democratic-csi | NetApp Trident | simplyblock CSI |
|---|---|---|---|
| Supported backends | TrueNAS, ZFS-based NAS/SAN | ONTAP, SolidFire, E-Series | simplyblock NVMe storage |
| Enterprise support | Community only (MIT) | NetApp commercial support | Commercial SLA support |
| NVMe/TCP native | Experimental | Limited (ONTAP NVMe/TCP) | Primary transport |
| QoS / multi-tenancy | ZFS-level, limited | Policy-based, per backend | Per-PVC IOPS and BW limits |
| Kubernetes version support | Community-tracked | Commercially maintained | Commercially maintained |
| Production readiness | Community assessment | Enterprise-validated | Enterprise-validated |
When to Move from democratic-csi to an Enterprise CSI Driver
democratic-csi is a reasonable choice for smaller environments, dev/test clusters, or teams with existing TrueNAS hardware that need basic Kubernetes PVC lifecycle management at low cost. Several signals indicate it is time to evaluate an alternative:
- Sub-millisecond latency is required: democratic-csi with iSCSI over spinning disk or HDD-backed ZFS cannot deliver the latency profile that production databases and analytics engines need.
- Production SLOs require support contracts: When storage downtime has business impact and requires SLA coverage, community-only support is not sufficient.
- Multi-tenancy and QoS are needed: Multiple teams or namespaces sharing storage need per-workload performance guarantees that ZFS-level controls cannot provide cleanly.
- NVMe performance is required: If the environment is moving to NVMe drives or NVMe/TCP networking, a purpose-built NVMe CSI driver delivers significantly better performance than democratic-csi’s experimental NVMe/TCP backend.
How Simplyblock Compares to democratic-csi
The simplyblock CSI driver is purpose-built for NVMe/TCP and NVMe/RoCE block storage with enterprise-grade QoS, multi-tenancy, and instant copy-on-write snapshot support out of the box. It is not a bridge to an existing NAS system — it is the data plane itself, delivering sub-millisecond latency directly to Kubernetes PVCs.
Teams using democratic-csi with TrueNAS often migrate to simplyblock when they need sub-millisecond latency for database workloads, production-grade SLOs with support contracts, per-PVC QoS isolation for multi-tenant environments, or enterprise snapshot and replication capabilities for DR. The migration path replaces the CSI driver and storage backend; application PVCs can be migrated using snapshot-based restore or application-level data migration depending on downtime tolerance.
Compared to iSCSI-based approaches, NVMe/TCP provides lower overhead per I/O operation and better utilization of modern multi-core storage nodes. For teams who used democratic-csi as a path into Kubernetes storage, simplyblock represents the next step when performance and reliability requirements grow beyond what community drivers over iSCSI can deliver. For teams comparing against NetApp Trident, the comparison is primarily on hardware independence — simplyblock runs on commodity x86 NVMe hardware, while Trident requires NetApp storage systems.
Related Terms
These pages cover related CSI driver, protocol, and storage concepts for teams evaluating Kubernetes storage options.
Questions and Answers
What is democratic-csi in Kubernetes?
democratic-csi is an open-source, community-maintained CSI (Container Storage Interface) driver that enables Kubernetes clusters to use TrueNAS, FreeNAS, and other ZFS-based storage systems for PersistentVolume lifecycle management. It supports dynamic volume provisioning, deletion, resize, and snapshot operations through the Kubernetes CSI API, translating those operations into calls to the TrueNAS REST API or ZFS over SSH. It is available under the MIT license and maintained primarily through GitHub community contributions.
Does democratic-csi support TrueNAS?
Yes, TrueNAS SCALE and TrueNAS CORE are the most actively supported backends for democratic-csi. The driver uses the TrueNAS REST API to manage ZFS datasets and zvols, configure iSCSI targets and NFS exports, and handle volume lifecycle operations on behalf of Kubernetes. TrueNAS SCALE (Linux-based) is the most current and best-supported target; CORE (FreeBSD-based) is also supported but sees less active development for new features.
How does democratic-csi compare to NetApp Trident?
Both are CSI drivers that connect Kubernetes to external storage backends, but they target different hardware ecosystems. democratic-csi targets community and open-source storage systems (TrueNAS, ZFS-based NAS); Trident targets NetApp ONTAP, SolidFire, and E-Series commercial storage arrays. Trident is commercially supported by NetApp and has enterprise-grade QoS, multi-tenancy, and backend feature integration. democratic-csi is community-maintained with no commercial support contract. A team choosing between the two is usually also choosing between keeping existing TrueNAS hardware versus investing in NetApp systems.
When should I move from democratic-csi to an enterprise CSI driver?
The main triggers are: performance requirements that exceed what iSCSI over TrueNAS can deliver (sub-millisecond latency for databases or high IOPS for vector stores), production SLA requirements that need a support contract rather than community-only assistance, multi-tenant environments where per-workload QoS is needed, or scale growth where the TrueNAS backend becomes the storage bottleneck. When those requirements emerge, purpose-built NVMe/TCP drivers like simplyblock’s CSI driver provide the performance tier and enterprise-grade support that community drivers cannot match.