Tell us what you are running on

Most of these start in one of a few places: you want a validated stack of your own, you want it inside your own walls rather than ours, or you need to prove exactly what is running and that it belongs to you. Tell us what you have now and what it has to do.

Where are you starting?

Name

Phone

Message

Please include enough detail for a useful reply.

Software held to the standards of science

A result nobody can reproduce is not a result. We build the same way — and the whole platform is now open source, so you do not have to take that on trust.

Read the source

Apache-2.0. No account, no licence request, no contact form.

What we work on

Three things

01 · Speed

A screen that changes while you are looking at it

Say what you want to see, in plain language, and the interface changes in front of you . No ticket, no spec, no waiting for a release.

The second question could not have been asked before the first answer appeared. Seeing an answer is what makes the next question sharper.

02 · The foundation

Compiled from source, from the kernel up

The compiler and C library are pinned first, then every layer above is built against that floor. Nothing in the stack depends on what the host happened to ship . One signed tree, either architecture.

Reproducibility is not a promise you make, it is a number you check. The thing you validated is the thing that runs - on our hardware or on yours. Every layer is published as source, so the check is yours to run.

03 · Your own agent

The thing writing the code runs where the code lives

An in-house equivalent of the assistant, working on your own software, on your own machines. The first pillar is only worth having if your source never leaves the building to get it.

Every agentic tool asks the same thing of you: send us your code. This one does not. The loop closes inside your own boundary, so speed stops being something you buy with your source - and the model behind it stays a part you can swap.

Rigour makes a result worth trusting; iteration is how you get one worth having.

Immutable by design

Built from parts that don't drift

Every layer is pinned, versioned and rebuildable from source. The same inputs produce the same system - here, or on your own hardware.

Versioned

Every change is a commit

Nothing is edited in place. Every state of the system is a point in history you can rebuild from exactly.

Continuous

Deploys are rolling

Build, migrate, drain, rotate. The new version is up before the old one stands down, so live sessions carry straight through.

Self-contained

Every domain is its own module

One module per host, each with its own boundary. Sites share no mutable state, so every one is built - and rebuilt - on its own terms.

Where the work happens

No handoff, no fixed desk

Describe it, watch it change, keep going. No ticket, no estimate, and no assumption about what you are sitting in front of.

This page has been built from a headset with no keyboard, and from a shell over ssh, in the same week. The surface is not part of the system - the change lands in front of the person who asked for it, in the same conversation, and their reaction is the next change.

Every one of them is the same running Shiny application — one app, one deploy, one thing to secure . Each site is a module inside it, with its own boundary.

Get started

Open the console

Get started Read the source