Why we built euraika-labs.net

The lab existed before the site did. Aegis was running in customer namespaces, Hermes was routing model traffic, Pan was on its way to fifty stars, ai-slopcheck was sitting in a few teams' CI pipelines. What was missing was a single place to point someone at when they asked who builds this?.

We wanted that place to do one thing: convince a technically literate visitor — within the first thirty seconds — that the team behind the products does real, deep AI work. Not by claiming so. By showing the artifacts.

Three rules guided the build.

Substance over signal. Every page links to or contains a real artifact: code, prose, data, demo. Decoration earns its place by serving the substance. There are no bento grids on this site, no testimonials, no logo walls. There is a manifesto, a list of recent writing, and a grid of repositories.

Sovereign in form, not just word. The site demonstrates the positioning by being sovereign. Fonts are served same-origin. Analytics is self-hosted Matomo, honouring Do Not Track. Errors flow to a Sentry instance on our own metal. The cluster is on-prem in EU jurisdiction, managed via ArgoCD from a GitLab repository on our own GitLab. The only script that runs in the reader's browser is our own.

Slow, durable, fast. Crafted to last — no design tropes that date in six months — and to load instantly. The home page ships under fifty kilobytes of JavaScript. Pages with prose ship only code we host ourselves.

You're reading the first post.