About us

A small studio that likes small software

Viridian Creations builds modular apps, small utilities and game engines. We’re a small team, we keep our dependency list short, and we’d rather ship something focused that works than something sprawling that almost does.

Most of what we make is free and runs entirely in your browser. The rest is client work, built the same way.

Fog settling over the tops of a spruce forest

Fast, small, and still here in five years

That's the goal for everything we make. Here's what it means in practice.

How we got here

Viridian Creations started as a few utilities we built for ourselves: a password generator that showed real entropy, a QR generator that didn't send your data anywhere, and a timer that kept time in a background tab. Enough people found them useful that they became the product.

Our client work grew out of the same habits: build it properly, write down why it was built that way, and leave it in a state someone else can pick up.

Moss-covered trees on a leaf-strewn forest floor at dusk

What we hold to

Three things we won’t give up, even when it would be faster.

  • Small on purpose

    Every dependency is one more thing that can break, get abandoned or ship a security hole. We only add one when we really need it, and we pin it to an exact version.

  • Yours, not ours

    The tools process your files in your browser. There's no upload server, no account and no tracking of what you put in. That isn't a policy we could quietly change. The code to do it simply isn't there.

  • Built to be maintained

    Code gets read far more often than it gets written. We pick the plain, readable approach over the clever one, and we write down why we made each decision while we still remember.

How we work

The same three steps, in this order, on every project.

  1. 01

    Understand the real problem

    What you're asked for and what you actually need aren't always the same. We start every project by working out which one we've been given.

  2. 02

    Build a small, real first version

    Something running beats something on paper. The first version is narrow on purpose, but it's real code, not a prototype we plan to throw away.

  3. 03

    Harden it, then hand it over

    Tests, types and documentation are part of the job, not an afterthought. What we hand over is something the next person can pick up without needing us.

Working on something?

If you have a project that needs building properly, or a tool you keep wishing existed, tell us about it. We read every message and reply to the ones we can take on.

Get in touch