Skip to main content
Historical record, not current figures. These numbers were measured on QWED v1.1.0 in December 2025. The engines, their checks and the fail-closed behaviour have changed a great deal since then, so latency on the current release will differ. Measure on your own workload and hardware before relying on any figure. QWED’s current evaluation results are at qwedai.tech/evidence.Cost comparisons, hosted pricing, an ROI calculator and comparisons with other tools previously on this page were removed: none of them had a reproducible source.
Test environment (December 2025):
  • Hardware: AWS EC2 t3.medium (2 vCPU, 4GB RAM)
  • Python: 3.11
  • QWED: v1.1.0
  • Date: December 2025

Latency (v1.1.0)

Verification engine latency

Observations at the time

  • Most single-engine checks finished in under 100ms on this hardware.
  • ⚠️ Symbolic execution was slow: use it only for simple functions.
  • ⚠️ Consensus was expensive: it makes several LLM API calls.

Latency optimization tips

1. Enable Redis caching

2. Async verification

3. Selective engines

4. Timeout tuning


Throughput (v1.1.0)

These figures came from the same December 2025 environment. Size your own deployment from your own load tests.

Need help measuring? Contact: support@qwedai.com