AI ERP with agents inside the systems you run
AI phone and voice agents for real calls
LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
CyberAttack.aiThreat detection and defense
Secure AI virtual data roomsatomic-crm
Atomic CRM is a full-featured, open-source customer relationship management application built with React, shadcn/ui, and Supabase. It provides contact management, task tracking, deal pipelines, email capture, and customizable workflows suitable for small to mid-sized teams.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | marmelab/atomic-crm |
| Owner | marmelab |
| Primary language | TypeScript |
| License | MIT — OSI-approved |
| Stars | 1.1k |
| Forks | 722 |
| Open issues | 9 |
| Latest release | v1.5.0 (2026-03-10) |
| Last updated | 2026-06-29 |
| Source | https://github.com/marmelab/atomic-crm |
What atomic-crm is
A TypeScript-based React application backed by Supabase (PostgreSQL + Auth), featuring React Hook Form, React Query, React Router, and shadcn component library. Local development uses Docker for Supabase, with Vite as the dev server and Playwright for e2e testing.
Get the atomic-crm source
Clone the repository and explore it locally.
git clone https://github.com/marmelab/atomic-crm.gitcd atomic-crm# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires Docker and Node 22 LTS; local Supabase setup adds dependency management complexity. Pre-deployment testing via `make test` and `make test-e2e` is mandatory.
- Supabase database schema and auth rules must be configured post-clone. No built-in migration wizard; schema design falls on implementer.
- Email capture feature (CC workflow) requires mail server or third-party integration; Inbucket used for local testing only.
- Customization relies on forking and modifying React components directly; shadcn registry updates may conflict with local changes.
- Activity logging and data export functionality present but extent of audit capabilities unclear; verify against compliance requirements.
When to avoid it — and what to weigh
- Enterprise-scale, multi-tenant SaaS operation — No multi-tenancy architecture evident; designed for single-organization self-hosting. Scaling, billing, and tenant isolation require significant custom work.
- Regulated industries requiring formal support SLA — Community-maintained project with no commercial support contract. Healthcare, finance, or compliance-heavy verticals may need vendor guarantees.
- Need for deep third-party CRM ecosystem integrations — Built-in integrations limited to auth providers and API hooks. Requires custom development for Salesforce, HubSpot, Pipedrive connectors.
- Zero deployment infrastructure or DevOps overhead — Requires Docker, Node 22, Supabase, and PostgreSQL familiarity. Not a managed SaaS; you own operational burden.
License & commercial use
MIT License (MIT). Permissive OSI license permitting commercial use, modification, and redistribution with attribution. No copyleft requirements.
MIT license explicitly allows commercial use, private deployment, and proprietary modifications. However, no warranty or liability indemnification is provided. Use in production requires your own risk assessment, security audit, and support plan.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
Project uses Supabase auth (supports OAuth 2.0 via third-party providers) and PostgreSQL backend. Access control via login and Supabase role-based policies. However, no security audit, penetration test, or CVE disclosure process mentioned. Self-hosted deployments require secure TLS, secrets management, and database hardening. Email capture and activity logging may surface sensitive data; review retention and access controls before production use.
Alternatives to consider
Odoo CRM
Mature, enterprise-grade open-source CRM with built-in accounting, HR, and ERP modules. Larger codebase and steeper learning curve but more integrations and commercial support options available.
Plane (Project Management / CRM hybrid)
Modern React-based alternative for teams blending project and relationship management. Simpler data model but less specialized for sales pipelines.
Salesforce (Commercial SaaS)
Industry standard with extensive ecosystem, multi-tenancy, formal support, and regulatory compliance certifications. Higher cost but eliminates deployment and infrastructure burden.
Build on atomic-crm with DEV.co software developers
Test the demo, review deployment requirements, and assess security/compliance fit. Contact Devco for guidance on customization, hosting, or production deployment support.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
atomic-crm FAQ
Can I run Atomic CRM in production today?
How do I integrate Atomic CRM with our existing CRM or business tools?
What happens if the Marmelab team stops maintaining this project?
Is Atomic CRM HIPAA, GDPR, or SOC2 compliant?
Build it with a software development company
DEV.co is a software development company with a dedicated AI development practice. Whether atomic-crm is a component or the centerpiece, we design the surrounding open-source crm architecture and ship it.
Ready to evaluate Atomic CRM for your team?
Test the demo, review deployment requirements, and assess security/compliance fit. Contact Devco for guidance on customization, hosting, or production deployment support.