What Is SocialMate? Self-Hosted WhatsApp Automation, Defined

What is SocialMate?

SocialMate is a WhatsApp automation app that runs on your own machine, on your own number, with no Meta Business approval. It ships as a desktop app for Windows, macOS and Linux, or as the same app self-hosted on a VPS through Docker or systemd. It runs on a flat license and keeps chats in local storage.

In short

• What it is. A local WhatsApp automation app with an engineered anti-ban pipeline, a local HTTP API, a native n8n node and a native MCP server.
• What it costs. Free at $0 forever, or Pro at $99/year ($8.25/month equivalent) or $10/month. No per-message fee on any tier.
• What it is not. Not the WhatsApp Cloud API, not affiliated with Meta, not an AI writer, not a bulk-messaging platform, and not ban-proof.
• Who it is for. Founders, agencies, marketers and developers who want WhatsApp automation on their own number without an approval queue or a meter.

The demand behind that is measurable. Sendblue's 9 April 2026 setup guide notes that consumer WhatsApp is used by over two billion people and that its terms prohibit commercial use at scale — the structural tension every unofficial route lives inside. WhatsApp's own State of Business Messaging library reports that 73.3% of 11,056 consumers across 22 markets prefer messaging a business. Read that as vendor research: directional, not decisive.

The open question is not whether people want to message a business. It is who owns the pipe, and who owns the bill.

Is SocialMate the official WhatsApp API, or affiliated with Meta?

No. SocialMate is independent — not affiliated with, endorsed by, or partnered with WhatsApp or Meta — and it does not use the WhatsApp Cloud API. It connects as a linked device, the same mechanism WhatsApp Web uses, on the customer's own number. Nothing about that connection is approved or endorsed by Meta.

Three different things get collapsed into one in most comparisons:

• The official WhatsApp Cloud API. Meta-operated, per-message billing, business verification, template approval, public webhook infrastructure. Official status is real, and it costs what it costs.
• Linked-device open-source engines. Unofficial. Evolution API, WAHA and Baileys pair a normal number and leave the anti-ban layer, the interface and the storage to you.
• SocialMate. Unofficial. Own number, own hardware, shipped anti-ban stack, browser admin console, local storage, flat license.

One constraint, stated rather than buried: Sendblue's 9 April 2026 setup guide records that consumer WhatsApp's terms prohibit commercial use at scale. Every unofficial route carries terms risk, and that risk sits with the operator — which is why consent-first messaging is the only defensible way to use any of them.

What does SocialMate cost, and why is there no per-message fee?

SocialMate is free at $0 forever with no card: one WhatsApp account, up to 200 messages a day. Pro is $99/year ($8.25/month equivalent) or $10/month, cancel anytime. A 7-day Pro trial is opt-in — started inside the app, one per machine, no card, only an email.

The reason there is no per-message fee fits in one sentence: the work runs on the customer's computer, so there is nothing to meter.

Meta's own "WhatsApp Business Platform pricing" page puts the contrast in one phrase: it charges "per message delivered," by category and market. Treat the phrase as the shape of the model rather than a rate card, and price your own market from Meta's current sheet. A delivered message is an event someone can bill. When the sending happens on your own hardware, the event disappears from anyone else's ledger, and the license is priced per device instead.

One license includes one device; extra concurrent machines are seats at $4/month, or about $40/year on annual. What Pro adds, concretely: unlimited WhatsApp accounts, 500 messages a day per account as the safe starting ceiling, media and group operations, polls, scheduled messages and batches, the smart queue, a named tunnel and unlimited webhook deliveries. Free is not a demo — human-like pacing, session warming, live risk scoring, read receipts, the typing indicator and the local API's read and plain-text send endpoints all ship on it.

How does the Cloud API's per-message pricing actually stack up?

On the official route every reply is a billing event, and in 2026 the free part of the conversation narrowed. According to Zendesk's 10 August 2026 notice, from 1 October 2026 non-template replies inside the 24-hour customer service window move from free to charged per message, and utility templates inside an open window are charged too. That is a BSP write-up of a Meta change, so verify it against Meta's own documentation before you build a budget on it.

A worked comparison, illustrative and labelled as such. Rates: $0.025 per US marketing message (Chatfuel, 2 September 2026); Twilio's add-on at $0.005 per message each way (Genuka, 8 October 2026).

Outbound US marketing messages	1,000	5,000	10,000
Meta fees at $0.025	$25	$125	$250
Plus Twilio at $0.005 each way	$30	$150	$300
SocialMate Pro Annual	$99/year	$99/year	$99/year

