DevTools
YFrom a YC alum • previously exited

From real traffic to CI-ready API workflows.

Import a HAR → generate a flow → export YAML → run in CI.

Local-first. Git-reviewable. CI-ready.

  • HAR → flow steps + mapping
  • YAML export for PR review
  • CLI reports (JUnit/JSON, exit codes)
Download StudioInstall CLI
DevTools main workspace screenshot
ParallelBy default
CI outputsJUnit/JSON
Local-firstNo cloud
How it works

Record → Flow → YAML → CI

Quick mental model: visual API workflows with Git‑native YAML export. Flows you can review and run in CI.

Import a HAR file into DevTools

Record real traffic

Capture a HAR from your browser or proxy and drag it into DevTools. We’ll parse requests and auth headers automatically.

  • • Chrome DevTools → Save all as HAR
  • • Sensitive data safe: process happens locally
How to record a HAR•Importing HAR files

Map variables across steps

Extract tokens and IDs from responses and map them to subsequent requests. Fine‑tune with JSONPath‑based overrides.

  • • Auto‑mapped variables from responses
  • • Override rules per step
Variables in flows
Variables mapped and used in flow
Flow canvas visual overview

Build and refine flows

Use a visual canvas to organize requests, set assertions, and add flow‑level logic. Keep reviews clean with YAML export.

Learn how flows work

Export to YAML and run in CI

YAML‑native by design: export human‑readable flows for Git review, then run locally or in CI with clear exit codes and reports.

  • • Git‑reviewable flow definitions
  • • CLI reports (JUnit/JSON, exit codes)
How to export YAML•YAML flow format
CLI JSON report and CI‑friendly output
Roadmap

Scale when you're ready

Run flows locally and in CI for free. When your suite needs more, scale with DevTools Cloud (Roadmap) or self‑host executors.

DevTools Cloud adds

  • • Scheduling
  • • Multi‑region runs
  • • Shared secrets/environments
  • • RBAC + audit log
  • • Hosted executors + autoscaling
  • • Run history + dashboards

Self‑host executors add

  • • Run in your VPC
  • • Your data residency
  • • Your infra control
Comparison

DevTools vs Bruno vs Postman

See how the tooling stacks up when you care about local-first flows, Git-friendly exports, and speed.

Postman alternative →Bruno alternative →DevTools vs Postman →DevTools vs Bruno →
Capability / ConcernDevToolsBrunoPostman
Open source✅ OSS (desktop + CLI)✅ OSS❌ Closed; cloud-centric
Flows (visual + reusable)✅ Flow trees from HAR; visual builder❌ No flows⚠️ Flows available; export limited
HAR → Flow (auto-build from real traffic)✅ Yes❌ No❌ No
YAML export of flows (Git-reviewable)✅ Yes (per-step overrides)❌ No❌ No (not for Flows)
Variable mapping (step-scoped, JSONPath)✅ Automatic, rule‑based (overrides)⚠️ Basic vars⚠️ Mixed; often script-heavy
Assertions & evals (flow-level)✅ Rich assertions at flow level⚠️ Limited⚠️ Mixed; tends to rely on scripts
Performance testing & regional locations🚧 Roadmap (designed pricing)❌ No⚠️ Separate add‑ons/monitors
Runner tech & speed✅ Go-based, multithreaded; parallel by default⚠️ JS runtime; slower at scale⚠️ Heavier runtime; slower in CI
Local-first / offline✅ 100% local; no accounts✅ Local⚠️ Cloud-first; login + sync
Scripting model✅ Logic in flows (clean reviews)⚠️ Limited⚠️ Often per-request scripts
CI/CD integration✅ CLI + JUnit/console outputs⚠️ Basic⚠️ Possible but heavier, cloud-dependent
Collaboration & dependency✅ No account required; local‑first✅ Local; no account⚠️ Requires account for collaboration; cloud‑dependent features