Devlog · Phase 0
Aubia, born in 2026 out of a developer's frustration, is an AI agent orchestrator that has the agents review each other's work. I have been designing it since April 2026, and this blog recounts my decisions, series after series: the build and its stack, with the taste for work done right that has driven me since 2009.
Devlog · Phase 0 · 7/7 10 min read
Each of aubia.dev's six languages has its own URLs and hreflang links. The served HTML also describes every article and its author in JSON-LD, without waiting for JavaScript.
Devlog · Phase 0 · 6/7 9 min read
Verre replaces aubia.dev's former design and will also serve aubia.cloud and the desktop application: two themes in neutral grays, gray glass, Geist and components drawn from a registry.
Devlog · Phase 0 · 5/7 6 min read
aubia.dev groups backend code by responsibility. Actions, Queries and DTOs help trace a change, but directories alone cannot control dependencies.
Devlog · Phase 0 · 4/7 7 min read
aubia.dev records a signup request before email confirmation. How the form catches typos, limits abuse and handles addresses that remain unconfirmed.
Devlog · Phase 0 · 3/7 7 min read
Signups are stored by aubia.cloud. The public site keeps sessions and a Redis cache, with signed requests and a form that depends on the network.
Devlog · Phase 0 · 2/7 10 min read
I built aubia.dev on a single Laravel application, with no database. Octane and FrankenPHP keep it in memory between requests, and React renders its pages on the server with Inertia.
Devlog · Phase 0 · 1/7 3 min read
I ask for an email address before launching Aubia. The signup goes through a single write route, to a separate domain, and is measured without cookies.
