About the Founder
Built by one developer
This page is the straight answer to "who actually built API Test Lab, and can I trust them?" No fake team grid — just the person behind the product, how it got here, and what you should expect.
Who built this
API Test Lab is a solo-founder product. I'm Abubakkar Sajid, a developer based in Lahore, Pakistan. I built this because I was frustrated paying for multiple tools to do what should be one job — API testing, load testing, and web analysis together. The full product story lives on the about page; this page is about the person and the process.
Abubakkar Sajid
Founder & Developer
Lahore, Pakistan
The story so far
The timeline below matches what we publish on the company story. I am not going to invent vanity metrics — if a milestone does not have a public number attached, it stays qualitative.
Early 2026
The problem showed up in daily work
I was running three API-heavy projects at once. Postman for exploring endpoints, a separate tool for load tests, another for uptime checks, and a spreadsheet to track what broke. Postman kept raising prices while load testing still meant switching products. That friction is what pushed me to build something for myself first.
January 2026
First working prototype
I built the first unified REST tester and load tester in about three weeks, mostly evenings and weekends. One browser tab instead of three apps. I shared it with a few developers I knew; they asked to keep using it.
February–March 2026
Early access and direct feedback
An early-access program opened for developers who signed up ahead of launch. Every bug report and feature request went straight to me — no product committee, no ticket router. That feedback shaped what shipped next.
April 2026
Public launch
The free tier opened with no credit card required. Pro and Max plans followed at flat monthly pricing. Shortly after launch, load testing and monitoring stayed in the same workflow instead of being bolted on as separate products.
After launch
Expanding the same workspace
In the months following public launch, the product grew into a fuller testing workspace — including a dedicated GraphQL tester, AI-assisted response explanations, and directory listings on independent SaaS platforms. The goal stayed the same: one place to test, load-test, and monitor without enterprise bloat.
How I actually build this
API Test Lab is developed solo — design, backend integration, frontend, billing, docs, and support emails. There is no separate QA department or roadmap committee. When something hurts in my own workflow, or when a user emails a clear pain point, it goes on the short list.
Prioritization is simple: fix broken things first, then ship improvements that reduce tool-switching for API work. Features like load testing and the GraphQL tester landed because real testing sessions needed them — not because a slide deck said they should exist.
Bugs get fixed by the same person who introduced them. That is not a corporate process — it is just how solo development works when you care about the product still working tomorrow. You can see how plans are priced and what ships on each tier on the pricing page.
What's different about a solo-built tool
I will not pretend a one-person product offers the same coverage as a vendor with a 24/7 support floor and an enterprise SLA. If you need that level of contractual guarantee today, you should compare established platforms — honestly, our compare page exists for that reason.
What you do get is direct access to the builder. When you email hello@apitestlab.org, I read it. When you hit a regression, I can often patch it quickly because there is no bureaucracy between "reported" and "assigned." Decisions are made in days, not quarters.
That tradeoff fits solo developers, freelancers, and small teams who want a fast browser-based workflow without paying for five subscriptions. It is not the right fit for every enterprise procurement checklist — and I would rather tell you that upfront than oversell. If you are evaluating how credentials and auth tokens are handled before entering them in the tester, see our dedicated security page for a verified, honest technical breakdown.
Frequently asked questions
Questions people actually ask before trusting a solo-founder testing tool. Curious how your API keys and auth tokens are handled? Check our security practices. For product mechanics, see the main FAQ; for tool comparisons, read Postman vs API Test Lab on the blog.
- Is this actually a real company or just a side project?
- API Test Lab is a real product with paid plans, a public privacy policy, and ongoing development — but it is honestly a solo-founder operation, not a 200-person SaaS company. I treat it as my primary product work: public pricing, documented API access, and regular shipping. It is smaller than Postman by design, not by accident.
- What happens to my data if you stop working on this?
- Your saved requests, collections, and account data are stored on infrastructure I maintain for the product. If I ever wind the service down, I would give advance notice, export options, and a clear timeline — the same way any responsible SaaS should. Today the product is actively maintained and launched publicly in April 2026. If long-term continuity is critical for your team, email me directly and we can talk about your workflow honestly.
- How fast do you fix bugs?
- Most reproducible bugs reported by email get a first response within one business day. Fixes ship as soon as I can verify them — often the same week for clear regressions, because the same person who reads the report also writes the patch. There is no handoff between support and engineering.
- Do you offer support?
- Yes — direct email support from the person who built the feature you are asking about. There is no 24/7 phone line and no dedicated account manager. For how-to questions, the docs and FAQ cover most setup steps. For anything else, hello@apitestlab.org goes straight to me.
- Can I trust a tool built by one person with my API testing workflow?
- You should evaluate it like any tool: try the free tier, check the privacy policy and our public security practices on apitestlab.org/security, and see if the workflow fits. The tradeoff is real — no enterprise SLA room full of staff — but the upside is also real: fast fixes, honest answers, and no roadmap theater. Many solo developers and small teams use API Test Lab for day-to-day REST testing and load checks; enterprise teams with strict compliance needs should compare options on our compare page.
- How do you handle API keys and credentials?
- Credentials entered in the tester are transmitted over HTTPS to our proxy service and isolated strictly by account. We never log full credentials, never send raw secret headers to external AI providers, and strip auth configs and secret header values before public collection sharing. For an honest, verified technical breakdown of our storage and session controls, read our full security practices on apitestlab.org/security.
- How is this different from Postman or other competitors?
- Postman is the industry standard for collections and team workflows; k6 and Grafana excel at script-based load testing at scale. API Test Lab targets developers who want browser-based REST testing, no-code load tests, and monitoring in one place without a desktop install or JavaScript test scripts. Free tier is permanent, Pro is $5/month flat. See the full comparison on apitestlab.org/compare for an honest feature-by-feature breakdown.
Why I built it
Postman and similar tools kept raising prices while load testing still meant switching to another product. I wanted one browser-based workspace where you can send REST requests, stress-test endpoints, and review results without enterprise bloat or a fake "team" page. That motivation has not changed since the first prototype in January 2026.
What this means for you
When you email support, I read it. When you find a bug, I fix it. There is no support ticket queue and no account manager. Just a developer who built this and wants it to work well — the same person described on this page and on /about.
Contact
Explore the product features, read the full story, compare tools on the compare page, or get in touch.