Atomic CRM Review: The React-Admin Based Option

Atomic CRM takes a different approach from most open source CRM projects. Rather than building a monolithic PHP application, it's built on React-Admin and Supabase — a modern JavaScript stack that makes it easy to customize, extend, and deploy. Created by the Marmelab team (the creators of React-Admin), it's a reference implementation showing what a React-Admin-based CRM looks like in practice.

The result is interesting: a CRM that feels like 2024 software rather than 2010 software, with a clean UI and real customizability. But it comes with significant limitations that make it more of a starting point than a production-ready CRM for most teams.

What Is Atomic CRM?#

Atomic CRM is an open source CRM published by Marmelab, the French software agency behind React-Admin. It's available on GitHub at github.com/marmelab/atomic-crm under the MIT license.

The stack:

• Frontend: React-Admin (a React framework for building data-driven UIs)
• Backend: Supabase (PostgreSQL-based backend-as-a-service)
• Auth: Supabase Auth
• Hosting: Self-hosted or deployed to Vercel/Netlify + Supabase Cloud

It's not a traditional packaged application you download and install. It's more of a template or starter kit that you fork and customize.

Architecture and Technical Design#

React-Admin Foundation#

React-Admin is one of the most popular frameworks for building admin interfaces in React. It handles list views, create/edit forms, filtering, sorting, and pagination with minimal code. The Atomic CRM codebase demonstrates how React-Admin's components can be assembled into a complete CRM.

For React developers, this is genuinely educational. You can see how to implement a contact list, deal pipeline, task management, and notes — all using React-Admin's standard components.

Supabase Backend#

Supabase provides the database (PostgreSQL), authentication, real-time subscriptions, and storage. The Atomic CRM schema is straightforward: tables for contacts, deals, companies, activities, and notes.

Because Supabase is just PostgreSQL under the hood, you have full SQL access to your data. This is a meaningful advantage over traditional CRMs that restrict data access to their own query interfaces.

Deployment Model#

You deploy Atomic CRM by forking the repository, connecting it to a Supabase project, and deploying the frontend to a hosting service. This is not the same as installing an application — it requires familiarity with modern web deployment workflows.

Core Features#

Contacts and Companies#

Standard contact management: name, email, phone, company, job title, notes. The list view supports search and filtering. The detail view shows all associated activities, deals, and notes.

The UI is clean and modern — noticeably better than PHP-based alternatives like Vtiger or SuiteCRM. React-Admin components render quickly and handle responsive layouts well.

Deal Pipeline#

A basic Kanban board for deal management. Stages are configurable in the Supabase database. Deals can be linked to contacts and companies.

The Kanban implementation is functional but basic. There's no revenue forecasting, no probability weighting, and no pipeline analytics out of the box.

Activity Log#

You can log notes, calls, and meetings against contacts and deals. The activity feed shows a timeline of interactions per contact. This is the core of what makes CRM useful — and Atomic CRM implements it cleanly.

Task Management#

Simple tasks with due dates, assigned users, and contact/deal associations. Not a full project management system, but adequate for basic follow-up tracking.

What Atomic CRM Does Well#

Modern stack: The React + Supabase combination is genuinely modern. Performance is good, the UI renders cleanly, and the developer experience is excellent compared to PHP applications.

MIT license: Full MIT, no AGPL restrictions. You can use it commercially, fork it, modify it, and never open-source your modifications.

Direct database access: Because the backend is Supabase (PostgreSQL), you have full SQL access to your CRM data. Write analytical queries, connect BI tools, export to any format you want.

Customizability: If you know React, you can add features, modify layouts, and integrate new data sources with relative ease. The React-Admin framework handles the boilerplate.

Good documentation: Marmelab is a professional agency with strong technical writing. The README and documentation are clear.

Where Atomic CRM Falls Short#

It's a Template, Not a Product#

This is the most important limitation to understand. Atomic CRM is a reference implementation, not a maintained commercial product. There's no issue tracker with roadmap items, no dedicated support, and no community of users trading tips. It's code that demonstrates a pattern.

If you use it in production, you are effectively owning the codebase. Feature gaps are your problem to solve.

Minimal Feature Set#

The core CRM features — contacts, deals, activities, tasks — are implemented. But everything you'd expect in a mature CRM is missing: email integration, workflow automation, reporting, dashboards, team permissions, API integrations, import/export, bulk actions, and more.

