A home for small, quiet tools.
Seventeen of them so far. sixteen run in your browser and keep nothing; CapyExpense lives on your desktop and keeps your files on your disk instead.
No account, no cookie banner, no onboarding tour.
Every byte is processed in your browser.
The suite forgets you the moment the tab closes.
Download the file. Desktop tools keep it on your disk.
Open an issue — quietly.
Capytools is open source (Apache-2.0). If something breaks, the fastest fix is an issue with the tool name and what you expected: github.com/unfoldingdimensions/Capytools/issues. The repo lives at github.com/unfoldingdimensions/Capytools.
Utkarsh Benjwal.
Analyst by day. Builder by night. A business analyst who builds open-source tools on the side. Capytools is the set of small utilities that were hard to find without an upload, an account or a cookie banner — every one of them built and maintained by one person.
Built as a Next.js app, deployed on Cloudflare Workers, Apache-2.0-licensed, version 0.1.0. Set in Fraunces, Plus Jakarta Sans and Albert Sans. The editorial collage plates were generated from the design notes.
Nothing you type, drop or upload into a tool leaves the tab.
The three GitHub-backed API routes are rate limited to 10 requests every ten seconds per visitor. That is enforced by a Cloudflare rule at the edge, before any of this code runs — the in-app limiter in src/proxy.ts keeps its counts in memory, and on Workers that memory is per isolate, so it damps bursts rather than enforcing a limit. Run this anywhere else and you will want your platform’s own equivalent; do not rely on the code alone.
What actually protects the upstream quota is caching: repeat requests for the same profile are answered from the edge without the server calling GitHub at all. Set GITHUB_TOKEN as well, or the card routes run on GitHub’s 60-an-hour anonymous quota.