Open-Source CRM · ArnasDon

wacrm

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.

Talk to DEV.co Discuss Implementation

Source: GitHub — github.com/ArnasDon/wacrm

1.4k

GitHub stars

3.5k

Forks

TypeScript

Primary language

MIT

License (OSI-approved)

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.

Quickstart

Get the wacrm source

Clone the repository and explore it locally.

terminalbash

1git clone https://github.com/ArnasDon/wacrm.git2cd wacrm3# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Small to mid-market sales teams using WhatsApp for customer communication

Teams that already rely on WhatsApp Business API for customer outreach can consolidate conversations, manage pipelines, and coordinate across agents in a single shared inbox without SaaS monthly seat fees.

Agencies and consultancies needing white-label CRM capability

Since wacrm is a template designed to be forked and rebranded, agencies can customize it for client-specific workflows, add proprietary fields, and deploy it on their own infrastructure for recurring revenue or standalone use.

Organizations with high compliance or data residency requirements

Full ownership of code, database, and data—deployable on private infrastructure or within specific geographic zones—addresses concerns about third-party SaaS access to customer conversations and business data.

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

Security considerations

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.

Software development agency

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.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

nextcrm-app laravel-crm espocrm

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source CRM CRM Development Web App Development Cloud Deployment Talk to DEV.co

wacrm FAQ

Can I use wacrm without Hostinger?

Yes. wacrm is MIT-licensed and runs anywhere Node.js does: Vercel, Railway, Docker on VPS, or bare metal. Hostinger is recommended for simplicity but not required. You handle environment setup and deployment independently.

What happens to my data if I fork wacrm?

Your data lives in your own Supabase project (Postgres database). You own the infrastructure, the encryption keys, and all customer data. No sync to upstream wacrm. You are responsible for backups and compliance.

Do I need to pay for AI features?

wacrm's AI reply assistant and knowledge base search use external APIs (OpenAI, Anthropic, or embeddings service). You bring your own API key and pay the provider directly. wacrm charges no per-seat AI fee; you only pay for what you use.

Is there upstreaming expectation or ongoing sync after I fork?

No. wacrm is a template, not a framework. Forking is the expected usage model. Bug reports and security issues are welcome; feature PRs belong in your fork unless they are general-interest improvements. No auto-update mechanism exists.

Software development & web development with DEV.co

Need help beyond evaluating wacrm? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source crm integrations — and maintain them long-term.

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.

Talk to DEV.co Schedule a Consultation