Built Here First

Why any of this is here

Different On Purpose

The things built here look unrelated, and that is deliberate. What they share is not a market but a principle: production is automated, and the judgement and the control stay with the people who own the work.

Something stays here, incubating, until a customer could take it on today. Then it launches under its own name.

We test the way we work on ourselves first.

Available

Ready Now

• MullionWorks

  Available

  A British model factory. MullionWorks makes small language models for organisations that need control over how their AI is built. Each model runs on the customer's own infrastructure, learns from their own data, and keeps working with no outside connection.

  The factory is laid out like a car plant. One line, built once, makes every model that leaves it. What makes a model yours is added at the end, in a lane of its own.

  mullionworks.com →

• Jargonautica

  Available

  A public glossary that takes the jargon out of a subject and keeps every definition consistent, published straight from a folder of plain text with no content management system behind it. Open source, and free to use.

  A term used in six different documents by six different authors drifts into six different meanings within a year unless somebody keeps checking it. Jargonautica is that checking, done once in the glossary rather than repeatedly by everyone who reads or writes about the subject afterwards. It started as an internal reference and stayed public because a glossary is only trustworthy while more people can see it and correct it than can quietly change it.

  jargonautica.com →

Incubating

Not Ready Yet

Each of these has a status and a description, and nothing else. We would rather tell you a thing is unfinished than send you to a page that says it is coming soon.

• Wren

  Private beta

  A household anticipation service for working-parent families, built for the mental load problem: the invisible work of noticing what a household needs before anyone has said it out loud. Real users are in it. There is no public front door yet and there deliberately is not one until the beta says there should be.

  Most tools in this space ask a household to keep a list and then remind it of the list, which still leaves someone carrying the list in their head between reminders. Wren is built to notice the pattern behind the list instead, the shape of a week, a term, a subscription renewal, so it can raise the thing that matters before anyone has to remember to look for it. The private beta exists to test whether that noticing holds up against a real household's mess, not a tidy demo one.

• CORTEX

  In development

  A command and control platform for defence. It takes the feeds an operation already produces, holds them as one current picture, and shows its working: every call it makes can be traced back through the data it used and the route it took to get there. That traceability is not a feature, it is the condition for anyone being allowed to act on what it says.

  It is built to run where the work happens, on secure networks and on hardware at the edge as readily as in a data centre.

  It sits in this lab rather than in the consulting pages because it is the same argument at a larger scale. An operations room burns an enormous amount of attention keeping a picture current so that somebody can make a small number of decisions. CORTEX takes out the attention.

• Polperro

  In development

  A system for building small, fast websites from reusable themes. A theme is a fixed set of named settings covering type, colour, spacing, motion and layout, and a site is then built from those settings rather than designed from scratch each time. Two complete themes have been designed and delivered.

  The site you are reading is not built on Polperro. It is feeding it. The components, the tokens and the discipline about what a theme is allowed to change all come back into the system, which is what a lab is for.