Overview
Self-hosted senderZ gives you the same messaging platform — iMessage routing, SMS fallback, compliance engine, and multi-tenant API — running entirely on infrastructure you own. Your messages, your Cloudflare account, your Apple IDs, your physical hardware.
This option exists for organizations where data residency, regulatory compliance, or security policy prevents using a shared cloud platform. Healthcare companies pursuing HIPAA compliance, legal firms handling privileged communications, and financial services teams with strict vendor policies are the most common buyers.
What You Need
Before we begin a self-hosted engagement, confirm your organization can provide:
- A Cloudflare account on a paid plan (Workers Paid or Enterprise). senderZ deploys three Workers, a D1 database, KV namespaces, and a Queue. All of these run in your account under your billing.
- Dedicated Apple hardware (Apple Silicon recommended) that stays powered on 24/7 with a stable internet connection. This machine runs senderZ’s iMessage engine and a secure tunnel back to your Cloudflare account.
- One or more dedicated Apple devices with active SIM cards (or eSIMs) and dedicated Apple IDs. Each device becomes a sending line in your pool.
- Ops experience. Someone on your team should be comfortable with terminal commands, Cloudflare dashboard basics, and monitoring a headless server. You do not need to write code, but you do need to keep the hardware online.
The Four-Step Engagement
Self-hosted deployments follow a structured process. Every engagement goes through these four stages:
1. Scoping
We review your use case, message volume targets, compliance requirements, and network topology. This call typically takes 30 to 60 minutes. At the end, we produce a deployment plan that covers how many phones you need, which Cloudflare plan fits your usage, and whether any custom configuration is required.
2. Provisioning
We configure your Cloudflare account with the required Workers, D1 database, KV namespaces, and Queue bindings. We set up wrangler secrets for all sensitive credentials. If you need Clerk for portal authentication or Stripe for billing, those integrations are configured during this phase.
3. Deployment
We deploy the three Workers (API, Router, Billing) to your Cloudflare account, run database migrations, and verify all bindings. On your dedicated Apple hardware, we install and configure senderZ’s iMessage engine, connect your devices, establish a secure tunnel, and set up the device supervisor that monitors the bridge with automatic recovery.
We send test messages across every configured phone line and verify inbound webhooks, compliance checks (opt-out, quiet hours), and phone warming limits are all functioning.
4. Operation
After go-live, you operate the platform day to day. We provide an ops runbook covering common tasks: adding phones, rotating Apple IDs, handling delivery failures, and monitoring warming limits. For the first 90 days, our team is available for incident support.
What senderZ Provides vs. What You Provide
| senderZ provides | You provide |
|---|---|
| All Workers source code (API, Router, Billing) | Cloudflare account and billing |
| Device supervisor and monitoring scripts | Dedicated Apple hardware and network |
| Ops runbook for day-to-day operations | Dedicated Apple devices with active SIM/eSIM |
| Deployment and configuration during onboarding | Dedicated Apple IDs per phone line |
| 90-day incident support post-launch | Team member(s) to manage hardware |
| Software updates and security patches | Physical access to hardware when needed |
HIPAA BAA
A HIPAA Business Associate Agreement is available exclusively for self-hosted deployments. Because your data never touches senderZ infrastructure — messages, contacts, and consent logs all live in your Cloudflare D1 database — the compliance boundary is clear and auditable.
If you require a BAA, mention it during the scoping call. We will include it in the contract and walk your compliance team through the architecture.
Pricing
Self-hosted senderZ is sold as a custom annual contract. The engagement includes initial deployment, 90-day incident support, and ongoing software updates.
The monthly retainer starts at approximately $2,000/month, depending on the number of phone lines, message volume, and support tier. Enterprise deployments with multiple hardware clusters or dedicated engineering support are priced individually.
There are no per-message fees. You pay for the infrastructure (Cloudflare and carrier costs) directly.
Next Steps
- Review the self-hosted product page for a summary of what is included.
- Read the architecture overview to understand how the Workers, Queue, and iMessage engine fit together.
- Contact our team at [email protected] to schedule a scoping call.