ST / 01 Engineering practice

A workshop for durable software.

Systems that remain
under your control.

Websites, publishing infrastructure and small tools built to be understood, owned and maintained.

Examine the work Discuss a project
01Publishing systemsSource, build and release paths
02Independent websitesFast, quiet and portable
03Small softwareUseful tools with clear boundaries

suteo is the engineering name of Nox, a house in which one author writes under several names. The house’s websites, its publishing pipelines and the feeds that join them together are built here.

Outside the house, suteo makes tools of his own: kits for running AI agents on modest infrastructure, a self-hosted word game, and the occasional essay on what building these things asks of the builder.

Working principles

  1. Own what you can. Plain files, static output, source in git. Nothing rented that does not have to be, and nothing a client or a reader can be locked into.
  2. Nothing watches the reader. No analytics, no tracking pixels, no fonts fetched from someone else’s server. Every site in the house ships that way.
  3. Fail loudly. Check the finish reason, verify the deploy, retry what is merely unconfirmed. Most production problems are silent ones.
  4. Write it down. Every system leaves a note explaining how it works and what went wrong. The essays here are the public half of that habit.

Selected work

All work →

Independent practice

Bring a real constraint.

For enquiries about an independent website, a publishing system or a small self-hosted tool, write with the problem, the people it serves and what must remain under your control. Scope and fit come before any proposal.

Start an enquiry

Recent writing

All writing →