Better Stack
Monitoring
Uptime monitoring, incident management and status pages in one affordable product.
Best for: Small and mid-sized teams consolidating uptime, on-call and status pages.
193 tools · 17 categories · independent
Made in GermanyFrom end-to-end automation and QA process to load testing, real-user research and A/B experiments. Every tool listed with what it is genuinely good at — and where it will let you down.
One pick per part of the stack · how we choose
Start here
Most people arrive knowing what hurts, not what the market calls the cure. Pick what sounds familiar and we will work backwards to the tools.
“Releases keep breaking things nobody noticed”
Features that worked last week stop working and you find out from a customer.
See what fixes this“We have little or no automated testing yet”
Everything is verified by hand before release, and it does not scale.
See what fixes this“Our tests are flaky and nobody trusts them”
Red builds get re-run rather than investigated.
See what fixes this“We don't know if it works on other browsers or devices”
Safari, older Android, one specific tablet a customer keeps mentioning.
See what fixes this“We ship a mobile app and test it by hand”
Every release means someone tapping through the app on two phones.
See what fixes this“We don't know how much traffic we can take”
No idea where it breaks, or whether last week's deploy made it slower.
See what fixes this“Customers tell us about outages before our monitoring does”
Expired certificates, a broken checkout, a third party quietly failing.
See what fixes this“We can't reproduce the bugs users report”
Reports arrive without steps, environment or any technical context.
See what fixes this“Users drop off and we don't know why”
The funnel numbers are clear; the reason behind them is not.
See what fixes thisThe landscape
Seventeen categories, each with a buyer's guide covering what to evaluate and the mistakes teams make.
Write and run tests against your product.
Organise the process around the tests.
Test with real people and real traffic.
Widely adopted
Not a ranking — these are simply the ones that come up in almost every shortlist.
E2E & UI Testing
Developer-first browser testing with an interactive runner developers actually enjoy.
E2E & UI Testing
The W3C standard for browser automation. Every language, every browser, twenty years of it.
Device Cloud
The largest browser and real-device cloud, with 3,500+ device/browser combinations.
Code Quality
The static-analysis standard: 30+ languages, quality gates, clean-as-you-code.
A/B & Flags
The enterprise feature-flag platform, with experimentation layered on top.
Test Management
The most widely deployed standalone test management tool.
Monitoring
Monitoring as code: your Playwright scripts, running against production on a schedule.
User Research
Rapid unmoderated testing on live products and Figma prototypes, with quantitative output.
Tested & recommended
We only enter commercial relationships with tools we have tested and would genuinely recommend. These relationships never buy a favourable write-up or change what we publish about a tool.
Monitoring
Uptime monitoring, incident management and status pages in one affordable product.
Best for: Small and mid-sized teams consolidating uptime, on-call and status pages.
Monitoring
Free uptime monitoring for 50 endpoints. The pragmatic starting point.
Best for: Side projects, small businesses and anyone who currently has no monitoring at all.
User Research
Unmoderated tests and live interviews on prototypes and websites, in one tool.
Best for: Unmoderated tests and moderated interviews in one tool, from solo researchers to enterprise teams.
A visit link may be an affiliate link. We may earn a commission if you sign up through one, at no extra cost to you.
How this works
A directory that only lists features is a price list. These are the things we insist on for every tool.
Every entry states where the tool falls down. If we cannot name a real limitation, we have not understood the tool well enough to recommend it.
Not just the headline number but the metric that actually drives your bill — parallel sessions, screenshots, tracked users, events, seats.
The right answer depends on your stack, who writes the tests and what you can spend. The finder weighs all three rather than ranking by adoption.
Six questions about your stack, your team and your budget. You get a recommended set of tools per problem, with the reason for each pick and the caveats spelled out.
Build my testing stack