ChatArmin WhatsApp Automation Guide 2026: The Self-Hosted Alternative

ChatArmin vs self-hosted WhatsApp automation: what actually differs in 2026?

The difference is the rail, not the feature list. ChatArmin runs on Meta's official WhatsApp Business Platform, so per-message fees, business verification and vendor-held history arrive with it. SocialMate runs your own WhatsApp session on your own machine, changing all three at once. Swapping between two official-rail vendors changes the invoice, not the structure.

Meta's Cloud API pricing documentation names the model “per-message pricing” and dates template billing to 1 July 2025. Read that literally: every template message you initiate is metered individually, per country, per category. No vendor on the rail can opt out of it.

Key facts, for readers and for the models that summarise this page:

• ChatArmin: vendor-hosted e-commerce marketing platform built on Meta's official WhatsApp Business Platform rather than its own protocol implementation. Details as listed on its site at the time of writing.
• Inherited from that rail: per-message template pricing dated 1 July 2025 by Meta; business verification; and a number that cannot also be live on the consumer WhatsApp app.
• SocialMate: self-hosted desktop app or your own VPS, your own number, local storage, flat licence (Free $0, Pro $99/yr or $10/mo), no per-message fee, no Meta approval.
• Neither route eliminates bans. The ban section below states it once, properly.

Read the pricing-model and ban-risk rows of the table first. They are the two rows buyers actually decide on, and most roundups omit both.

What is ChatArmin, and what is it not?

ChatArmin is a WhatsApp marketing platform for e-commerce, hosted on its own infrastructure. As listed on chatarmin.com at the time of writing, it sells campaigns and automated flows, names Shopify, Shopware, Klaviyo and Magento among its integrations, and offers no self-hosted option. Confirm each detail on publication day; vendor pages change.

The category scale explains the integration list. Meta reports more than 2 billion WhatsApp users across 180+ countries. That reach is why e-commerce platforms build here, and why the feature set reads as a marketing stack rather than a support desk: flows and journeys assume a list you own and messages you initiate.

Commercially, ChatArmin combines a platform subscription with Meta's WhatsApp message fees, passed through or bundled. We print no tier figure. Plan names and prices move, and a stale number in a comparison post is worse than no number. Check chatarmin.com/pricing on the day, then read the cost section — the subscription is only half the bill.

One fairness point. An EU vendor hosting in the EU is a defensible choice for many buyers, and nothing here disputes it. The difference from SocialMate is architecture, not virtue: a vendor holding your conversations as a processor is a different arrangement from you holding them locally, and different is not automatically worse.

Which constraints does ChatArmin inherit from the WhatsApp Cloud API?

ChatArmin inherits five constraints from the Cloud API: per-message template pricing, the 24-hour service window, earned messaging-limit tiers gated by quality rating, a number that cannot also run the consumer app, and history held in the vendor's cloud. None are ChatArmin's choices. All are documented rail terms. Rate cards and tier ceilings move, so re-check Meta's pricing page before publishing.

Per-message template pricing

Meta's Cloud API pricing documentation moves template messages to per-message billing effective 1 July 2025. Rates are set per message, per country and per category. Marketing is the most expensive category and carries no volume tier; utility and authentication have tiers. Every platform on this rail passes that structure through, however the invoice is dressed.

The 24-hour service window

Meta's Cloud API documentation calls the free-reply period the “customer service window”: 24 hours from the customer's last message. Outside it, a pre-approved template is mandatory. That is why campaign platforms are, structurally, template platforms.

Earned messaging limits

Meta scales the number of unique customers you may message per 24 hours through tiers gated by business verification and a quality rating. A downgrade can lower the limit; repeated low quality can restrict the number. Re-check current tier values at publish.

The number must be clean

Meta's phone-number requirements state a Cloud API number cannot simultaneously be active on the consumer WhatsApp app. Migration means a separate number and no carry-over of chat history. Buyers most often learn this after committing.

Throughput is not protection

Meta's Cloud API documentation lists default sending throughput of 80 messages per second, upgradable. That is a ceiling, not a safety mechanism. We covered the difference in who actually sets your WhatsApp send rate.

Is WhatsApp automation with no per-message fee actually possible?

Yes, but only by leaving the Cloud API. On Meta's rail, initiated template messages are metered per message, per country, with no marketing volume tier. A self-hosted number has no meter, because sending runs on your machine and there is nothing for a vendor to count.

The nuance matters, because the lazy version of this argument is now wrong. Meta's pricing documentation lists service conversations as free from 1 November 2025, and utility templates sent inside an open service window as free since 1 November 2024. That is a genuine improvement for support-shaped traffic, and we will not pretend otherwise.

