
Doberman
Guard dog for your AI when it goes rogue.
Launched Doberman on Product Hunt this week. It's an open-source runtime authorization layer for AI coding agents, sits between the agent and its tools and checks every shell command, file write, or MCP call before it executes. v0.18.5 shipped two days before launch. Current numbers: 198 GitHub stars, 28 forks, alpha software with about 2,000 tests in CI.
The mistake right after the launch is worth writing up. I posted the same link to seven subreddits within about a day, same domain each time, near-identical text on two of them. Reddit's own sitewide spam filter removed every single one, not the subreddit mods. New account, high link-post velocity, same domain repeated, that's a textbook spam signature, and I walked into it thinking I was just "sharing something I built in the obviously relevant places."
Lesson: an account needs to look like a person before it can look like a maker. Verified email, some karma, some link-free comment history, then post once, in one place, and let it breathe before the next one. Going to do the slow grind of building up an new account for a couple of months before even thinking about pushing Doberman on it.
Happy to answer questions about the launch, the tool, or exactly how I torched a week of Reddit karma in under a day.
I think agent security is going to be a boring, unavoidable line item the way backups became one, and I wanted the open-source default to exist before the enterprise vendors define the category. Doberman sits between a coding agent and its tools, every tool call gets allow/authenticate/block from a local policy engine before it runs. Apache-2.0, local-first, pip install doberman-core.
The open-core bet: the runtime, policy engine, and adapters are free forever, and the paid layer later is compliance evidence and team controls. 19 contributors have merged PRs since it went public.
Live on Product Hunt today: https://www.producthunt.com/products/doberman
5 Likes
3 Comments
3 Comments
-
1
Solid positioning. Agent security and tool-call authorization are definitely heading toward that "boring, unavoidable line item" status as autonomous agents get more execution privileges.
Love the local-first approach with the policy engine sitting right in front of tool execution.
Just checked out the PH page and dropped an upvote/comment. Releasing open-source core with 19 PRs already merged is a serious validation signal. Congrats on shipping today!
PS: If you get a quick breather between PH notifications today, I’d love your eyes and technical feedback on LocalPatron over on the Build Board: https://www.indiehackers.com/product/localpatron?post=BZHMchLNDI4lxlFrw6xz
-
1Not to toot my own horn but there;s actually been over 170 PR's merged across 19 contributors in the last month. Checking out LocalPatron now!
-
1
170+ PRs across 19 contributors in a single month is massive! That's serious open-source velocity right there.
Appreciate you taking a look at LocalPatron amidst the launch chaos today!
-
-
About
AI guardrails only protect against 89% of dangerous commands. This may seem pretty good until you think of it as a lock that lets 1 in 9 intruders in.


1 Comment