Every tool we publish
We add a tool when it is genuinely useful, not when a roadmap says so. Each one has a free tier, and each works perfectly well on its own.
The catalogue is temporarily unavailable. Everything else on the site still works — try again shortly, or ask us what is available.
Same account, same rules, every tool
Whatever the tool does, the parts around it never change — so the second one you try needs no learning at all.
- A free tier that is usable, not a countdown.
- Full access through the API, not just the dashboard.
- Usage records you can audit and export.
- Cancel one without touching the others.
Published when it is actually useful
Each tool starts as something we needed on a real project. It ships when it does its one job properly — not when a quarter ends.
Built for the job, not the job title
Operations teams, engineers, trainers and support staff all end up in the same tools — because the chore they are avoiding is the same one.
Every tool is also an endpoint
Nothing here is dashboard-only. Whatever you can click, you can call — same auth, same envelope, same error codes across the whole catalogue.
- Script a tool into CI without a bespoke integration.
- Embed it in your own product where customers never see us.
- Rate limits and validation, so automation fails loudly.
The order is set by what you ask for
There is no secret roadmap. The tools people ask about most are the ones that get built next, and the empty slots in the grid above are genuinely open.
Every tool works wherever you do
No regional editions and no country gate. Whatever your addresses, time zones or team locations look like, the catalogue behaves identically.
Missing the tool you actually need?
The empty slots in the grid are real. What people ask for most is what we build next.