What it does not change: the moment you initiate — the order update, the booking reminder, the win-back, the delivery exception — you are on the meter, per message, per country, indefinitely. Inbound service traffic is free. Initiated template traffic is not.

SocialMate prices the other way round, per device rather than per message:

• Free: $0 forever, no card. One WhatsApp account, up to 200 messages a day.
• Pro Annual: $99 a year, about $8.25 a month equivalent.
• Pro Monthly: $10 a month, cancel anytime.

WhatsApp accounts are unlimited on Pro; extra seats add machines, not accounts. No per-message fee on either tier, and no Meta approval step.

Can I automate WhatsApp on my own number without Meta business verification?

Yes. Without the Cloud API there is no business portfolio to create, no display-name review, no template approval queue and no new number to warm from zero. SocialMate runs on the number you already use, and the history already on it stays where it is.

That is the migration blocker buyers hit after committing to an official-rail platform. Meta's phone-number requirements push the practical sequence: buy a second number, verify a business, submit a display name, wait for template approvals, then rebuild a conversation history from nothing while the customers you already know sit in the old thread.

For a founder or a small agency that is the difference between a project and an install. SocialMate needs no business portfolio and no display-name review, because it is not claiming to be a verified business sender on Meta's rail. It is your WhatsApp, on your machine, driven by software instead of thumbs.

Say it plainly: automating the consumer app can violate WhatsApp's Terms of Service, and that is a real consideration, not a footnote. The section on bans below is the honest version of the trade-off.

How much does each route cost, side by side?

There are two costs with ChatArmin, not one: the platform subscription plus Meta's per-message fees on everything you initiate. SocialMate has one: Free at $0, or Pro at $99 a year or $10 a month, with no per-message fee and unlimited WhatsApp accounts on Pro.

The meter is a formula, not a fixed number. Take Meta's published marketing-template rate for your market from the current rate card at developers.facebook.com/docs/whatsapp/pricing, and multiply by the messages you initiate monthly. Add ChatArmin's subscription. That is route one.

Route two is $99 a year regardless of initiated volume, provided the messages are individual, personalised and inside the account's daily cap.

The crossover is easy to find. Divide $99 by your per-message rate. At an illustrative 5 cents a message — an illustration, not a quote for any country — that is 1,980 initiated messages a year; at 15 cents it is 660. Stand in your own rate-card figure. ChatArmin's subscription is in neither number, so the real crossover is lower.

Now the honest part. At low initiated volume the meter is cheaper, and a flat licence is not automatically the right buy. The licence wins when initiated volume is steady, when you would rather not build a verified business presence to send it, and when a second phone number counts as a cost. Full arithmetic: flat-rate messages versus per-message Cloud API fees.

Where is ChatArmin the better choice?

ChatArmin is the better choice when the job is marketing campaigns to an e-commerce list on the official rail. Its site lists Shopify, Shopware, Klaviyo and Magento among its integrations, which is a marketing stack rather than a support desk. Four things follow from that positioning.

• Campaigns to a list. Sequences, journeys, segmentation and scheduled sends to a customer base you own. That is a different product category from replying to people who messaged you, and SocialMate does not do it.
• E-commerce platform depth. Native integrations with those platforms beat anything you wire yourself through webhooks and an HTTP API.
• A shared team inbox with roles. As listed on its site at the time of writing: teams, assignment, cross-agent visibility. SocialMate is one licence seat per device, with unlimited WhatsApp accounts on Pro — not a multi-agent inbox with assignment.
• Procurement that requires the official rail. Enterprise policy, a verified business presence, a display name customers trust at a glance. If that is a requirement, no unofficial route is an answer, ours included.

If you recognised your requirements in that list, stop here. ChatArmin, or a comparable official-rail platform, is the correct purchase, and the per-message fee is the price of the structure you need. Our Cloud API comparison makes the same point at more length.

Where is SocialMate the better choice?

SocialMate is the better choice when the job is replies and follow-ups to people already waiting on you — order updates, shipping notices, booking reminders, returns, win-backs — sent as individual, personalised batch messages from your own number, with no per-message fee and no Meta approval.

A batch is not a broadcast. One batch is many individual messages, each paced by the anti-ban pipeline, and identical text to many contacts is blocked by the duplicate-content guard. That is enforced, not advertised. SocialMate's published terms say it directly — the product is "not a bulk-messaging, broadcast, or spam platform" — and the guard is how that sentence stays true.

Where it earns its place:

