Compare

Why this and not that.

Every fact about another project on these pages is single-sourced to docs/strategy/COMPETITOR_MAP.md and carries that file's research date. Nothing from another project was installed, configured or run. Where a comparison would need a fact the map does not carry, the sentence is dropped rather than softened — and every page opens by naming where the alternative wins.

Should you build a CRM from scratch, or start from a framework?

Building a CRM yourself

The comparison with no competitor in it: your own empty repository against this framework.
Twenty, or a CRM your coding agent writes as code you own?

Twenty, the open-source CRM platform

Twenty is an open-source CRM platform with an apps SDK; Accordo is a framework that generates CRM source into your repository.
Odoo's CRM app, or one custom process as code you own?

Odoo, the open-core business suite

Odoo's CRM is one app inside a business suite that a company buys and runs; this is a framework that generates one commercial process as code.
Is this a customer data platform? Bounded customer foundation, not a full CDP

Not a customer data platform

Accordo is a CRM framework with bounded customer imports, deterministic matching, logical canonical identity and a consolidated profile.
Frappe CRM, or customization as reviewable code instead of metadata in a running database?

Frappe CRM, the metadata-driven CRM app

Frappe CRM is a working end-user CRM app on the Frappe low-code framework, with the most mature metadata-driven customization model in the researched set and a managed cloud behind it;…
Relaticle, or a coding agent that writes the CRM rather than operating it?

Relaticle, the agent-operated open-source CRM

Relaticle describes itself as an open-source CRM with native AI agent support, and the research this page reads credits it with the most agent-forward claim among the incumbents: a…
Comp AI's agentic CRM, or an approval boundary the agent cannot cross?

Comp AI CRM, the agentic-first CRM

Comp AI's CRM is the loudest version of a thesis this project deliberately inverts: an autonomous background agent doing CRM work inside the product, with a work queue, evidence-based…
EspoCRM or SuiteCRM, or one custom commercial process as code you own?

EspoCRM and SuiteCRM, the legacy PHP self-host CRMs

EspoCRM and SuiteCRM are working self-host CRMs that a small or midsize business installs and uses; this is a framework a developer generates one commercial process from.
Atomic CRM and the Supabase starters, or a starting point with CRM machinery already in it?

Atomic CRM, Refine app-crm and the Supabase starters

Atomic CRM, Refine's app-crm and the Supabase starters are the closest neighbours this framework has: MIT-licensed code you copy into your repository and own outright.

What none of the 9 pages above means

These pages describe this repository at this commit. None of them implies the framework is deployable, and none of them is a roadmap: nothing that is not merged appears on this site, in any tense.

No authentication ships: the framework authenticates nobody. Production Spine v1 (ADR-038) gives the framework verified identity, organizations and memberships, server-authoritative authorization and one tenant per application instance — so tenancy and authorization now exist and are enforced. What does not exist is authentication: no login, password, session or OIDC implementation ships, and a deployment must supply the adapter that verifies the request. Production mode refuses to start without one. In local-development mode an actor header is accepted as an assertion and is not an identity, which is the default developer posture. This is not shared-database multi-tenancy and it is not a readiness claim.
Not shared-database tenancy. createAccordoAppAsync can boot one tenant onto dedicated PostgreSQL databases. Shared-database row-level tenancy is not implemented, and this is not a production-readiness claim.
Timers exist; a service that runs them for you does not. Durable jobs, a transactional outbox and scheduled asks exist for self-hosted applications that explicitly start a worker. Nothing autostarts; a timer opens an ask, never makes a decision, and no managed worker service or recurrence is included.
No email, calendar or marketing integrations. An in-memory notification provider contract exists. MK1 marketing records supplied funnel observations and human-reviewed proposals only; it has no sending, publishing or spending path.
The build benchmark has not been run. The protocol is designed and published; no Successful Agent Build Rate exists yet. Any number you see quoted for this project is not ours.
Ownership means vendored source: there is no framework dependency to bump. The published create-accordo@0.1.0 scaffolds vendored source; it is the August 19 snapshot, not the current repository feature set. Use a current source checkout for the capabilities described here; upgrades require merging source (L-08). The framework is copied into the project, not installed as a framework library dependency. The accordo npm name is an empty reservation; the @accordo scope is claimed and deliberately empty.

Every claim and every limitation is on one page, and the questions this project refuses to answer are published beside them.