Taking on work for 2026

Software you can stop worrying about.

I build the app, the API, the deploys and the boring operational bits around them. The goal is simple: fewer surprises after launch, and fewer mysteries when something breaks.

Get in touch →

prod · us-east

$atropos deploy --prod
✓build passed · 0 warnings
✓migrations applied · 12ms
✓health checks green
→uptime 412 days, still boring
>

How I work

First we get honest about the job.

Scope

We decide what needs building, what can wait, and what should be quietly killed before it becomes a line item.

Build

You see working software early. I keep the surface area small enough that changes still feel cheap.

Maintain

Launch is not a disappearing act. I keep it healthy, fix the weird bits, and hand it over cleanly when that makes sense.

What I build

Whole product, not a loose slice.

Web apps

Interfaces that do the job, backed by APIs and data flows that are not held together with optimism.

APIs & backends

Schemas, queues, integrations and admin paths that make sense when you come back to them six months later.

Infrastructure

Deploys, monitoring and alerts you trust. Enough platform to sleep at night; not a new control plane for a contact form.

Before you ask.

Is it really just you?

Yes. When a project genuinely needs more hands, I bring in people I would trust with my own production systems. You still deal with one person.

What if you get hit by a bus?

Morbid, fair. Work lives in repos, tickets and docs, not in a private maze in my head. You should be able to replace me without starting again.

Will you work with our existing team?

Happily. I can lead a build, pair with your engineers, or take the awkward chunk everyone has been avoiding.

Can you make it AI-powered?

If it earns its keep, yes. If it is only there so the homepage can say 'AI-powered', I will try to talk you out of it.

Got something to build?

Tell me what you are working on. If I am not the right fit, I will say so.

Get in touch →