Inbound replies add another $0.005 each on Twilio. The honest trade, stated rather than implied: the Cloud API is official and built for business-wide scale — its messaging limits are reported as calculated at business-portfolio level rather than per number (instantreply.co, 4 September 2026, citing Meta's developer documentation). SocialMate is unofficial, capped per account, and carries ban risk. The point is the shape of the bill, not a like-for-like win.

What can you automate on your own number without Meta Business approval?

You can automate on your own number with no business verification, no template approval and no public HTTPS webhook server to operate. The local HTTP API runs on every tier — read endpoints and plain-text send are free — and the platform exposes 35 webhook events, 9 of them free.

Developer appetite for that route is visible in public numbers. Pasquale Pillitteri's 27 August 2026 analysis cites 9,433 GitHub stars and 7,100+ forks for Evolution API, an unofficial linked-device engine — evidence that people are choosing no-approval automation in volume, whatever the terms say.

• Local HTTP API. An x-api-key header plus outbound webhooks. Free covers read access and plain-text send up to 200 a day; Pro adds media, polls, locations, contact cards, group operations, the smart queue, scheduled messages, a stable named tunnel and unlimited webhook deliveries. Reference at /docs.
• n8n. A first-class native community node, n8n-nodes-socialmate, with a scope-aware credential isolated per account, an action node and a trigger node. Every operation is exposed as an n8n AI-Agent tool, so an agent can send, read, look up contacts and queue batches on its own. Guide at /docs/n8n.
• MCP. A native socialmate-mcp server exposing 44 WhatsApp tools to Claude Desktop, Claude Code, Cursor and Cline. Setup at /docs/mcp-server — and switch the API server on first, because it is off by default.

The boundary matters. MCP is an open protocol surface, like the REST API and webhooks. It is not a per-service connector. SocialMate supplies the hands and the memory; the customer's own LLM is the brain. That split explains why AI replies, summaries and triage remain coming soon rather than shipped.

Where does my data live?

Chats and contacts stay in local storage on the customer's own machine. No SocialMate server sits in the data path for them, so there is no copy on our side to route, retain or hand over. On a desktop that means your disk; on a VPS it means the data volume you own and persist.

Running headless on a server does not change the model — the volume is yours, the admin console is yours, the backup is yours. What leaves the machine is what you choose to send out: webhook deliveries and API calls you configure.

This has become a procurement line rather than a preference. imbee's 28 May 2026 APAC checklist for ISO 27001 and customer messaging treats vendor risk across Meta, the BSP and the underlying cloud as a top 2026 audit item, alongside audit trails and retention windows. When the auditor asks where the conversation is stored, "in a vendor's cloud, in a region I would have to look up" is the answer that costs weeks.

One limit, stated plainly: self-hosting removes a vendor from the data path. It does not make anyone compliant by itself. Retention, lawful basis, disclosure and consent remain the operator's job — the questions the EU AI Act piece works through.

Will I get banned?

Yes, you can be. Bans are always possible on every route, official or not, and no tool eliminates them — SocialMate included. A vendor who promises otherwise is selling reassurance rather than software. What you control is pacing, the volume ramp, content uniqueness and monitoring, and a gradual ramp plus monitoring is the safe default.

The mechanism is not fully public. Sendblue's 9 April 2026 guide records that WhatsApp's terms restrict commercial use at scale, and one commentator cited in Pillitteri's 27 August 2026 analysis characterises the Baileys connector as breaking those terms and getting numbers banned — one person's characterisation, not our claim. What is not in dispute is that enforcement exists, and that no vendor can guarantee against it.

What the anti-ban pipeline does about it: randomised delays and jitter with Safe, Balanced and Fast pacing profiles and per-number rate limits; session warming for new numbers, with 72 hours of warming required before High-Volume Mode; read receipts and a real "typing…" indicator before replying; an adaptive throttle that slows sends as risk climbs; a duplicate-content guard that blocks identical text or images to many contacts; live risk scoring including cold-outreach detection; and risk-based auto-resume for accounts that were cooled.

On network position: the desktop app connects from your own residential IP — ideally the same home network as the phone that owns the number. That removes a risk factor; it does not prevent bans. A VPS uses a datacenter IP, and Pro's per-account proxy routing lets that account egress through your own residential or mobile proxy. It changes the network path only. It never bypasses a rate limit or shortens warming. The longer answer sits at /kb/will-i-get-banned/.

How many messages can I send per day?

Free sends up to 200 messages a day on one account. Pro starts at a safe 500 a day per account and, through High-Volume Mode, scales to 5,000 a day per account — only after 72 hours of warming. High volume is never safe on day one, and warming is not optional.

That 5,000 is a ceiling the software will allow, not a target to hit. Pro also lets you set a lower custom cap per account, which is the right move for a number that carries real conversations. Free and Pro share the same burst logic, three and five sends in a ten-second window respectively, so the pacing profile rather than the daily number shapes how a session looks.

The comparison that matters is structural. Meta's business messaging limits are reported as calculated at business-portfolio level rather than per number (instantreply.co, 4 September 2026, citing Meta's developer documentation; Qontak's help centre described the same change in a 22 January 2026 FAQ). One number's quality now touches the others. A self-hosted channel on your own number sits outside that portfolio — with its own, smaller ceiling and its own risk.

How does SocialMate compare with the Cloud API and with self-hosted engines?

The four routes differ in three ways that matter more than any feature list: how you are billed, where the conversation lives, and who carries the ban risk. The Cloud API is official and metered. The BSPs are official with a markup or a per-number license. The open-source engines are free and unofficial. SocialMate is flat and unofficial.

The table below sets all four side by side on pricing model, ban risk and data location. The short verdicts:

• WhatsApp Cloud API direct. For teams that need official status and business-wide scale. Pricing model: per message delivered, by category and market. Trade-off: verification, templates, and a meter that reportedly now covers service-window replies.
• BSPs (Twilio, 360dialog, WATI). For teams that want managed onboarding. Pricing model: Meta's fees plus a markup or license. Trade-off: you inherit the meter and add a second invoice.
• Open-source engines (Evolution API, WAHA, Baileys). For developers who want code and will build the rest. Pricing model: free license, real cost in VPS and engineering time. Trade-off: Docker becomes an obligation, and anti-ban, GUI and storage are yours to write. See /compare/self-hosted/.
• SocialMate. For founders, agencies and developers who want their own number without approval or a meter. Pricing model: flat, $0 or $99/year. Trade-off: unofficial, capped per account, and bans stay possible.

The open-source engines are genuinely good at what they do. Pillitteri's 27 August 2026 article cites 9,433 GitHub stars for Evolution API, and records one commentator describing the Baileys connector as breaking WhatsApp's terms and getting numbers banned — one person's characterisation, not our claim. What is not in dispute is the division of labour: the engine ships; the anti-ban layer, the interface and the storage do not. Full breakdown at /compare/ and /compare/cloud/.

What SocialMate is not

This section is definitional, and it carries more weight than the feature list. SocialMate is not the official WhatsApp Business API, not affiliated with WhatsApp or Meta, not an AI writer, not a bulk-messaging platform, not a calling product, not a source of contact lists, and not ban-proof. Seven exclusions, stated in full.

• Not official, not affiliated. No approval, endorsement or partnership from WhatsApp or Meta, and no use of the Cloud API.
• Not a bulk-messaging, broadcast or spam platform. A batch is many individual, personalised messages, each paced by the anti-ban pipeline. The duplicate-content guard blocks identical text or images to many contacts. It messages people who are already waiting on you — they ordered, they booked, they asked. Unsolicited bulk messaging is the fastest route to a ban.
• Not an AI writer. AI replies, summaries and triage are coming soon and are not shipped. Agent Memory only stores what the customer's own model produced — a contact name, notes, a media description — and never generates it.
• Not a calling product. It automates WhatsApp messages; it does not place voice or video calls.
• Not a source of contact lists. No scraping, no guessing, no bought data. Consent is required.
• Not shipping interactive buttons or list menus. They are deprecated on the WhatsApp Web protocol; polls are the supported primitive.
• Not ban-proof. Bans are always possible on every route, official or not. Sendblue's 9 April 2026 guide records that WhatsApp's terms prohibit commercial use at scale, and enforcement is real — any claim to the contrary would be false.

What should you read next if you are evaluating SocialMate?

Four questions decide whether SocialMate fits, and each has a page behind it. Take them in order.

Is the bill the problem? Then test the flat-rate argument. WhatsApp Messaging Limits in 2026 covers portfolio-level limits and where a self-hosted channel fits; the WATI pricing alternative and Evolution API pricing pieces take the metered and the "free" routes apart line by line.

Do you want your own number without an approval queue? Read There Is No Unofficial WhatsApp Business API. It sets out what the official route genuinely requires, which is more than most roundups admit.

Does the conversation have to stay on your infrastructure? Start with self-hosted messaging independence. If your auditor is involved, the EU AI Act piece is the one to forward.

Is this for a developer? The native n8n node is documented at /docs/n8n, the MCP server at /docs/mcp-server, and the API at /docs. If ban mechanics are the worry, Baileys Anti Ban explains what an engine has to do that a library does not.

When you are ready, the free app runs today with no card, and /pricing is one page with no calculator required.

Option	Pricing model	Ban / account risk	Data location	Who it is for
WhatsApp Cloud API (direct to Meta)	Per message delivered, by category and market; service-window replies reportedly charged from 1 October 2026 per Zendesk's 10 August 2026 notice	Official route; messaging limits and quality rating can still restrict or suspend sending	Meta's cloud	Teams that need official status and business-wide scale
BSPs (Twilio, 360dialog, WATI)	Meta's fees plus a markup or per-number license (Twilio +$0.005 per message each way; 360dialog from €49 per number per month, per Genuka's 8 October 2026 comparison)	Same as the official route, plus BSP policy on top	BSP cloud and Meta	Teams that want managed onboarding and support
Open-source engines (Evolution API, WAHA, Baileys)	Free license; you pay in VPS, engineering time and maintenance	Unofficial; no anti-ban layer out of the box, and bans are a live risk	Your VPS	Developers who want code and will build the rest
SocialMate	Flat license: $0 Free, $99/year or $10/month Pro; no per-message fee; one device included, extra seats $4/month	Unofficial; the anti-ban engine reduces risk, but bans remain possible on every route	Your machine, or your own VPS data volume	Founders, agencies and developers who want their own number without approval or a meter

