SMS-24 is a multi-tenant SaaS that lets every user run their own AI workers across messaging (Telegram, WhatsApp), voice (real-time Telegram calls via Pipecat), and emulated Android devices. It also exposes real-time phone-reputation antifraud — a 50-millisecond verdict on any phone number against a graph of public SMS-receive numbers spanning 55+ countries.

What does an AI Worker do?

You create a Persona with a name, role, system prompt, biography, and knowledge base (free text plus uploaded PDF/DOCX/TXT/MD files). You link it to your Telegram and WhatsApp accounts. Inbound messages get auto-replied by the LLM you picked (OpenAI / Anthropic Claude / Google Gemini), using your own API key. You can also link a voice agent so the persona answers Telegram voice calls in real-time, and link device-action templates that the LLM can call as tools mid-conversation.

Do I bring my own LLM API keys?

Yes. SMS-24 is BYOK — you paste your own OpenAI, Anthropic, Google Gemini, Deepgram, Cartesia, and ElevenLabs keys in Settings. All keys are Fernet-encrypted at rest. Every LLM, STT, and TTS call from your personas bills your own account directly. We do not markup model usage.

What is persona function-calling?

When you link Android device-action templates to a persona, those actions are exposed to the LLM as OpenAI-compatible tools. Mid-conversation the model can decide to call them — for example send_whatsapp_text(phone, body), send_telegram_text(username, body), or install_apk_url(url). The action runs against your Android device(s) and the result is fed back into the conversation.

Can I route traffic through specific countries?

Yes. The operator runs a ProtonVPN orchestrator that spawns per-country VPN tunnels and exposes each tunnel as a SOCKS5 and HTTP proxy on the internal network. Your messenger accounts, voice agent, and emulated Android devices can all be pinned to a country — the matching proxy is auto-selected from the pool.

What is the phone antifraud product?

A REST API that returns a risk verdict on any phone in roughly 50 milliseconds. It draws on 12 orthogonal signals — public-board appearances, OTP collisions across services, fraud-ring cluster membership, carrier line-type, geo inconsistency and more. Used to block bot signups, fake KYC, and airdrop farms before you send an OTP.

How is data isolated between tenants?

Every user-scoped entity — personas, knowledge-base files, messenger accounts, Android devices, voice agents, service keys, action templates, action runs — carries an owner_user_id NOT NULL and is filtered at the SQL level by the authenticated user's id. Cross-tenant access returns HTTP 404, not 403, so the existence of other users' resources is never telegraphed. Secrets are Fernet-encrypted at rest.

Is SMS-24 GDPR compliant?

SMS-24 only ingests SMS messages and phone numbers that are already published on public SMS-receive websites. We never receive or store private SMS content from any user's phone. User-side data (personas, KB files, linked accounts, action runs) lives in your isolated tenant and can be exported or deleted on request. Billing data lives in Stripe.

What is the API rate limit?

Per-second rate limits scale with subscription tier: 2 requests per second on the daily plan, 10 on monthly, 30 on yearly. Limits apply per active API key. 429 responses include a Retry-After header.

How do I cancel my subscription?

Go to Billing in your account, click Cancel, and confirm with the SMS code we send to your verified phone. Cancellation takes effect at the end of your current billing period — access continues until then.

← Back to blog

Multi-account ProtonVPN orchestrator

2026-05-22 · 9 min read

If you run more than two messaging accounts, you eventually hit the problem that all of them talk to Telegram or WhatsApp from the same exit IP. Platforms notice; accounts get flagged. The fix is per-account network egress, which on a VPS without bare metal means VPN tunnels.

The orchestrator stores ProtonVPN credentials encrypted, and spawns per-country sessions on demand. Each session is a docker container running openvpn against the operator-uploaded .ovpn config; once the tunnel is up it starts danted (SOCKS5 :1080) and tinyproxy (HTTP CONNECT :3128) with per-session basic auth.

On healthy session, the manager calls the api gateway's admin proxies endpoint twice — once with the SOCKS5 URL, once with the HTTP URL — tagged with the session id, country, and vpn proxy_type. The existing proxy pool picks up the new entries instantly.

Consumers don't change: ProxyRotator.get_proxy(target_country="DE") was already country-aware. Scraper, OSINT TG resolver, messenger-hub, voice agent, openwa-bridge all pick from the same pool.

Operator UX: Configs tab (uploaded .ovpn files per region), Sessions tab (live external IP + Reconnect), Country plan tab (declare "US:3, DE:2, NL:1" and Reconcile).

Start free trial → · All features →

Multi-account ProtonVPN orchestrator

Related