GoKawiilJepsen audits Orkes' ParticleDB 1.1.4 database ahead of wider release
Orkes, maker of the Conductor workflow platform, commissioned Jepsen to test its in-house database ParticleDB, starting with version 1.1.4. ParticleDB combines SQL, key-value storage, vector search and analytics in one Rust-built engine, and can run as a single node or as a Raft-based replicated cluster, though replication is limited to enterprise cloud deployments. Orkes had already used an earlier 1.0.0 build internally and with some customers before refactoring the system for a broader public release via particledb.ai.
GoKawiil's interpretation of the reporting above, not reported fact.
Independent verification from Jepsen carries weight in the database community because it probes consistency and fault-tolerance claims that vendors often cannot fully test themselves. Orkes building its own database instead of relying on Postgres or Redis suggests a strategic bet on performance for its orchestration product, but the move also raises the stakes of ensuring correctness as it opens ParticleDB to outside customers. The findings could shape trust in ParticleDB as Orkes pushes it beyond internal use toward general availability.
- ParticleDB is a multi-model Rust database built by Orkes to replace Redis and Postgres in its Conductor platform.
- Jepsen was engaged to evaluate ParticleDB 1.1.4 as Orkes prepares a broader public release.
- Replication via Raft consensus is only available in enterprise cloud deployments, and the tested builds lacked full support for it.
Source: jepsen.io — Kyle Kingsbury, 2026-10-31
Published there as: “Jepsen: ParticleDB 1.1.4”
Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.