Most CRMs bolt AI on. Relaticle is built agent-first: any MCP client gets 37 first-party tools over OAuth, with workspace custom fields in each agent's schema automatically. The in-app assistant is stricter: every write is a proposal showing the exact change, approved record by record. Self-host everything under AGPL, including local inference with Ollama. Free forever self-hosted; Cloud is flat per-workspace pricing, not per-seat.
Hi Product Hunt, Manuk here. I've been building Relaticle for about two years, mostly solo.
It started as a conventional open-source CRM. Then I added agents and hit a question I couldn't dodge: how much authority should each kind of client get? Read-only access was too limited to be useful. Silent writes into customer data felt wrong.
I ended up with two trust levels. External MCP clients (Claude, Cursor, anything that speaks MCP) authenticate over OAuth and write directly through 37 tools, the same way an API client would. The in-app assistant works next to human users, so every write it wants becomes a proposal that shows the exact change and waits for approval. Batches are reviewed record by record: you approve or skip each one, and whatever you approved is kept.
The chat client itself was rebuilt after failures I hit in real use. A rate-limited retry could delete a conversation turn. A stale stream handler could write a draft into the wrong conversation. Drafts now survive reloads, failed sends stay visible, and answers link back to the records they mention.
Everything self-hosts under AGPL, including model inference with Ollama. Each workspace defines its own custom fields, and they show up in the agents' schemas automatically.
One question I'm still chewing on and would genuinely like opinions on: should an in-app assistant ever get policy-based auto-approval, or should every write stay explicit?
Approval gated writes is the piece I keep rewriting in my own tooling. Where did you land on the granularity, one approval per write or one per session?
Flat per-workspace pricing on the cloud tier is the right call for a CRM: per-seat is how you get three people sharing one login.
How do you stop the flat price from being a bad deal for a solo founder and a steal for a 30-person team? Usage caps, or you just accept the spread?
I am also looking for open source crm. Love to explore more.
Congratulations the launch btw
@manukminasyan the two trust levels for ai writes is an interesting decision. i can see why silent changes to crm data would make people nervous. curious if you have found users prefer approving every change or if they’re already asking for some writes to be automated?
I like the smaller recovery details here too. Keeping failed sends visibla and drafts intact after a reload sounds minor, until an assistant is working with actual CRM records.
Would love an undo trail for approved writes, not just the approve step. Excited to see where this goes!
On the auto-approval question, I'd be wary of it even with policy rules. The whole pitch here is that the assistant's writes are legible to a human before they land, and policy-based auto-approval is basically a slow reintroduction of silent writes once someone gets tired of clicking approve. If anything I'd want auto-approval scoped to read-adjacent stuff like tagging or dedup, never to fields that touch pipeline value or contact ownership. That said, 37 tools over MCP with OAuth is a lot of surface area for a two-year solo project, curious how much of that is generated vs hand-written.
Really like the approach here! Letting AI do the heavy lifting while keeping users in control of every change feels like the right balance. Have you considered adding customizable approval rules for low-risk updates?
It’s great to see a CRM that isn’t just adding AI on top, but is actually designed around AI from the ground up. And the MCP compatibility is really cool stuff! Good luck =)
This project has a solid based of Laravel that have helped me learn Laravel. I learned so much about how to setup Laravel in a professional - enterprise grade setup which alone is gold. In combination with AI - MCP, it really can turn a basic CRM into a full-fledge internal processing system, ie: an ERP.
Wish alot of success for Manuk for the launch!
Honestly, this is the kind of CRM + AI approach that makes sense to me.
I like that the AI can actually do things instead of just generating text, but you still get to approve what changes before it touches your data.
And making the whole thing open-source + self-hostable is a huge plus. Nice work!!
37 tools over oauth for any mcp client, and the workspace custom fields land in each agent's schema on their own. do they refresh live or only on reconnect?
Can you set rules so certain fields can be automatically written while others always require approval?
About Relaticle on Product Hunt
“Open-source CRM with approval-gated AI writes”
Relaticle launched on Product Hunt on September 8th, 2026 and earned 165 upvotes and 37 comments, placing #6 on the daily leaderboard. Most CRMs bolt AI on. Relaticle is built agent-first: any MCP client gets 37 first-party tools over OAuth, with workspace custom fields in each agent's schema automatically. The in-app assistant is stricter: every write is a proposal showing the exact change, approved record by record. Self-host everything under AGPL, including local inference with Ollama. Free forever self-hosted; Cloud is flat per-workspace pricing, not per-seat.
Relaticle was featured in Open Source (68.8k followers), Artificial Intelligence (478.1k followers), GitHub (41.4k followers) and CRM (2.1k followers) on Product Hunt. Together, these topics include over 166.1k products, making this a competitive space to launch in.
Who hunted Relaticle?
Relaticle was hunted by Manuk Minasyan. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Relaticle stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Manuk Minasyan