Frappe CRM

Open-source CRM, honestly reviewed. No marketing fluff — just what you get when you self-host it.

TL;DR

• What it is: Open-source (AGPL-3.0) CRM built on the Frappe framework — leads, deals, pipelines, call logging, WhatsApp integration, and workflow automation, all on your own server [GitHub][website].
• Who it’s for: Small-to-mid sales teams that are paying for HubSpot’s paid tiers or Salesforce Essentials and want a clean, opinionated alternative with zero per-seat pricing [website].
• Cost savings: HubSpot Sales Hub Starter runs $20/seat/month and climbs fast. Frappe CRM self-hosted runs on a $10–20/month VPS with no per-user costs and no seat caps [website][GitHub README].
• Key strength: Unlimited users out of the box, genuine ERPNext integration for teams that want to connect CRM to accounting/inventory without a third-party bridge, and a Frappe ecosystem with 20+ years of production hardening [GitHub README][website].
• Key weakness: Installation requires the Frappe bench CLI — it is not a docker run one-liner and will stop a non-technical founder cold without help. The AGPL-3.0 license limits embedding in proprietary products. At 2,456 GitHub stars, the community is much smaller than competitors like Monica or Twenty [GitHub].

---

What is Frappe CRM

Frappe CRM is a purpose-built sales CRM that Frappe — the company behind ERPNext — built for their own internal sales team when off-the-shelf options were either too expensive, too generic, or too closed. The README is unusually candid about this: “As it turns out, available CRMs in the market could not meet our needs. Too basic. Too expensive. Not open source. Since ‘building our own’ is in our DNA, we built our own CRM.” [GitHub README]

The architecture is what you’d expect from any Frappe product: a Python/MariaDB backend running on the Frappe framework, a Vue.js frontend using the Frappe UI component library (called Espresso), and a REST API underneath everything. If you already run ERPNext, Frappe CRM is a one-command install on the same bench instance. If you don’t, you’re setting up a full Frappe stack from scratch [GitHub README].

The product covers the core CRM loop cleanly: leads → qualified contacts → deals → closed/won. Each entity gets a unified page that surfaces activities, comments, notes, tasks, call logs, and email history in a single scroll. There’s a Kanban board for visual pipeline tracking, custom views with saved filters, and email templates. More interesting is what sits on top of that core: a native call integration via Twilio and Exotel (with call recording), WhatsApp send/receive through Frappe WhatsApp, automatic Meta lead ingestion from Facebook and Instagram ads, and workflow automation for lead assignments and follow-ups [GitHub README][website].

As of this review: 2,456 GitHub stars, AGPL-3.0 license, compatible with Frappe v15/v16 [GitHub].

---

Why people choose it

The core pitch is three things: unlimited users, ERPNext integration, and the Frappe ecosystem.

On unlimited users. The CRM market has a pricing structure problem. HubSpot’s free tier is real but caps out fast — you hit the limit on contacts, sequences, and reporting, and the next tier starts at $20/seat/month. Salesforce Essentials is $25/seat. For a 10-person team, that’s $200–$250/month before you’ve gotten to any automation. Frappe CRM’s hosted tiers and the self-hosted path both drop the per-seat structure entirely. The homepage headline “Don’t pay per user” is the entire pitch in four words [website].

On ERPNext integration. This is where Frappe CRM has no equivalent in the self-hosted space. If you’re already on ERPNext for invoicing and inventory, connecting your CRM to your ERP is not an integration project — it’s a toggle. Customer records, quotes, and sales orders flow between systems natively. For any business running operational software alongside sales software, this eliminates an entire category of sync pain [GitHub README].

On the Frappe ecosystem. Frappe Framework has been in production since 2005. The bench tooling, the deployment patterns, the community documentation — it’s battle-tested in a way that newer CRM projects simply aren’t. If you have a developer who already knows ERPNext, deploying Frappe CRM is familiar territory [GitHub README].

