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 roomswacrm
wacrm is a self-hosted CRM template built on Next.js and Supabase that integrates with WhatsApp Business API. It includes shared inbox management, contact management, sales pipelines, broadcasts, no-code automations, and an AI reply assistant—designed to be forked, customized, and deployed quickly without vendor lock-in.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | ArnasDon/wacrm |
| Owner | ArnasDon |
| Primary language | TypeScript |
| License | MIT — OSI-approved |
| Stars | 1.4k |
| Forks | 3.5k |
| Open issues | 8 |
| Latest release | Unknown |
| Last updated | 2026-07-08 |
| Source | https://github.com/ArnasDon/wacrm |
What wacrm is
TypeScript-based Next.js 16 application backed by Supabase (Postgres + Auth + RLS) and Meta Cloud API integration. Features token encryption (AES-256-GCM), row-level security, HMAC-verified webhooks, CSP headers, rate limiting, and a public REST API; uses Tailwind v4 for UI and pgvector for semantic search in the knowledge base.
Get the wacrm source
Clone the repository and explore it locally.
git clone https://github.com/ArnasDon/wacrm.gitcd wacrm# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Supabase project setup, schema migrations, and RLS policy configuration are prerequisites; familiarity with Postgres and auth flows is beneficial.
- WhatsApp Business API requires Meta Business account, verified phone number, and webhook domain (HTTPS); integration involves production cert, webhook signing validation, and Meta approval flow.
- Encryption key management (AES-256-GCM) for tokens must be securely stored as `ENCRYPTION_KEY` environment variable; rotation strategy should be defined before production use.
- AI reply assistant requires external API keys (OpenAI or Anthropic, stored encrypted); cost attribution and usage monitoring fall to the operator, not wacrm.
- Knowledge base search leverages Postgres full-text or pgvector embeddings; embeddings require separate API key setup and incur per-request costs.
When to avoid it — and what to weigh
- You need turnkey multi-channel CRM (email, SMS, social media, etc.) — wacrm is WhatsApp-native; broader channel support (Slack, email, Telegram) is not included. Adding them requires custom development.
- Your team has no technical resources for infrastructure setup and maintenance — Even though Hostinger one-click deploy is offered, self-hosting requires familiarity with Supabase project management, environment variable setup, WhatsApp Business API credentials, and long-term maintenance.
- You require enterprise-grade support, SLAs, or audit trails baked in — wacrm is a community template without formal support contracts, SLA guarantees, or built-in comprehensive audit logging. Production deployments rely on your own monitoring and Supabase's audit capabilities.
- You need offline-first or mobile-native functionality — wacrm is a web application; mobile app support and offline sync are not part of the template.
License & commercial use
MIT License. Permits commercial use, modification, and redistribution. Attribution and license text must be retained in derivative works. No warranty or liability protection.
MIT is an OSI-approved permissive license that explicitly permits commercial use, including building proprietary products on top of wacrm. No royalties, licensing fees, or commercial restrictions apply. Forking for client work, resale, or internal business use is permitted. Retain the LICENSE file and MIT header in the codebase. Verify that Supabase, Meta APIs, and hosting provider terms also permit your intended commercial model.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Low |
| DEV.co fit | Strong |
| Assessment confidence | High |
Codebase implements token encryption (AES-256-GCM), Postgres row-level security on every table, HMAC-verified webhooks, Content Security Policy headers, and rate limiting. TypeScript and CI typecheck/build on every PR reduce runtime errors. Critical: (1) encryption key must be managed securely and rotated; (2) Supabase RLS policies should be audited after fork; (3) WhatsApp webhook must validate Meta signatures; (4) AI keys and database credentials must never be committed; (5) operator is responsible for ongoing monitoring, backups, and patches post-deployment. No formal security audit or penetration test mentioned; community-driven template model means security responsibilities lie with the deployer.
Alternatives to consider
Twilio Flex / Twilio CRM
Managed cloud CRM with multi-channel support (WhatsApp, SMS, voice) and enterprise SLAs. Avoids self-hosting but introduces vendor lock-in, seat-based pricing, and less customization freedom.
HubSpot (with WhatsApp integration)
Mature, feature-rich CRM with built-in WhatsApp integration via third-party connectors. No deployment overhead but subscription-based pricing, seat limits, and closed-source constraints.
Chatwoot or Haptik (open-source alternatives)
Open-source omnichannel platforms with WhatsApp support. Offer flexibility and self-hosting but broader scope (multi-channel) and steeper learning curve; less opinionated for sales CRM workflows.
Build on wacrm with DEV.co software developers
Fork wacrm on GitHub, configure Supabase and Meta API credentials, and deploy to Hostinger or your infrastructure in under an hour. Full docs and one-click deploy available.
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.
wacrm FAQ
Can I use wacrm without Hostinger?
What happens to my data if I fork wacrm?
Do I need to pay for AI features?
Is there upstreaming expectation or ongoing sync after I fork?
Build it with a software development company
Pairing wacrm with the rest of your stack is where most open-source crm projects stall. DEV.co is a software development agency that does the integration work — plus AI development when models are in scope.
Ready to deploy a WhatsApp CRM on your own terms?
Fork wacrm on GitHub, configure Supabase and Meta API credentials, and deploy to Hostinger or your infrastructure in under an hour. Full docs and one-click deploy available.