02 / 08 · shipped · 2026 · MVP live at reguai.tech
REGU
Started as an EU AI Act compliance engine. Became a local LLM infrastructure service for companies in Munich.
- Role
- Sole engineer across both chapters: ingestion and retrieval pipeline, then the calculation engine, form, report and the marketing site.
- Stack
- Java · Spring Boot · Spring AI · PostgreSQL · pgvector · Next.js · TypeScript · Supabase
- Links
- Live siteGitHub
REGU started as a RAG system that ingested the EU AI Act, effective August 2026, and produced structured, cited compliance reports for founders asking which obligations apply to them. Law, guidance, commentary and examples lived in four vector tables with their own chunking; hybrid search blended semantic and lexical scoring, and a confidence gate failed closed when citations did not meet a threshold. Every claim traced back to a chunk ID.
Conversations with the founders it was built for moved the problem. The question they actually had was about cost and control: what would it take to run their models on their own hardware, and when does that pay off. REGU became that answer: a local LLM infrastructure setup and maintenance service for startups and companies in Munich.
The first product of the second chapter is a one-page analysis report. A company enters its current cloud AI spend and usage profile; the engine picks the most suitable local hardware from a catalogue and shows what they pay today, what they would pay with REGU, break-even, ROI, a three-year TCO and an urgency score. The calculation engine is locked by a golden output shared with a Python prototype, so a formula change is a deliberate, reviewed diff.
Two chapters
01 · Early 2026 · Archived on GitHub
EU AI Act compliance engine
A RAG system over the EU AI Act: four vector tables, hybrid search, law-primary retrieval and a confidence gate that refuses rather than guesses.
Java 21 · Spring Boot 4 · Spring AI · Postgres + pgvector · Voyage embeddings · Claude Sonnet
Regu-EAACC on GitHub02 · Sep 2026 · MVP live
Local LLM infrastructure for Munich
A one-page cloud-versus-local analysis report: hardware pick from a catalogue, OPEX versus CAPEX, break-even, ROI, three-year TCO and an urgency score. Honest by design: when local does not make sense, the report says so.
Next.js · TypeScript · Supabase EU · Vercel · Python prototype
reguai.tech