Product upvotes vs the next 3

Waiting for data. Loading

Product comments vs the next 3

Waiting for data. Loading

Product upvote speed vs the next 3

Waiting for data. Loading

Product upvotes and comments

Waiting for data. Loading

Product vs the next 3

Loading

Relaticle

Open-source CRM with approval-gated AI writes

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.

Top comment

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?

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.

On the analytics side, Relaticle competes within Open Source, Artificial Intelligence, GitHub and CRM — topics that collectively have 590.4k followers on Product Hunt. The dashboard above tracks how Relaticle performed against the three products that launched closest to it on the same day.

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.

For a complete overview of Relaticle including community comment highlights and product details, visit the product overview.