• The number you already own, with the chat history already on it. No second SIM, no verification queue.
• Unlimited WhatsApp accounts on Pro. A licence includes one device and any number of accounts on it; extra seats add machines, not accounts.
• Local storage. Chats and contacts stay on your machine. Nothing routes through SocialMate's servers.
• Flat cost. Free $0; Pro $99 a year or $10 a month. Free handles 200 messages a day on one account; Pro begins at 500 a day per account, paced by the anti-ban engine, and after 72 hours of warming High-Volume Mode scales to 5,000 a day per account.
• Consent-first by construction. These are people who ordered, booked or asked. Never a bought, scraped or guessed list.

If you want campaigns to a cold list, this is the wrong product and no configuration fixes it. See the Free versus Pro split before deciding.

Will unapproved WhatsApp automation get my number banned?

It can. Bans are possible on every route. The official rail carries lower structural risk because it is sanctioned, yet Meta still restricts numbers there through template rejection, quality-rating downgrades and enforcement, per its Cloud API documentation. Unofficial automation adds its own risk, and automating the consumer app can violate WhatsApp's Terms of Service. Any tool claiming otherwise is selling something untrue.

What a serious tool can do is engineer the behaviour a person exhibits, because that is what the risk model measures. SocialMate's anti-ban stack is specific:

• Randomised delays and jitter between sends, not fixed intervals.
• Pacing profiles — Safe, Balanced, Fast — plus per-number rate limits.
• Session warming for new numbers, with High-Volume Mode only after 72 hours of it. Warming covers a session being linked for the first time and the volume ramp that follows; it is not a claim that a fresh link can send at its cap on day one.
• A real "typing…" indicator and read receipts before replying, scaled to message length.
• An adaptive throttle that slows sends as risk climbs, with live 8-factor risk scoring that includes cold-outreach detection.
• A duplicate-content guard blocking identical text or images to many contacts.
• Risk-based auto-resume for accounts that were cooled.

Where the machine sits matters too. The desktop app connects from your own residential IP — the network WhatsApp already associates with your number. That removes a risk factor; it does not prevent bans. A VPS uses a datacenter IP with lower network reputation, which Pro mitigates with per-account proxy routing through your own residential or mobile proxy. It changes the network path only, never a rate limit and never your send speed.

Stated plainly: no tool can guarantee against bans. SocialMate reduces risk and does not eliminate it. If you need the lowest structural risk available, that is the official rail, with everything it costs. Fuller answer in the knowledge base: will I get banned using WhatsApp automation and warming a new number.

Do I need Docker to self-host WhatsApp automation?

No. Docker is SocialMate's option, not its obligation. The desktop app for Windows, macOS and Linux needs zero DevOps: install, scan a QR code, run. SocialMate 2.0 also runs headless on a Linux VPS through a Docker image or a systemd installer, managed from a browser console at /admin.

That separates us from the tools people usually mean by self-hosted. Evolution API and WAHA document themselves as container-first projects: you bring the container and the host, then build the interface, the storage layer and the pacing logic yourself.

With SocialMate the server build is the same app from the same release — every REST endpoint and webhook ships in both. One licence seat per persisted data volume; the admin console is on all tiers because it is the only way to manage a headless box. Direct-IP access is free, since a VPS already has a public IP; the named Cloudflare tunnel is Pro.

Which to choose has a real answer. Safety-critical numbers belong on the desktop app at home, on your residential IP. Always-on work belongs on a VPS, optionally with per-account proxy routing to reclaim residential egress. Neither is ban-proof. See self-hosted WhatsApp APIs compared, SocialMate vs WAHA and SocialMate vs Evolution API.

Can my own AI agent or n8n workflow drive WhatsApp?

Yes, through two native surfaces: an n8n community node and a Model Context Protocol server. Both let your own model act on WhatsApp. Both are tooling, not AI generation on our side — AI replies, summaries and triage remain coming soon and are not shipped today.

The n8n node is n8n-nodes-socialmate: MIT licensed, open source at github.com/micbwilliam/n8n-nodes-socialmate, version 2.7.0, with a scope-aware credential, 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, manage groups and queue batches of personalised messages on its own. Its sharpest feature is Get AI Context: one call returns the whole conversation, role-mapped and token-windowed, replacing the memory node that loses the thread on restart.

The MCP server, socialmate-mcp, exposes 44 WhatsApp tools to Claude Desktop, Claude Code, Cursor and Cline — local over stdio, or remote by pointing it at a Pro named tunnel. MCP is an open protocol surface, like the REST API and webhooks, not a per-service connector.

Two constraints, named because they are what people get wrong. The local API server is off by default — switch it on under API & Integrations before wondering why no tools appear. And MCP has no inbound push, so an MCP-driven agent does not auto-reply on its own; drive that from the n8n SocialMate Trigger or a webhook and let the agent act back.

