thinglaunch
Small tools. One job each.
Servers declared in a file, one seam in front of every outside service, and the chores on the workbench. Every thing Rytter builds lives here.
21 things · 5 in use · 6 being built · 8 planned
The things
One stack, in layers.
The machine runs everything, the seams keep vendors out of projects, and the workbench is where it all gets built.
The machine
The ground everything runs on: machines declared in files and rebuilt the same way every time.
-
hostingthing
In use
The host serving this page: a site is a folder of finished files, served from disk with no build step and no dashboard.
hostingthing.com
-
iacthing
In use
The cluster as code: every host, service and setting in one repository, and one command that makes each box match it.
iacthing.com
-
providerthing
Being built
The services the machines rent, declared: mail, access policies and spending limits as files, with a plan before every change instead of a click in a console.
providerthing.com
-
vpsthing
Planned
The same idea for a single box: the parts of iacthing that fit on one machine, from one flake and one command.
vpsthing.com
-
nixthing
Being built
Turns a fresh machine into a declared one, with flakes on and the config moved into a flake, in about ten minutes.
nixthing.com
-
secretsthing
In use
Every credential in one encrypted file, opened by one key you keep yourself, and handed to each program when it runs.
secretsthing.com
The seams
One place in front of each outside service, so no project ever learns a vendor's shape.
-
dnsthing
In use
Every zone a file in git, applied through one API: a reviewed plan, an apply bound to it, and a check that the live records match.
dnsthing.com
-
gatething
Planned
One bucket behind a gate: a key per application, the access rules in one place, and endpoints that sanitise what they are handed.
gatething.com
-
notifything
Planned
One call for every message a project sends, so the credentials and the boring failures are handled once instead of per project.
notifything.com
-
outboxthing
Being built
The email channel under notifything: one service in front of the mail provider, a key per app, and each key pinned to the one domain it may send from.
outboxthing.com
-
billingthing
Planned
One merchant account and one entitlement check, shared by everything that takes money.
billingthing.com
The workbench
The tools on the desk: the chores every repository and every project repeats.
-
dxthing
Being built
The developer chores behind one verb each: repo rules, secrets made human, and dev databases provisioned or reset.
dxthing.com
-
repothing
Being built
The git and GitHub steps that repeat: sync a branch, open its pull request, land it, sweep what is merged.
repothing.com
-
stubthing
Being built
Notes about the work, out of the repos: each with a kind, a reason and an end date, and agents writing through tools that refuse anything else.
stubthing.com
-
faviconthing
In use
Production-grade favicons from the first letter of a domain: every size a browser asks for, standard every time, in one command.
faviconthing.com
-
llmthing
Planned
The small agent orchestrator: roles with one prompt each, delegation, and a reviewer that can say no. Nothing more.
llmthing.com
-
scrubthing
Planned
A value leaked: every key that holds it, copies and hashes included, sorted into a rotation plan without a value ever printed.
scrubthing.com
-
mopthing
Planned
The code-quality analysers run across every project, read as one format, and handed back to the agent that wrote the code.
mopthing.com
-
applything
Planned
Job listings in, tailored LaTeX CVs out. The agent finds the match, and applything makes it a document a human can open.
applything.com
Experiments
School projects and side quests, kept up because they taught something.
The rules
Small on purpose.
-
One job each
A thing does one job with one verb. When it grows a second job, it becomes two things.
-
Written down, not clicked
Every thing is configured from a file in git, so there is no dashboard to remember settings.
-
Honest about state
Every page says what exists and what does not yet, and so do the labels on this one.
Who built it
Built by Rytter.
I'm Jakob Rytter. thinglaunch is the name every thing I build sits under, held open for the day one becomes a product.