A local‑first Postman alternative

Name: DevTools
Author: DevTools

DevTools turns real traffic (HAR) into visual API flows you can export as YAML and run in CI. Download DevTools Studio.

Why teams switch from Postman

Cloud friction for simple local workflows
Script‑heavy collections that are hard to review
Painful or slow CI runs, flaky exit codes
Team drift between exported collections and reality

What DevTools does differently

HAR → flow → YAML → CI (reviewable and portable)
Automatic variable mapping with JSONPath overrides
Go‑based runner: parallel by default, JUnit/JSON reports
Local‑first, no account required

Deep dive guide

Ready to migrate collections and environments? See the Migrate from Postman guide.

Head‑to‑head

Capability	DevTools	Postman
HAR → Flow	✅ Yes	❌ No
YAML export (Git‑reviewable)	✅ Yes	⚠️ Limited
Variable mapping	✅ Automatic, rule‑based	⚠️ Often script‑heavy
Runner speed	✅ Go‑based, parallel default	⚠️ Heavier runtime in CI
Local‑first / offline	✅ 100% local; no account	⚠️ Cloud‑first defaults

Want a deeper breakdown? See the DevTools vs Postman comparison.

Migration: Postman → DevTools

Export your Postman collection and environments.
Import the HAR of your real workflow (Chrome → Save all as HAR).
Map secrets via {{#env:VAR}} and variable rules.
Export YAML and run in CI with JUnit output.

GitHub Actions

name: API tests on: [push] jobs: test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - name: Install DevTools CLI run: curl -fsSL https://sh.dev.tools/install.sh | bash - name: Run flow (JUnit) run: devtools flow run --report junit:test-results.xml api-tests.yaml

FAQ

Is DevTools open source?

Yes — desktop and CLI are open source on GitHub.

Does it work offline?

Yes. DevTools is local‑first and does not require an account.

Can I run it in CI?

Yes. The CLI outputs JUnit/JSON with clear exit codes for pipelines.

Can I import Postman collections?

Collections can be migrated; we recommend starting from a HAR to capture real workflows with fewer scripts.