Afoxlabs Labs
Labs is our product experiment programme. A small number of genuinely free tools, each one a real production system that we develop, test, monitor and keep running using exactly the practices we sell. It is the most honest portfolio a quality company can have.
Anyone evaluating a QA partner can look at something we operate ourselves, rather than taking a case study on faith.
Problems we hit repeatedly become reusable internal tools. Some of those become the tools on this page.
Strictly secondary to the services business. Small enough to shut down without drama if nobody uses it.
The tools
Status is stated honestly below. Nothing here is announced as finished before it is, and anything that fails to earn its keep will be retired rather than quietly left to rot.
For: Developers and QA engineers
A browser-based API client that needs no account and no install. Build a request, save a collection to a shareable link, run a small suite, read the diff between two responses. Built because the established tools have grown heavy and account-gated for what is often a two-minute job.
Why this one
Directly reinforces what we do. The people who need it are the people we work with.
For: API teams and reviewers
Paste two OpenAPI or JSON Schema versions and get a plain-language breaking-change report: removed fields, narrowed types, newly required properties, changed enums. The check most teams only run after a client integration has already broken.
Why this one
Solves a real recurring pain, and it is the kind of check we build into client pipelines.
For: Teams with an automated suite they no longer trust
Upload JUnit or Playwright results from recent runs and get a ranked flakiness report — which tests are intermittent, how much CI time they waste, and whether the pattern looks like timing, shared state or a genuine intermittent bug.
Why this one
Flakiness is the single most common reason a suite stops being believed. This is our own internal tooling, made public.
For: Freelancers and small studios
A free, no-signup invoice generator that produces a clean PDF and remembers your details locally. Deliberately small: no accounting suite, no upsell ladder, no feature creep.
Why this one
The one tool here aimed at a business rather than a technical audience — a controlled experiment in whether that audience is worth serving.
Want to be told when one of these goes live? Email us and we will add you to a short list — one message per launch, nothing else.
Operating rules
Side projects are how service companies quietly lose focus. These rules exist to prevent that, and they are enforced rather than aspirational.
How we judge them
A tool with modest traffic and strong retention is worth more than one with a large launch spike and nobody coming back. These are the measures that decide whether a tool continues.
Labs is a secondary engine. The large majority of our effort goes into client work, and it should — a quality company that neglects its clients to polish side projects has failed at the one thing it sells. If you are evaluating Afoxlabs, judge us on the services and on how we work. Labs is supporting evidence, not the pitch.
Answer twelve questions about how your team tests today. You get a maturity score, the three gaps most likely to cause a production incident, and a 30/60/90-day roadmap — whether or not you ever work with us.