Httrace captures real production traffic and automatically generates integration tests — without you writing a single line.
Developers spend entire sprints writing tests based on what they think users do. Real users always find something else.
Your test suite passes. Production breaks. The scenario existed in your traffic logs the whole time — you just didn't know it.
Deadlines kill test coverage. Every "we'll add tests later" endpoint is a future incident waiting to happen.
Add Httrace to your Python project. One package, one line of code.
Add the middleware to your app. Real traffic is captured, PII is removed automatically.
Run one command. Httrace writes real pytest files into your repo, ready to commit.
Your API key unlocks everything. Here's exactly what happens after you join.
After signing up, you receive a personal ht_ API key via email. It identifies your account and tracks your monthly usage against your plan.
Install via pip and register the middleware in your FastAPI, Flask, or Django app. The key goes in your environment variables — never hardcoded.
Once the middleware is active, every real HTTP request is captured in the background. PII (emails, tokens, card numbers) is stripped before anything leaves your server.
Run httrace generate from your project root. Httrace writes real pytest files to your repo — ready to commit and run in CI.
Use httrace status to see which endpoints are covered and how many captures remain in your monthly quota.
* Feature comparison based on publicly available documentation as of April 2026. Subject to change.
| Feature | Httrace | Keploy | Speedscale | GoReplay |
|---|---|---|---|---|
| Generates real test code (not just replay) | ✓ | ✓ | ✕ | ✕ |
| No root / kernel access required | ✓ | eBPF mode only | ✕ | ✓ |
| No Kubernetes required | ✓ | ✓ | ✕ | ✓ |
| Managed SaaS (no self-hosting) | ✓ | ✕ | ✓ | ✕ |
| PII sanitization built-in | ✓ | ✕ | Partial | ✕ |
| Auto-generated test fixtures | ✓ | Partial | ✕ | ✕ |
| GitHub Actions integration | Coming soon | ✕ | Partial | ✕ |
| Works with pytest / Jest / RSpec | ✓ | Go / JS only | ✕ | ✕ |
| EU data residency (GDPR) | ✓ | Self-hosted only | ✕ | Self-hosted only |
| Free tier available | ✓ | ✓ | ✕ | ✓ |
For solo developers and open-source projects.
For early-stage startups shipping fast.
For scale-ups with real traffic and real stakes.
For teams that need control, compliance, and SLAs.
Httrace sits inside your production stack. We don't take that lightly.
Passwords, tokens, credit card numbers, emails, and IBANs are automatically scrubbed before any data leaves your server.
All traffic is sent over TLS 1.3. Data at rest is encrypted with AES-256. No plaintext request bodies are stored.
Data is stored exclusively on EU servers. No cross-border transfers. Full GDPR compliance out of the box.
The capture middleware is MIT-licensed and fully auditable. Know exactly what runs inside your stack before you ship it.
Set retention periods per service. Payloads are purged automatically — only the generated test code remains.
Run the entire Httrace stack inside your own VPC. Zero data leaves your infrastructure.
password, token, ssn, and (2) regex patterns that detect credit cards, IBANs, JWTs, emails, and phone numbers in values. Matched fields are replaced with placeholder strings in generated test fixtures.sample_rate=0.1 (the default). At 100% sample rate, expect ~8ms overhead. We recommend 5–10% sampling in production.Manual test writing is the last major bottleneck in modern CI/CD. Httrace eliminates it by treating your production traffic as ground truth. Every real user interaction becomes a test — permanently.
Talk to the founders →Join already on the list. Early access. Founding team pricing.
No spam. Early access. Founding team pricing.