Contact
Direct line to the maintainer.
For integration help, regulation-specific profile authoring, audit walkthrough prep, or anything Regulus-shaped you want another set of eyes on.
me@dipankar.name
Best for everything substantive. Three questions I'll ask in the first reply: which regulation set you're under, which GRC system the evidence has to land in, and what your current audit log story looks like end-to-end.
GitHub Discussions
github.com/neul-labs/regulus/discussions
Best for technical questions other users will benefit from seeing. Integration patterns, plugin authoring, profile composition gotchas. Answered publicly so the next team doesn't ask twice.
LinkedIn DMs
linkedin.com/in/dipankarsarkar
Best for fast back-and-forth or qualified-buyer intros. DMs open. Just say which post brought you in so I know which conversation we're continuing.
GitHub Issues
github.com/neul-labs/regulus/issues
Best for reproducible bugs, security issues (use the
security label), and feature requests. Issues are
triaged within 48 hours; security issues within 24.
What I'm working on right now
Inbound DM and email volume is real but answerable. If you're a qualified buyer — running ADK in production in regulated EU/UK financial services, healthcare, or public sector — flag that in your first message and I'll move you to the front of the queue. Enterprise support arrangements are by direct engagement; the framework itself stays MIT-licensed regardless of whether you sign anything.
What I won't do
Reply to generic outreach about sponsored content, paid speaking slots, or AI tooling sales. The inbox is reserved for engineering and compliance discussions. Apologies in advance for not engaging with the rest.