Folk vs Wacrm
Choose Wacrm when WhatsApp is the primary channel and owning, modifying, and self-hosting the CRM outweighs the operational work of maintaining a fork. Choose Folk for a hosted, broader relationship CRM spanning email, WhatsApp, meetings, LinkedIn activity, company research, and contextual follow-up or recap workflows. Wacrm offers deeper documented WhatsApp inbox, broadcast, and automation functions, but it is not a
Decision guide
The practical reasons to choose either option, based on documented capabilities.
Choose Wacrm if
- WhatsApp-first sales or support teams needing a shared inbox with assignment and internal notes
- Teams requiring self-hosted CRM data and modifiable MIT-licensed source code
- Workflows needing branching WhatsApp automations, waits, tags, deal creation, or webhooks your own infrastructure can run the application, Supabase, credentials, migrations, and automation scheduling; a managed Node.js,
Stay with Folk if
- Email, meetings, LinkedIn activity, and other channels must share one documented relationship history
- Context-aware follow-up detection and on-demand relationship or deal recaps are required
- Company firmographic enrichment and bulk research notes are important workflows personalized email campaigns and open, reply, and bounce tracking are required migration must preserve historical chats or pipeline history
Deployment and operations
Wacrm is MIT-licensed and intended to be forked and self-hosted. It uses Next.js 16 with Supabase and the official Meta Cloud API. Local setup requires Node.js 20+, npm, environment variables, Supabase migrations, and Meta credentials for WhatsApp functions. Docker and Docker Compose instructions are documented; Kubernetes support is not documented. The recommended production route is Hostinger Managed Node.js, although the README says it can run anywhere Node.js does. Operators must deploy fork
Migration considerations
Contacts can be exported from the current CRM as CSV and imported into Wacrm. The supplied material says historical chat transcripts and pipeline history do not transfer automatically, so teams should expect to start new conversation threads and rebuild pipeline stages.
Feature fit
What Wacrm covers
- Contact records with custom fields
- Customizable sales pipelines
- WhatsApp-linked relationship context
- AI-assisted response drafting
- Trigger-based workflow automation
- Campaign or broadcast delivery tracking
- External access through an API
What’s different or missing
- Documented email and LinkedIn history
- Meeting-centered interaction history
- Inactive-conversation follow-up detection
- On-demand relationship and deal recaps
- Company research and enrichment
- Personalized email workflow campaigns
- Email open, reply, and bounce tracking
Project snapshot
- GitHub stars
- 1,985
- Contributors
- 13
- Language
- TypeScript
- Last commit
- Aug 12, 2026
- Latest release
- Not available
Categories: Customer Relationship Management, Marketing Automation, Customer Support, Content Marketing, Sales Intelligence, Workflow Automation, Business Intelligence
Sources and editorial review12 linked sources
Public documentation supports this comparison. Automation assists collection and classification; editorial standards and corrections remain the responsibility of Kris.
Self-hostable CRM template for WhatsApp — shared inbox, contacts, sales pipelines, broadcasts, and no-code automations.
repository description · github.comThis repo is the product — clone or fork it to run your own CRM.
readme · github.comShared inbox on the official WhatsApp Business API — multiple agents working one number, per-conversation assignment, status, and notes.
readme · github.comNo-code automations — triggers on inbound messages, new contacts, keywords, or schedule; conditional branches, waits, tags, webhooks. Visual builder.
readme · github.comPublic REST API (`/api/v1`) with scoped, revocable API keys.
readme · github.comPrefer containers? See `docs/docker.md` for the Dockerfile + Docker Compose setup.
readme · github.comShared inbox on the official WhatsApp Business API — multiple agents working one number, per-conversation assignment, status, and notes.
verdict · github.comContacts + tags + custom fields, CSV import, deduplication.
shared feature · github.comSales pipelines (Kanban) with deals linked to conversations.
shared feature · github.comNote: wacrm is MIT-licensed and runs anywhere Node.js does (Vercel, Railway, your own VPS). Hostinger is recommended, not required.
deployment · github.comIf the database schema changed, apply any new SQL files from supabase/migrations/ in the Supabase SQL editor first — migrations are idempotent.
deployment · wacrm.techContacts, yes — export them as CSV from your current tool and import them into wacrm. Historical chat transcripts and pipeline history do not transfer automatically between systems, so plan to carry your contact list and start fresh on threads. Rebuilding pipeline stages takes a few minutes.
migration · wacrm.tech