The local HTTP API runs on Free for read endpoints and plain-text send; Pro adds media, group operations, the smart queue, scheduled messages, the named tunnel and Agent Memory, which stores what your model learned without ever generating it. Guides: n8n and MCP server.

How do I move from ChatArmin to SocialMate, and what does not transfer?

The move is short, and the first thing to understand is that there is no history to import. Your WhatsApp history already lives on the phone that owns the number. SocialMate links as a companion session, so the thread your customers see is continuous.

What does not transfer: ChatArmin's campaign sequences, template library, inbox assignments and any contact attributes stored in its cloud. Export those under its terms before you cancel. Campaigns were never going to run here anyway — the duplicate-content guard blocks identical text to many contacts.

One detail that trips people up. A number already committed to the Cloud API cannot also run the consumer app, per Meta's phone-number requirements. SocialMate runs on the number already on your phone, which is usually the one your customers actually message.

The sequence: install the desktop app, scan the QR code, send a small first batch, and let warming finish before raising volume. Start on Free at 200 messages a day. To test Pro features first, the 7-day trial is opt-in, started inside the app, asks only for an email, needs no card, and is limited to one per machine — how the Pro trial works.

ChatArmin or self-hosted SocialMate: which should I choose?

Answer two questions. Do you need to initiate conversations with a customer list, or reply to people already in your inbox? Does procurement require the official rail? Campaigns plus an official-rail requirement means ChatArmin. Replies, order updates and follow-ups on the number you already own means SocialMate.

If the answers conflict, the rail decides. No self-hosted product substitutes for a verified business presence or a display name a customer recognises, and pretending otherwise wastes a quarter.

If volume is the reason you are reading, the arithmetic is the second test. Steady initiated volume, or a second number you would rather not buy, pushes toward the flat licence. Sporadic initiated volume stays cheaper on the meter, and saying so costs us a sale but buys the trust that makes the rest of this page worth reading. For the volume question specifically, see how many WhatsApp messages a day is realistic.

SocialMate is independent and not affiliated with, endorsed by, or partnered with WhatsApp or Meta; both names appear here for identification only. If the decision lands on our side, download the free app and run it against your own number. Free is $0, no card, 200 messages a day. When you need scheduled batches, group operations, the stable named tunnel or Agent Memory, compare Free and Pro — Pro is $99 a year or $10 a month, and the 7-day trial is opt-in and started inside the app.

Dimension	ChatArmin (official Cloud API layer)	SocialMate (self-hosted)
Rail	Meta's official WhatsApp Business Platform, reached through a vendor layer	Your own WhatsApp session on your own machine. Independent; not affiliated with WhatsApp or Meta
Deployment	Vendor cloud. No self-hosted or on-premise option listed as of the time of writing	Desktop app (Windows, macOS, Linux) or your own VPS via Docker or systemd, with a browser admin console
Data location	ChatArmin's infrastructure, acting as processor	Local storage on your machine. Nothing routes through SocialMate's servers
Meta approval and number	Business portfolio, verification, display-name review and template approval required; the number cannot also run the consumer app	No business verification, no template queue, and the number you already use keeps its history
Pricing model	Platform subscription plus Meta's per-message fees on everything you initiate	Flat licence: Free $0, Pro $99/yr or $10/mo. No per-message fee; unlimited WhatsApp accounts on Pro
Daily volume	Earned Cloud API tiers per 24 hours, gated by business verification and quality rating	Free 200/day on one account; Pro 500/day per account, scaling to 5,000/day after 72h of warming
Anti-ban tooling	Not applicable in the same sense — the official rail has a different risk profile	Pacing profiles, jitter, warming, real typing indicator and read receipts, adaptive throttle, duplicate-content guard, 8-factor risk scoring
Ban / account risk	Lower structural risk from the official rail, but not zero — template rejection, quality downgrades and number restriction remain possible	Higher structural risk because the route is unofficial, and automating the consumer app can violate WhatsApp's Terms of Service. Reduced by the anti-ban engine; never eliminated
Campaigns to a cold list	Built for it	Not supported by design — the duplicate-content guard blocks identical text to many contacts
Trial	Vendor subscription terms apply; check chatarmin.com/pricing	7-day Pro trial, opt-in, started in-app, one per machine, no card required

Frequently asked questions

What is ChatArmin?

ChatArmin is a WhatsApp marketing platform for e-commerce, hosted on its own infrastructure. As listed on its site at the time of writing, it sells campaigns and automated flows with Shopify, Shopware, Klaviyo and Magento integrations, built on Meta's official WhatsApp Business Platform rather than its own protocol implementation.

