About DevForge

DevForge is a collection of free developer and AI tools built on one principle: the tool should be faster to use than to log into.

Why this exists

Every developer has the same experience at least once a week. You need to decode a JWT, check what a cron expression actually means, count the tokens in a prompt before you commit to an architecture, or work out why a JSON payload is rejected. The task takes thirty seconds. Finding a tool that does not require an account, does not cap you after three uses, and does not quietly upload your production data to a server you have never heard of takes longer than the task.

DevForge is the answer to that. Ten tools, no accounts, no usage limits, no upload step. Every tool runs entirely in your browser.

What "runs in your browser" means concretely

It is a real architectural constraint, not a marketing line. There is no backend API for any tool on this site. When you paste a JWT, a JSON payload, or a prompt containing your proprietary business logic into a DevForge tool, that text is processed by JavaScript executing in your own browser tab and is never transmitted anywhere.

You can verify this yourself in about thirty seconds:

1. Open your browser's developer tools and go to the Network tab.
2. Load any tool page and clear the log.
3. Paste text into the tool and use it.
4. Observe that no request containing your input is made.

Or take it further: load a tool page, then disconnect from the internet entirely. Every tool continues to work. That is only possible if nothing depends on a server.

This matters because the inputs to these tools are frequently sensitive. JWTs contain authentication claims. JSON payloads contain production data. Prompts contain the business logic you are about to ship. Handing those to a third-party web service is a real risk that most people take without thinking about it.

How the site is funded

DevForge is free and has no paid tier. It is funded by advertising, which is why you will see ads on these pages. Being straightforward about that is part of the deal: the tools stay free, and in exchange the pages carry ads.

Advertising is limited to display ads. There is no affiliate link manipulation, no sponsored placement inside tool output, and no arrangement where an advertiser can influence what a tool tells you. Where a tool produces guidance — for example, the security warnings on the JWT decoder — that guidance comes from the tool's own logic and is not influenced by anything commercial.

See our Privacy Policy for exactly what data third-party advertising collects and how to opt out.

Accuracy and corrections

Technical documentation decays, and pricing information decays faster than almost anything else. Where a page states a fact that can go stale — model pricing, tool behaviour, specification details — we date it and say so.

Specific commitments:

• Pricing data is dated and flagged. LLM API prices change frequently. Where they appear, they carry the date they were checked and a pointer to the provider's official page. Verify there before making decisions.
• Estimates are labelled as estimates. The token counter says plainly that it approximates, and tells you how to get an exact count. It does not pretend to be authoritative.
• Security guidance is conservative. Where the JWT decoder warns about something, it errs toward caution, because the cost of a false warning is reading a paragraph and the cost of a false negative is an incident.

If you find an error — a wrong price, an incorrect claim, a tool that mishandles your input — please tell us. Corrections are made quickly and we would rather hear about it than have it stay wrong.

Limitations worth knowing

These are real and worth stating rather than hiding:

• Token counts are estimates. Within roughly 10% on ordinary English prose, less reliable on code and non-Latin scripts. Use the provider's own counter for billing.
• The YAML parser handles the common structural subset. Anchors, aliases and multi-document files are not fully supported.
• The SQL formatter tokenises rather than fully parses. Deeply nested CTEs and vendor-specific syntax may indent unexpectedly. Always read the output.
• The JWT decoder does not verify signatures. Doing so would require your secret, which should never be pasted into any website.

Who builds this

DevForge is built and maintained by working software engineers. The tools come from problems we hit ourselves — a cron expression that fired on the wrong days, a JWT that expired earlier than expected, a token estimate that was off by a factor of two in a budget review.

Get in touch

Bug reports, correction requests, and feature suggestions are all welcome — see the contact page. The most useful report is a concrete one: the input you used, what you expected, and what you got.