Evaluate your workload in a pilot
Agree on success criteria, test your workload on a dedicated instance and review the results with our team.
Scope, load, test, report.
- Week 1
Scope
Data shapes, query patterns, expected volumes, availability target, region. We write the success criteria together — latency, recall, throughput, cost — and agree how each will be measured.
- Week 2
Load
A dedicated instance is provisioned in your region (under two minutes). Your data lands through the SDK or HTTP API; schemas, indexes and the natural-language layer are configured against real queries.
- Week 3
Integrate & test
Your service talks to the instance. We run the agreed benchmarks side by side with your current stack, on the same data, and record the numbers.
- Week 4
Report
A written report: every criterion, the measured result, the configuration that produced it and its monthly price. You decide with numbers, not a demo.
- → A representative slice of the data (or a generator that produces its shape).
- → Ten to twenty real queries, including the slow ones.
- → The numbers that matter to you and the thresholds that make the pilot a pass.
- → One engineer who can wire a client and read a dashboard.
- → A dedicated, single-tenant instance in your region for the duration.
- → A named engineer on a shared channel throughout.
- → Benchmark harnesses for the agreed criteria, with reproducible scripts.
- → The report, and a sized configuration with a written quote.
After the pilot, the numbers decide.
After the pilot, the same configuration continues at the published price — $570 / month for the default configuration, before add-ons — or you walk away with the report.
Ready to measure? Send the workload.
Tell us the data shapes, the volumes and the numbers you care about. We reply with a proposed scope.