Frequently asked questions

Is SocialMate free?

Yes. Free is $0 forever, no card, with one WhatsApp account and up to 200 messages a day — human-like pacing, session warming, live risk scoring, read receipts, the typing indicator and the local API's read and plain-text send endpoints are all included. Pro is $99/year ($8.25/month equivalent) or $10/month, and a 7-day Pro trial is opt-in, one per machine, and needs only an email.

Do I need Meta Business verification or template approval?

No. There is no Meta Business verification, no template approval and no public HTTPS webhook server to operate. SocialMate connects to WhatsApp as a linked device on the customer's own number, and its API is local. A Pro named tunnel provides a stable public URL only when an outside service needs to reach it.

Can I use my existing WhatsApp number?

Yes. SocialMate pairs your existing WhatsApp number as a linked device, the way WhatsApp Web does. There is no dedicated number to buy, no migration and no business account to create. Because it is an unofficial route, the terms risk of automating a consumer number remains yours to weigh.

Where is my data stored?

Chats and contacts are stored locally on your own machine, or on the data volume you own when self-hosted on a VPS. No SocialMate server sits in the data path for them, so no chat or contact data is routed through or retained on our infrastructure. What leaves the machine is only what you configure: webhook deliveries and outbound API calls you set up yourself.

Do I need Docker to run SocialMate?

