Star on GitHubWhy we built this
Modern APIs ship fast — but API testing workflows haven’t kept up.
Most teams still end up with one of two bad options:
- Click-driven tools that don’t belong in Git, don’t diff cleanly, and don’t scale in CI.
- Hand-written test scripts that drift from reality, break quietly, and become maintenance debt.
We built DevTools because we lived the pain: tests that don’t reflect production traffic, workflows that can’t be reviewed properly, and “automation” that collapses the moment a team grows.
After going through YC, building products under real pressure, and learning firsthand how fragile dev workflows get when they’re not versionable, reviewable, and reproducible, we wanted a different foundation:
Start from real traffic. Make it reviewable. Make it runnable anywhere.
That’s why DevTools is built around a simple flow:
Import a HAR → generate a flow → export YAML → run in CI.
No magic. No hidden state. No “someone has it on their laptop.” Just workflows that:
- are local-first
- live in Git
- are easy to diff + review
- run reliably in CI
DevTools isn’t trying to be another dashboard. It’s trying to be the missing layer between what actually happened in production and what you can confidently ship tomorrow.
If your API workflows matter, they should be treated like code. DevTools makes that practical.