ekoDB is live. Start building for free
Why ekoDB / Performance
Performance that speaks for itself
Powered by Rust, ekoDB's proprietary database engine is capable of remarkable throughput and sub-ms latency across a variety of workloads. Every figure on this page is read from the benchmark artifact we publish. See for yourself how our performance compares to that of some of the world's top databases.
Benchmarks
Measured against the systems you already run
No benchmark run is published right now. Figures return here as soon as one passes the publish gates. Nothing on this page is typed in by hand, so there is nothing to show in the meantime.
Methodology
How these numbers are produced
Document engines are compared in durable mode with matching fsync settings, and key-value in cache mode. Running one engine durable against another buffered is the easiest way to produce a flattering chart, so the run does not do it.
ekoDB is measured with auth, per-operation encryption, and search indexing switched on. The engines it is compared against do not carry those costs in their numbers, so the comparison is unfavourable to us by construction and we publish it that way.
These runs are driven over ekoDB's internal cluster transport rather than the HTTPS, WebSocket, and SSE endpoints an application connects on. Those carry protocol and TLS overhead the harness does not, so treat these as engine throughput rather than as end-to-end numbers for your own client. Measuring the customer transports is tracked and will be published the same way, from the same artifact, once it runs.
The published artifact this page reads from can be found here. For the full write-up, see the performance reference in the docs.
Go deeper
Explore more about ekoDB
Try ekoDB free
Deploy your first database in minutes. No credit card required.