A dev hub that turned into a factory

The short history

The first version was a development hub: tooling to make agents useful on real repositories instead of on demos. The tooling kept absorbing the work around it — tickets, branches, standards, gates, deploys, incident handling — until the honest description of it stopped being “tools for developers” and became “a factory that delivers software”.

The turning point was the moment the platform started deploying itself. Once its own releases went through its own pipeline, the question changed from “can agents write this?” to “what should we point it at?” The answer to that question is the product: a business goal, expressed as a metric.

Who builds it

Stigmera is built by a solo founder and the factory. That is not a figure of speech about productivity tooling — the delivery loop does the work, and its throughput is measurable: tickets delivered, cost per delivered ticket, deploys per day.

Best way to reach us is email: [email protected]. It is read by a person.

How it is built

Node and TypeScript services, Postgres for state, containers on Kubernetes, blue-green releases, structured logs and metrics on everything that runs. Nothing exotic — the interesting part is not the stack, it is what drives it. This website is the smallest example: static pages, one small API for the waitlist, specified as tickets and deployed by the same pipeline as everything else.

Elsewhere

Code and releases live on GitHub. The stream channel for the $1M challenge is not open yet — when it is, it will be linked from the challenge page and in the footer. We do not list profiles that do not exist.