No. Docker is an option, not an obligation. SocialMate runs as a desktop app on Windows, macOS and Linux with no DevOps work at all, or headless on a VPS via the Docker image or the systemd installer, managed from the browser at /admin. Docker is required by the open-source engines; here it is one of two deployment paths.

Will I get banned?

You can be, and no tool can prevent it — bans are always possible on any route, official or not. SocialMate reduces risk with randomised delays and jitter, pacing profiles, per-number rate limits, session warming for new numbers, read receipts and a real typing indicator, an adaptive throttle, a duplicate-content guard and live risk scoring including cold-outreach detection. That lowers the odds; it does not remove them.

How many messages can I send per day?

Free sends up to 200 messages a day on one account. Pro starts at a safe 500 a day per account and, after 72 hours of warming, High-Volume Mode scales it to 5,000 a day per account. That ceiling is what the software will allow, not a safe starting point: no volume is safe on day one, and a higher ceiling never removes the risk.

Does it work with n8n, Claude and Cursor?

Yes. n8n has a first-class native community node, n8n-nodes-socialmate, with a scope-aware credential isolated per account, an action node and a trigger node, and every operation is usable as an n8n AI-Agent tool. Claude Desktop, Claude Code, Cursor and Cline connect through the native MCP server, socialmate-mcp, which exposes 44 WhatsApp tools. Switch on the local API server first — it is off by default.

Does SocialMate write my replies with AI?

No. SocialMate runs no model and generates no replies, summaries or triage — those are coming soon and are not shipped today. It supplies the hands and the memory: your own LLM, in n8n or an MCP client, decides what to say. Agent Memory stores names, notes and media descriptions your model produced; it never writes them.

Is SocialMate the official WhatsApp API or affiliated with Meta?

No. SocialMate is independent — not affiliated with, endorsed by, or partnered with WhatsApp or Meta — and it does not use the WhatsApp Cloud API. It connects as a linked device on the customer's own number, the same mechanism WhatsApp Web uses.