No AI Features#

Like Monica and EspoCRM, Atomic CRM has no AI capabilities. No natural language interface, no intelligent suggestions, no automated enrichment. You're working entirely through manual form-based data entry.

Requires Ongoing Supabase Management#

Supabase is a managed service, which means you're dependent on their infrastructure and pricing. If Supabase changes its pricing or you outgrow the free tier, you'll pay for their hosted service or manage a self-hosted Supabase instance (which is non-trivial).

The alternative — replacing Supabase with a different backend — requires significant code changes.

Not Beginner-Friendly#

If you're a non-technical user who wants to install a CRM, Atomic CRM is not for you. It requires Node.js, npm, a Supabase account, and a deployment pipeline. The setup process assumes developer familiarity.

Limited Pipeline Features#

The Kanban board is visual but lacks the pipeline analytics that sales teams need: win rate by stage, deal velocity, pipeline value, forecast accuracy. For anything beyond "see deals in columns," you'll need to build it yourself.

Who Is Atomic CRM For?#

Atomic CRM is specifically useful for:

• React developers learning how to build data-driven applications with React-Admin
• Agencies and consultants building custom CRM solutions for clients (it's a faster starting point than from scratch)
• Technical founders who want a fully customizable CRM and are comfortable owning the codebase
• Teams with specific requirements that no off-the-shelf CRM meets, who want a foundation to build from

It's not appropriate for:

• Non-technical users who want to install and use a CRM
• Teams that need enterprise features without building them
• Anyone who wants AI-native CRM capabilities

Atomic CRM vs. DenchClaw#

DenchClaw takes a fundamentally different approach. Rather than a web application with a database backend, it's a local-first AI agent workspace where the CRM is one component of a broader system.

For a developer building a custom CRM, Atomic CRM is a reasonable starting point. For anyone who wants a working CRM today with AI capabilities, DenchClaw is the faster path.

Alternatives to Atomic CRM#

If you're drawn to the "modern stack, open source" positioning of Atomic CRM, there are other options worth considering:

Twenty CRM#

Twenty is a newer open source CRM heavily inspired by Salesforce's data model, built with React and NestJS. It's more feature-complete than Atomic CRM and has a more active development community. Still requires self-hosting and technical setup.

DenchClaw#

The fastest way to get a working CRM with AI capabilities. Local-first, MIT licensed, installs in one command. Trades the React customizability for a more opinionated, fully featured system.

Supabase + Custom Build#

If you want full control over a Supabase-backed CRM, building from scratch on Supabase gives you more flexibility than forking Atomic CRM. The Supabase documentation is excellent.

Migrating From Atomic CRM#

If you've been using Atomic CRM and want to migrate, the good news is that your data is in a PostgreSQL database. You can export it with standard SQL tools:

COPY contacts TO '/tmp/contacts.csv' WITH CSV HEADER;
COPY deals TO '/tmp/deals.csv' WITH CSV HEADER;

This makes Atomic CRM one of the more data-portable options — a PostgreSQL export is a universal format that any destination CRM can import.

Frequently Asked Questions#

Is Atomic CRM production-ready?#

It depends on your definition. The code is functional and runs in production. But as a template rather than a maintained product, it lacks the support, documentation, and feature completeness of dedicated CRM products. Use it if you're ready to own and extend the codebase.

Does Atomic CRM work without Supabase?#

The application is tightly integrated with Supabase for auth and database. Replacing Supabase with a different backend would require significant refactoring. If you want more backend flexibility, building on React-Admin with a different data provider is an option.

Is Atomic CRM free?#

Yes, MIT licensed. You can use it commercially without restriction. You'll pay for Supabase hosting (or manage your own Supabase instance) beyond the free tier.

Can I use Atomic CRM for a team?#

The Supabase auth supports multiple users, so yes, technically. But the role/permissions model is minimal. For multi-user team environments with granular permissions, you'd need to build that functionality.

How does Atomic CRM compare to Twenty CRM?#

Both are modern React-based open source CRMs. Twenty is more feature-complete, has a larger development community, and includes more enterprise-adjacent features. Atomic CRM is simpler and more useful as a learning resource or customization starting point.

Ready to try DenchClaw? Install in one command: npx denchclaw. Full setup guide →