The testimonial on the homepage from Nilay Patel (Vulcan Group) points to the WhatsApp integration as the standout: “Hands down, one of the best features of Frappe CRM is its WhatsApp integration. It’s a total game-changer for keeping in touch with our clients.” [website] For sales teams in markets where WhatsApp is the primary business communication channel — most of South Asia, Southeast Asia, Latin America, Middle East — that’s not a niche feature, it’s a core workflow requirement.

Third-party review data specifically covering Frappe CRM as software was not available at time of writing; no independent review sites had published assessments that were locatable. The analysis here draws from the GitHub README, official website, and Frappe’s documentation.

---

Features

Core CRM:

• Lead and deal management with unified activity pages (notes, tasks, comments, emails, calls in one view) [GitHub README]
• Kanban board with drag-and-drop across pipeline stages [GitHub README]
• Custom views: saved filters, sorting, columns, public/private/pinned views [website][GitHub README]
• Email templates for outbound sequences [GitHub README]
• Workflow automation for assignment rules, follow-up triggers, and stage transitions [website]
• Reports and analytics with customizable views [website]

Communications:

• Twilio integration: make/receive calls from inside the CRM, with call recording [GitHub README]
• Exotel integration: calls routed to agent mobile phones, with recording [GitHub README]
• WhatsApp integration via Frappe WhatsApp app (send/receive messages linked to lead/deal records) [GitHub README]
• Email threading and team discussion tracking [website]

Lead capture:

• Meta integration: automatic lead ingestion from Facebook and Instagram ad forms, pre-filled into the CRM pipeline [website]

Integrations:

• ERPNext: extend CRM into invoicing, accounting, inventory, purchasing — native, no middleware [GitHub README]
• REST API exposed for custom integrations [merged profile]
• Docker and docker-compose support [merged profile]

Infrastructure:

• Built on Frappe Framework (Python, MariaDB, Redis) [GitHub README]
• Vue.js frontend with Frappe UI / Espresso design system [GitHub README][website]
• Full REST API [GitHub README]

---

Pricing: SaaS vs self-hosted math

Frappe Cloud (their managed hosting):

Frappe offers managed hosting through Frappe Cloud. Shared hosting plans start at approximately $10/month for small teams; dedicated plans scale up from there. Exact current pricing should be verified at frappe.io/pricing at time of evaluation — SaaS pricing changes and the rate card was not confirmed in the available sources [website]. The key structural point is that plans are not per-seat — they’re per-site (a single CRM instance for your whole team) [website].

Self-hosted:

• Software license: $0 (AGPL-3.0) [GitHub]
• VPS: $10–20/month (2–4GB RAM minimum; Frappe stack is heavier than a simple Node app)
• Your time to install, maintain, and update

HubSpot for comparison:

• Free: real but limited (capped contacts, no sequences, no custom reporting)
• Starter: $20/seat/month (billed annually) — 5 users = $100/month
• Professional: $100/seat/month — 5 users = $500/month
• Operations Hub required for advanced automation: adds $50–$100/seat

Salesforce for comparison:

• Essentials: $25/seat/month
• Professional: $80/seat/month
• Automation (Flow) and integrations: often additional cost

Concrete savings for a 10-person sales team:

On HubSpot Starter: 10 seats × $20 = $200/month, or $2,400/year — before you hit any limits that push you to Professional.

On Frappe CRM self-hosted: ~$15/month for a decent VPS + your setup time = $180/year. That’s roughly $2,200/year saved.

On Frappe Cloud (estimated): ~$50–100/month depending on plan, still no per-seat cost = ~$600–1,200/year. Still well below HubSpot at scale.

The math gets more dramatic as team size grows. At 25 users, HubSpot Starter is $500/month. Frappe CRM on the same $15 VPS is still $15/month.

---

Deployment reality check

This is where Frappe CRM parts ways from tools like Activepieces or Mattermost. The install path is Frappe bench — a Python CLI that manages Frappe apps and sites. It is not difficult for a developer who has set up a Python web app before, but it is not “paste this docker-compose.yml and run” either.

What you actually need:

• Ubuntu 20.04/22.04 or Debian (officially supported) — bench works on macOS for development but Linux for production
• Python 3.10+, Node.js 18+, MariaDB 10.6+, Redis, wkhtmltopdf, and a few system dependencies
• A domain and reverse proxy (nginx is standard in the bench stack)
• At least 2GB RAM; 4GB recommended for a team deployment

The bench install sequence:

1. Install frappe-bench via pip
2. Initialize a new bench: bench init frappe-bench
3. Create a site: bench new-site your-site.com
4. Install the CRM app: bench get-app crm && bench --site your-site.com install-app crm
5. Configure production mode (nginx + supervisor) via bench setup production

That’s not terrifying if you’ve done web server setup before. For a founder who has never SSH’d into a Linux machine, it’s a long afternoon at best, a wall at worst [GitHub README].

Docker path: There is Docker support listed in the merged profile. Frappe maintains a frappe_docker repository with compose files. This is meaningfully easier than the full bench path, but even the Docker setup has more configuration surface than a typical self-hosted app. Expect 1–2 hours even with Docker if it’s your first Frappe deployment.

What can go sideways:

• Frappe bench manages multiple apps on one instance. If you already run ERPNext, adding CRM is clean. A fresh install for only CRM carries the full Frappe stack overhead, which feels like overkill for a team that just wants a pipeline board.
• The AGPL-3.0 license means if you’re building a product on top of Frappe CRM, your product must also be AGPL. This matters for anyone wanting to white-label or embed the CRM.
• WhatsApp integration requires the separate Frappe WhatsApp app and a Meta Business account with API access — not a toggle, a setup project [GitHub README].
• Twilio and Exotel integrations are built-in, but you still need active accounts with those providers to get call functionality working.

Realistic time estimates:

• Developer familiar with Linux: 1–2 hours to a working production instance
• Developer new to Frappe: 3–4 hours
• Non-technical founder following a guide: a full day, or hand this off to someone

---

Pros and Cons

Pros

• No per-seat pricing. Genuinely unlimited users on both self-hosted and cloud plans. This is the biggest structural advantage over every commercial CRM [website][GitHub README].
• ERPNext integration is native. If you use or plan to use ERPNext, the CRM-to-ERP bridge is a first-class feature, not an API project. Quotes, invoices, and customer records flow without a middleware layer [GitHub README].
• WhatsApp, Twilio, Exotel built in. Call logging and messaging integrations that require custom development in most CRMs are first-class, documented features here [GitHub README].
• Meta lead ingestion. Auto-pulling Facebook/Instagram ad leads directly into the pipeline with fields pre-filled is a meaningful timesaver for any team running social ads [website].
• Clean, modern UI. The Espresso design system (built with one of India’s top design teams, per the website) is genuinely polished — not the dated feel of older open-source CRMs [website].
• Frappe Framework maturity. 20+ years of production use behind the underlying platform. This is not a hobby project [GitHub README].
• Custom fields and data models. Adding custom fields or entire new data models is native to Frappe Framework — no plugin marketplace needed [website][GitHub README].

Cons

• AGPL-3.0 license. Copyleft that extends to any product that embeds or extends the code. If you want to build commercial software on top of Frappe CRM, you’re either releasing your product under AGPL too or negotiating a commercial license with Frappe [GitHub].
• Bench install is not beginner-friendly. The deployment path requires Linux familiarity that most non-technical founders don’t have. Docker reduces friction but doesn’t eliminate it [GitHub README].
• Small community for a CRM. 2,456 GitHub stars is honest traction but it’s a fraction of ERPNext’s ~25K or even newer CRM projects like Twenty CRM [GitHub]. Community-answered questions and third-party tutorials are sparse compared to HubSpot.
• Heavy stack for CRM-only use. You’re running a full Frappe environment (Python, MariaDB, Redis, Node, nginx) for what some teams just need as a pipeline tracker. Lightweight alternatives exist for that use case.
• No independent review record. No Trustpilot page, G2 profile, or meaningful Capterra presence was locatable — community adoption is genuine but largely concentrated in the Frappe/ERPNext user base.
• WhatsApp and Twilio require external accounts. The integrations are built-in but the underlying services aren’t free or trivial to configure [GitHub README].

