Blog
Engineering Blog. How we build an open-source CRM.
Deep dives into self-hosting, MCP, custom attributes and the code behind Relaticle.
-
Engineering
Designing an MCP tool suite for a CRM: four lessons
What building Relaticle’s MCP server taught us about schemas, shared custom-field validation, authorization, and client discovery.
-
Guides
Migrating from HubSpot or Attio to a Self-Hosted CRM
Plan a HubSpot or Attio migration: export records and notes, map relationships, test imports, and identify the history and files needing separate work.
-
Guides
Let Claude Code Run Your Sales Pipeline
Five real Claude Code sessions against Relaticle's MCP server: pipeline review, data entry, task cleanup, custom fields, and a delete it wouldn't rush.
-
Guides
What 'Agent-Native CRM' Actually Means
Evaluate an agent-native CRM through its write surface, approval model, self-hosted support, machine-readable documentation, and first-party tooling.
-
Guides
How to Connect Claude to Your CRM with MCP
Connect Claude to Relaticle through OAuth or a scoped token. Understand custom fields, tool discovery, and the direct-write behavior before editing records.
-
Comparisons
Open-Source Attio Alternatives, Ranked by Use Case
Compare Relaticle, Twenty, EspoCRM, and Frappe CRM by workflow, deployment, pricing, and migration requirements before leaving Attio.
-
Comparisons
Relaticle vs Twenty: An Honest Comparison
Compare Relaticle and Twenty on self-hosting, AI approvals, MCP, pricing, and extensibility. Both support self-hosted MCP; their product models differ.
-
Guides
Self-Hosting an AI-Native CRM in 2026
Self-host Relaticle with Docker, Coolify, or Dokploy. Understand the additional model and broadcasting setup needed for chat, plus MCP and credit limits.