Limited early access
Put your app into any test state in seconds. No backend changes. No collisions.
FlowMock is a proxy for your staging API. Fabricate, reshape, and reproduce any response — each tester gets an isolated session on one shared URL.
Or see it in action belowLive, not a recording
Break the app. Watch the API story unfold.
Every request below is yours. Flip a scenario, use the app, and see exactly what Flow Mock changed.
Sound familiar?
Your Tuesday, summarized
None of this is hypothetical. It’s the actual cost of testing against a real backend — paid in minutes, favors, and Slack threads.
The 30-minute tax
You need to test the "expired token" flow. Staging won’t produce it, so you ping a dev. They change a database record. Thirty minutes later you’re finally testing — and you’ve used up your one favor for the day.
Shared staging roulette
You set the cart to "out of stock" for your test. Two minutes later someone pings: "why is the store suddenly empty?" Now you’re both debugging each other’s setup.
Can’t reproduce it
QA finds a bug that only happens in one specific account state. They describe it in Slack. The dev can’t reproduce it. Three days of back-and-forth later, it ships "as is."
Death by a thousand fixtures
Every edge case — empty state, server error, slow network, partial data — means another seed script, another redeploy, another wait. Multiply that by every test you’ll ever write.
What changes
Three ways FlowMock rewrites your Tuesday
Fabricate any state instantly
Ask a dev to change a database record. Wait for a redeploy. Hope it doesn’t break someone else’s data.
Flip a switch. Your app gets the response instantly — even states the real backend can never produce.
Applied to your session, instantly — no redeploy.
Everyone gets their own session
One shared staging environment. Mock something for your test, and you’ve just broken someone else’s.
Same proxy URL, same staging API — but your overrides apply only to your session. No collisions, ever.
One URL. Two testers. Zero collisions.
Reproduce any bug with a link
"Can you reproduce this?" Twenty Slack messages later: "works for me."
Capture the exact state that triggered the bug and share one link. The dev opens it and sees precisely what you saw.
Opens to the exact session, scenario, and overrides QA had active.
How it works
Set up in minutes, not sprints
Point your app’s API URL at FlowMock
Swap your staging base URL for your FlowMock proxy URL. One config value — no SDK, no code changes, no certificate to install.
Watch your traffic arrive, live
Every request your app makes shows up in the dashboard in real time — method, path, status, headers, and full bodies.
Mock, reshape, or record any response
Flip a switch to mock a response, edit a real one, or save a captured response as a reusable override for next time.
No certificates. No proxy install. No SDK. If you’ve ever fought Charles or mitmproxy just to get a proxy working, this is the part that feels like cheating.
Where it fits
From manual QA to your CI pipeline
FlowMock isn’t just for poking around staging by hand — the same scenarios and overrides power your automated tests too.
Manual QA & exploratory testing
Flip a scenario, hit refresh, and your app is in the exact state you need — empty cart, expired subscription, server error. No backend changes, no waiting on a dev.
Local & frontend development
Building a UI for a backend feature that isn’t ready yet, or an error state your API can’t currently return? Mock the response yourself and keep building — no blocked tickets.
CI/CD & automated tests
Point your test suite’s API base URL at a FlowMock proxy with a scenario pre-set for that run. Every test gets the exact backend state it expects — deterministic and fast, without a hand-rolled mock server to maintain.
Same proxy, same scenarios QA already built — now in CI.
Early access
We’re onboarding teams gradually
FlowMock is in early access. We’re bringing on a small number of teams at a time so we can get the details right — and actually be there when you have questions.
Founder pricing, locked in
Whatever plan you start on stays your price for as long as you’re a customer — even after we launch publicly.
A direct line to the team
Early teams shape the roadmap. Tell us what’s missing, and your edge cases become our priorities.
Generous free usage
We’re onboarding teams gradually, and early access comes with extended limits while we do.
Free to start. Paid plans for teams when we launch publicly — pricing details to come.
Join the early-access waitlistStop burning 30 minutes on test setup.
Join the early-access waitlist — early teams get founder pricing and a direct line to the people building it.