---

Who Should Use This / Who Shouldn’t

Use Frappe CRM if:

• You have 10+ users and the per-seat cost of HubSpot, Pipedrive, or Salesforce is becoming a real line item.
• You’re already running ERPNext and want CRM that integrates without middleware.
• Your sales team communicates heavily via WhatsApp or uses Twilio for outbound calls.
• You have a developer (or budget to hire one) for initial setup and occasional maintenance.
• Your market is South Asia, Southeast Asia, LATAM, or MENA — Frappe has deep community roots there and the WhatsApp-first workflow fits.

Skip it (use Twenty CRM or Monica) if:

• You’re a solo founder or team of 2–3 who just needs a contacts + notes tracker. The Frappe stack is heavier than necessary.
• You want docker-compose up simplicity. Twenty CRM and Monica both offer that.

Skip it (use HubSpot free) if:

• You have under 1,000 contacts and basic pipeline needs. HubSpot’s free tier is genuinely functional for early stage, and you avoid setup entirely.
• You don’t have anyone technical who can run a Linux VPS.

Skip it (use Salesforce or HubSpot Pro) if:

• Your compliance team requires SOC 2 or enterprise SLA guarantees you control. Frappe Cloud may offer this eventually, but it’s not the current selling point.
• You need a massive third-party integration marketplace. Frappe CRM has a short integration list compared to HubSpot’s 1,000+ app ecosystem.

---

Alternatives Worth Considering

• Twenty CRM — newer, React-based, MIT-licensed, cleaner Docker install, GitHub-native metadata model. Good if you want modern code architecture and easier deployment, but less mature on integrations [general knowledge].
• Monica — personal CRM focus, not really a sales pipeline tool. Better fit for relationship management than B2B sales.
• SuiteCRM — the enterprise-grade open-source CRM with 15+ years of history, full feature parity with commercial tools, but a heavier and older UI. Worth considering if you need advanced reporting or multi-currency sales.
• HubSpot CRM (free) — for early-stage teams, the free tier is hard to beat on time-to-value. The ceiling is low, but for 0-to-$1M companies still figuring out their sales process, it’s the pragmatic choice.
• Pipedrive — the cleanest commercial pipeline CRM, $15/seat. Still per-seat, still proprietary, but extremely well-executed if you’re not trying to escape SaaS costs.
• ERPNext — if your needs extend into ERP territory (invoicing, inventory, HR) and you want CRM as part of that, ERPNext bundles a CRM module. Frappe CRM is the standalone, opinionated extraction of that module with a better UX.

---

Bottom Line

Frappe CRM is a serious piece of software with a clear use case: teams escaping per-seat CRM pricing, especially teams already in the Frappe/ERPNext ecosystem. The unlimited-users model is genuinely differentiated, the WhatsApp and call integrations are first-class, and the Frappe Framework gives it a production-hardened foundation that newer open-source CRMs don’t have yet.

The honest catch is the setup story. If you hand this to a non-technical founder today and say “deploy it,” they’ll hit a wall. The bench install path requires Linux familiarity that the target audience often doesn’t have. That’s not a dealbreaker — it’s exactly the kind of one-time deployment task that a studio or freelancer can handle — but it should be in the calculus upfront. The payoff, for a 10-person team paying HubSpot $200/month, is a self-hosted system that costs $15/month to run forever with no seats to count.

If the deployment is the blocker, that’s exactly what upready.dev handles for clients. One setup, you own the infrastructure.

---

Sources

1. Frappe CRM GitHub Repository — README, features, integrations, license. https://github.com/frappe/crm
2. Frappe CRM Official Website — homepage, feature descriptions, pricing structure, customer testimonials. https://frappe.io/crm
3. Frappe CRM Documentation — setup guides, configuration. https://docs.frappe.io/crm
4. Frappe CRM Live Demo — https://frappecrm-demo.frappe.cloud/api/method/crm.api.live_demo.login