About
The project, the bet, the maintainer.
Regulus is the open-source EU + UK compliance plane for Google ADK. Built by Neul Labs. First commit 2026-03-20, ten days before ADK Java 1.0 GA.
The bet
Google's Agent Development Kit landed on 2026-03-30. It is the best-designed agent runtime shipping in 2026. By design, ADK is a runtime, not a control plane — Google rightly doesn't try to make the framework the place where Article 9 evidence gets emitted.
Most teams shipping regulated agents on top of ADK are doing one of two things: ignoring it and hoping the GPAI Code of Practice deadline doesn't bite, or hand-rolling a compliance wrapper with PDFs and Notion pages. Both of those answers are wrong. The correct answer is a control plane in the same shape as the rest of GCP — one layer up, plugged into the runtime's own extension seams.
That's what Regulus is. The bet is that the plugin SPI seams
(BasePlugin, SessionService,
MemoryService, ArtifactService,
EventCompactor, ToolConfirmation) are
stable enough that an external compliance plane can ride along
with ADK's releases without forking. The shipped framework has
been compatible across three ADK patches so far.
The maintainer
Dipankar Sarkar — open-source maintainer, formerly of independent regtech and platform engineering work in London ↗. Based in Vienna and London. Background in Java platforms, regulated financial-services systems, and AI agents. The technical work on Regulus is the work; this isn't a side-project to a SaaS pitch.
Direct line to the maintainer: me@dipankar.name. LinkedIn DMs open at www.linkedin.com/in/dipankarsarkar.
The organisation
Neul Labs is the umbrella under which
Regulus and adjacent open-source projects (closegate, bondfoundry)
live. The Maven namespace is com.neullabs. The
container registry is ghcr.io/neul-labs/. The repos
live under github.com/neul-labs ↗.
Editorial standards
Every Regulus compliance documentation page follows a fixed 12-section template (codified as ADR-009: regtech-as-product- docs). The reader is a competent backend engineer or architect who has never touched financial regulation, GDPR Articles, AI Act terminology. Every regulation page teaches the regulation before showing the code — what it is, who it applies to, what it requires of an engineer, what Regulus does, time saved, code minimal, code production, how to verify, what an auditor will ask, what's out of scope, citations.
This site applies the same standard. If a regulation page on regulus.neullabs.com claims something the shipped code doesn't deliver, that's a bug — open an issue and we'll fix the docs or the code.
Licence and governance
Regulus is MIT-licensed. Code lives on GitHub. Issues, PRs, Discussions are public. Release cadence is roughly quarterly with patch releases between (see the CHANGELOG ↗).