Relaticle, or a coding agent that writes the CRM rather than operating it?

Where Relaticle wins

On the axis it chose, it is ahead of everything else in the researched set — including this project's own runtime story. The research file — docs/strategy/COMPETITOR_MAP.md, dated August 4, 2026 — records a first-party MCP server with 30 tools, calls it the most agent-forward incumbent claim, and names Relaticle the first mover on agent-native CRM language. It is a working application on a modern PHP stack — Laravel, Filament, PHP 8.4, Postgres — that a developer-led team or an AI-forward SMB can self-host and point an agent at today. The MCP server here, by contrast, is stdio and local only, with no hosted or authenticated endpoint (C-18), and there is no product around it to operate: no hosted CRM, no free tier, no account (L-07).

Runtime flexibility without a deploy. The file records 22 custom field types and no-migration schema changes — a record can be reshaped inside the running app without touching a repository. And the baseline asymmetry holds here as everywhere on this site: Relaticle is a CRM you can use, while this framework has no authentication, tenancy or RBAC (L-01), stores everything in local SQLite (L-02), and installs nothing from npm — the bootstrap runs from a checkout, so ownership means copying source and upgrading means merging (L-08).

Where this is different

One sentence in the research file carries the whole comparison: agents can operate the CRM via MCP but cannot reshape it — the customization is runtime configuration inside a fixed app. Here, reshaping is the point. A module manifest becomes a migration, a service, a REST resource, an SDK method and Admin screens with no page code (C-01); a customer-authored domain package attaches and detaches with the kernel's fingerprint unchanged, reaching other packages only through declared capabilities (C-13); and one command reads checked-in source and reports what the application actually is as deterministic JSON (C-14). The agent's output is a diff a human reviews, not a sequence of tool calls against a schema someone else fixed.

The two projects also disagree about what an agent should be free to do at runtime. Thirty tools operating a live CRM is a large writable surface. The surface here is deliberately narrow and refusal-shaped: anything that generates code or destroys state is dry-run unless an explicit apply flag is passed (C-18), and the boundary that matters commercially is asserted by a test — an agent cannot approve on the human's behalf (C-04). Nothing in the research file proves either posture superior; they are different bets about where an agent's mistakes are cheapest to catch.

The file's category note is the reason this page exists at all: Relaticle defines the adjacent category — AI agents working in a CRM — that this project must not be confused with. A reader who wants agents operating a CRM should take Relaticle's category. A reader who wants an agent to build the CRM, as reviewable code with approvals, audit and trace as primitives, is in this one.

How to choose

Choose Relaticle if you want a working CRM now, operated by agents through a first-party MCP surface; if a modern PHP stack fits your team; if self-hosting is acceptable — the file records self-host as the only deployment; and if AGPL fits what you are shipping. The file also records solo-maintainer risk at 1.5k stars and 167 forks: weigh that as you would for any dependency this central, and check the current state yourself, because those figures are a snapshot from one date.

Choose this framework in the narrow case: the deliverable is a bespoke commercial process that must exist as source in your repository, written mostly by a coding agent and reviewed as a diff, with the approval boundary asserted by a test — and you supply authentication, hosting, PostgreSQL, import and export yourself, because none of them is here (L-01, L-02).

If your requirement is a hosted, authenticated agent endpoint, neither column is the answer today: the file records Relaticle as self-host only, and the MCP server here is stdio and local, with no identity behind any call (L-01).

What this comparison does not cover

No hands-on evaluation. Nothing from Relaticle was installed, configured, benchmarked or run in producing this page. Every fact traces to docs/strategy/COMPETITOR_MAP.md, researched on August 4, 2026, and this environment has no network access to re-verify any of it.

No tool-by-tool review. The file records that the MCP server has 30 tools and records nothing about what the individual tools do, so nothing about them is described or evaluated here.

No feature matrix and no pricing. The file carries neither for Relaticle, so this page carries neither.

Licence descriptions are factual summaries of published texts, not legal advice.

No build-rate or speed comparison in either direction — the benchmark has not been run, and any number quoted for this project is not ours (L-03). When the competitor research is refreshed, this entry must be re-read against it.