SamToolkit — developer tools that run entirely in the browser

The privacy architecture

The thing that makes SamToolkit different from most free developer-tool sites isn't the list of utilities — it's where the processing happens. SamToolkit is built entirely on Blazor WebAssembly, which means the tools run as compiled .NET code inside the user's own browser tab. There is no API call carrying your JWT, your regex, your timestamp, or your JSON payload to a server for processing. The data you paste in is decoded, converted, or validated locally, on your machine, and never transmitted anywhere.

That's a meaningfully different guarantee than "we don't log what you paste in," which is the most that most free tool sites can honestly claim. A server-side tool that doesn't log is still a server-side tool: the data crosses the network and touches a process you don't control, even briefly. SamToolkit removes that step entirely. If you disconnect from the internet after the page loads, every tool keeps working, because nothing about running them ever depended on a round trip to GreenFrog's servers.

This is also why SamToolkit doesn't have accounts, logins, or saved history tied to your identity. There's nothing to log in to, because there's no server-side state to protect. The tradeoff is that nothing persists between visits unless the browser itself remembers it — a deliberate choice, not a missing feature.

What's in it

SamToolkit currently ships 29 utilities across 7 categories — converters, debuggers, generators, and reference tools that come up constantly in day-to-day development. A JWT decoder and verifier, a JSON-to-string converter, a regex tester and explainer, a timestamp and timezone converter, and a colour palette extractor with a contrast checker are among the most used. Each one is a small, focused tool rather than a bundled everything-app, and a filter on the homepage makes it fast to find the one you need.

New tools get added the same way the original set did: someone on the team needed it for a real task and it was quicker to build a proper version than to keep using a half-broken one from a search result. That's also why the categories are practical rather than exhaustive — there's no ambition to cover every possible developer tool, only the ones that earn a place by actually getting used.

Why we built it

SamToolkit started as an internal itch. Building client platforms like BatteryCompany means reaching for the same handful of small utilities constantly — and most of the free versions we found were cluttered with ads, gated behind sign-up, or quietly sending pasted data to a server with no clear retention policy. We built our own, using the same Blazor stack we use for client work, and kept it free because there's no server-side cost model that would justify charging for it: once the WebAssembly bundle is downloaded, every tool run is free to us and private to the user.

It's a small side product next to client work like BatteryCompany, but it's also a genuine demonstration of the stack: a real, actively used application with zero backend at all.