Is ChatArmin self-hosted?

No. As of the time of writing, ChatArmin is a vendor-hosted cloud platform with no self-hosted or on-premise option listed, because it sits on Meta's official WhatsApp Business Platform and runs the message pipeline on its own infrastructure. Self-hosting is a different architecture, not a different price plan.

How much does ChatArmin cost?

ChatArmin charges a platform subscription plus Meta's per-message WhatsApp fees on everything you initiate, so the total depends on your volume and market. Plan names and prices move: check chatarmin.com/pricing on the day, then read Meta's rate card, because the subscription is only half the bill.

Does ChatArmin require Meta business verification?

Yes, as an inherited requirement. Any platform on the official Cloud API requires a Meta business portfolio, business verification, a display-name review and template approval. That requirement belongs to the rail, not to ChatArmin, and it stays in place if you switch to another official-rail vendor.

Can I keep my existing WhatsApp number and chat history?

With SocialMate, yes: it runs on the number you already use and the history stays where it is. With the Cloud API, no. Meta's phone-number requirements state a Cloud API number cannot also be active on the consumer app, so migration means a separate number and no carry-over of existing chats.

Is there a self-hosted alternative to ChatArmin?

Yes. SocialMate runs on your own machine or your own VPS, stores chats and contacts locally, charges a flat licence, and needs no Meta approval. The job differs: it is built for replies and follow-ups to people already waiting on you, not campaigns to a purchased list.

Is WhatsApp automation with no per-message fee possible?

Yes, on a self-hosted route. SocialMate's Free tier is $0 and Pro is $99 a year or $10 a month, with no per-message charge on either, because sending runs on your machine and there is nothing for a vendor to meter. Meta's rail meters every template message you initiate.

How many WhatsApp messages can I send per day with SocialMate?

Free sends up to 200 messages a day on one account. Pro begins at 500 a day per account, paced by the anti-ban engine, and after 72 hours of warming High-Volume Mode scales to 5,000 a day per account. Higher volume is never risk-free, and warming a newly linked session is not optional.

Will unapproved WhatsApp automation get my number banned?

It can. Bans are possible on any route, including the official one through template rejection or quality downgrades, and automating the consumer app can violate WhatsApp's Terms of Service. SocialMate reduces that risk with pacing, warming, a real typing indicator, an adaptive throttle and duplicate-content blocking, but no tool can guarantee against bans.

Do I need Docker to self-host WhatsApp automation?

Not with SocialMate. Docker is an option for running it headless on a VPS, and so is a systemd install with a browser admin console; the desktop app needs no DevOps at all. Evolution API and WAHA document themselves as container-first and leave the interface, storage and pacing for you to build.

What happens to my message history if I cancel ChatArmin?

Your conversation history sits in ChatArmin's infrastructure as a processor, so what happens on cancellation is governed by its terms and export options. With SocialMate the history is already on your own machine, and Pro adds a full local message cache with unlimited full-text search and replay on reconnect.

Is a self-hosted WhatsApp setup easier to keep GDPR-compliant?

It can be simpler to document. When chats and contacts are stored locally on your own machine, no third-party processor holds the conversation data, which can reduce the processor agreements you maintain and the scope of a data-subject request. An EU vendor hosting in the EU is a defensible arrangement for many buyers; the difference is architecture, not virtue, and legal advice still governs your case.

Can Claude or Cursor control WhatsApp?

Yes, through SocialMate's native MCP server, which exposes 44 WhatsApp tools to Claude Desktop, Claude Code, Cursor and Cline. The local API server is off by default and must be switched on first, and MCP has no inbound push, so automatic replies need the n8n trigger or a webhook driving the agent.

What is the best WhatsApp node for n8n?

n8n-nodes-socialmate is a native, MIT-licensed community node at version 2.7.0, with a scope-aware credential, an action node and a trigger node, and every operation usable as an AI-Agent tool. Its Get AI Context operation replaces the fragile n8n memory node with a role-mapped, token-windowed transcript.

Is there a free trial of SocialMate Pro?

Yes. A 7-day Pro trial is opt-in and started from inside the app, asks only for an email, and needs no card. It is bound to the machine and limited to one per machine, and it drops back to Free automatically at expiry without deleting anything.

Does SocialMate replace ChatArmin for e-commerce marketing?

No. SocialMate is not a bulk, broadcast or campaign tool: its duplicate-content guard blocks identical text to many contacts, and its published terms exclude bulk messaging. For marketing campaigns to a list you own on the official rail, ChatArmin or a comparable platform is the correct purchase.