All articles

Why rellit.de: tools for the occasional need

Why I built myself a collection of small developer tools – and why the explanations mattered more to me than the features.

Some tools you do not need daily, but every few weeks. Quickly decoding a Base64 string. Opening up a JWT to see why the login keeps expiring. Working out what 0 3 */2 * * actually means. Producing a hash to verify a file against.

It is precisely that occasional need which is the problem.

A plugin for every little task? Not really.

There are plugins for all of these jobs. For every single one. And a separate variant for every IDE.

Except that for an occasional need, the maths does not work out. I search for a plugin, skim whether it is the right one, install it, thereby allow it to run inside my development environment – and then use it three times a year. At the next major update it is no longer compatible, or the author has abandoned the project. The effort of choosing and maintaining it bears no relation to the use it gets.

On top of that comes a point developers like to overlook: not everyone works in an IDE. The colleague in support who has to trace a token from a ticket. The admin sitting at a console. Someone from testing who wants to check whether two configurations really are identical. The project manager who wants to know what is inside this token everyone keeps talking about. All of these people have a very concrete question – and no development environment to build a plugin into.

A browser, on the other hand, is available everywhere.

Everything in one place

For years my alternative was the search engine. A different site for every task, each with its own way of being operated, and every time the question of whether the site even does what I expect. For half of them it was not apparent whether the input stays in the browser or gets sent somewhere for processing.

That becomes uncomfortable at the latest when you paste a real token, a real hash or an extract from a real configuration into someone else’s form.

I wanted the tools I need in one place. Operated consistently, without signing up – and built so that the input never leaves the machine in the first place. Everything runs in the browser; there is no backend that could receive anything. That is not only a privacy decision, it is also the most honest one: what is never sent anywhere cannot be stored anywhere either.

The part that bothered me most

The real annoyance, though, was a different one.

Most of these tools work, but they explain nothing. You throw something in, get a result out, copy it away. What happened in between stays in the dark – even though that knowledge is exactly what would make the actual work easier.

A bcrypt generator hands you something like this:

$2b$12$LQv3c1yqBWVHxkd0LHAkCOYz6TtxMQJqhN8/LewdBPj/rCWDfe1Nu

Done. Copy, paste, move on. And yet everything that matters is in that string: 2b is the variant of the algorithm. 12 is the cost factor – the exponent that determines how much computational work a single hashing operation costs. Every increase by one doubles that effort. After that come the salt and the hash proper, joined into one string. Which is why the salt need not be stored separately anywhere – it is part of the hash.

Anyone who has seen that once asks the right question the next time round. Not “how do I produce a hash”, but “which cost factor suits our hardware and the response time our login can afford”.

It is the same with JWTs. Almost every decoder shows you the contents. Considerably fewer mention that the middle part is merely Base64-encoded and therefore readable by anyone who gets hold of the token. That is not a nicety, it is the central property – and the reason secrets have no place in a JWT. And the abbreviations exp, iat and nbf would not be arcane knowledge either if someone wrote down what they stand for.

That is why, in my tools, the explanation sits beside the result as an equal. Not as a collapsible footnote, but as part of the output: what each component means, why the result looks the way it does, what to watch out for.

The side effect is the part I like best: you can send someone a link instead of having to explain it yourself.

What came of it

The idea turned into rellit.de – a collection of exactly those tools I kept searching for myself. Converters and formatters, hashes and encodings, password hashing, JWT, cron, regular expressions, timestamps, text comparison, colours.

Each tool is a self-contained, statically served page on its own subdomain. No framework ballast, no sign-up, no backend. And next to every result the explanation I would have liked to have myself, back when I first looked at a hash like that.

In the next few posts I will take individual ones apart in more detail – starting with the question of why bcrypt and Argon2 work fundamentally differently from the hash functions you know from your studies.