Replication and promotion
GAPrimary and replicas, restart-free promotion, rolling upgrades. You supply the failover trigger in 4.0.
QuestDB Enterprise · 30-day trial
Run Enterprise on your own workload. Then decide.
A 30-day QuestDB Enterprise trial on your own infrastructure. Your data, your queries, your criteria. We’ll email you a download link for the Enterprise trial binary within one business day.
- 01
The full Enterprise build: replication, restart-free promotion, cold storage, access control.
- 02
No discovery call. The download link arrives by email.
- 03
A named engineer on the thread for setup and migration questions (optional)
30 daysFull Enterprise trial
1 business dayDownload link in your inbox
0 callsRequired to start
Request a trial
Get a 30-day Enterprise trial.
Seven fields. We’ll email you a download link for the Enterprise trial binary within one business day.
Published benchmarks
Our numbers are public.
The trial gets you yours.
Every figure below is published with its method and runs on default settings. Treat them as a starting hypothesis and use the trial to test them against your own row shapes and queries.
19M
Rows/sec/server ingestion
220M
Rows/sec streamed to Arrow
2.3s
To stream 500M rows
32ms
First Arrow batch
Published QWP benchmark results on
QuestDB v10.0QuestDB vs
ClickhouseTSBS cpu-only ingestion on identical hardware, 32 workers, at 100K hosts.
up to 5xfaster ingestion
1.75M rows/s
8.59M rows/s
8.59M rows/sQuestDB vs
TigerDataFormerly Timescale. Same TSBS dataset, same schema and batch size, at 100K hosts.
8xfaster ingestion
1.08M rows/s8.59M rows/s
8.59M rows/sQuestDB vs
InfluxDBTSBS cpu-only, InfluxDB v1.12, at 100K hosts.
16xfaster ingestion
541K rows/s8.59M rows/s
8.59M rows/sQuestDB vs
kdb+No figure allowed.
The kdb+ DeWitt clause prohibits published head-to-heads, so none can appear on this page. Running QuestDB beside it for 30 days is how you get that number.
kdb+ evaluation guideWhat the trial includes
The full Enterprise build,
not a demo tier.
Enterprise 4.0, built on QuestDB 10. A dedicated trial build with the Enterprise features below, with status labels as published in the release notes.
Cold storage tiering
GAOld partitions move to S3, Azure Blob or NFS and stay in the same table. Plain Parquet that other tools read in place.
Access control
GARole-based grants, single sign-on and TLS across every protocol.
QWP client failover
GAStore-and-forward on writes, resumable streams on reads. One connect string across all nodes.
Replicated live views
BETARolling VWAP, cumulative volume and running ranks kept current on every node of the cluster.
An engineer on the thread
OPTIONALSetup, schema and migration questions answered by the people who build the database.
A fair evaluation
Six things to test
in your 30 days.
Use production-shaped data, not a synthetic bulk load that hides the behaviour your live system depends on. Swap any line for your own criteria.
01
Your real ingest shape
MeasureSustained rows per second at 1, 10, 1K and 10K rows per batch, with your real out-of-order rate.
Look forThroughput that holds without tuning.
02
Time to query
MeasureThe gap between a write being accepted and the row appearing in a query.
Look forOne number, not three stages that each report success.
03
Queries under ingest
Measurep50 and p99 for dashboards and ad-hoc queries during peak ingestion.
Look forRead latency that stays flat as writes climb.
04
Hot and cold in one statement
MeasureA query spanning today and last year once a storage policy has tiered old partitions to your bucket.
Look forThe same SQL, and the storage bill.
05
Failover and upgrade
MeasureRows lost or duplicated when you kill the primary mid-ingest and promote a replica. Then roll an upgrade.
Look forZero gaps with DEDUP keys set, no client redeploy.
06
Access control, built in
MeasureHow long it takes to map your desks, teams and service accounts onto roles and grants, with SSO in front.
Look forRBAC enforced by the database itself. kdb+ ships without it, so that layer is one you build and maintain.
Running it beside an incumbent? Use the specific checklist.
How the trial runs
Three stages.
No forced migration.
Day 0
Request
Seven fields. The confirmation page carries the test checklist and the Docker one-liner while you wait.
Day 1
Download and setup
Within one business day, we’ll email you a download link for the Enterprise trial binary, setup in three steps, and replication and cold-storage guides. A named engineer on the thread.
Days 2–30
Run it in parallel
Point your producers at both systems and keep production untouched. Check-ins on day 7 and day 21 if you want them.
Critical infrastructure runs on QuestDB
“QuestDB brings a SQL-first solution that is easy to connect to our existing tools and able to ingest data at speed. Their commitment to open standards and close collaboration gives us confidence.”
Denys Rtveliashvili
Head of Data, Laser Digital (Nomura Group)
“QuestDB is an essential part of our trading platform, giving us a high-speed, scalable store for billions of trades that we can query in real time.”
Steven Harper
Chief Security Officer, One Trading
Trial FAQ
QuestDB Enterprise trial:
the practical questions.
Do I have to talk to sales first?
No. Submit the form and we’ll email you a download link for the Enterprise trial binary within one business day. Engineering help is there if you ask for it.
What does the trial include?
The full Enterprise 4.0 build: replication, restart-free promotion, cold storage tiering, access control and the QWP clients.
Are there limits on cores or nodes?
You can test on any setup and hardware, with no limits on cores or nodes. The trial license agreement permits use for testing and development only. The trial binary must not be used for any production workload.
What happens on day 31?
The trial binary will not abruptly stop when the 30-day trial ends, but once shut down after that point, it will not restart. The trial binary must never be used for live production workloads. To continue using Enterprise, send us a request for an Enterprise license or a trial extension, including your rationale for the extension.
I already run QuestDB open source. Can I start from that?
Yes. The documented path takes an existing open-source instance to Enterprise in place: Migrate to Enterprise →
Does it work on-prem or air-gapped?
The trial is self-managed on your own infrastructure. Pick On-prem in the form and the setup email is written for that.
Thirty days. Your data. Your numbers.
One representative workload, the full Enterprise build, direct engineering support, and no requirement to replace the rest of your stack.