Products · Self-Hosted
Run the senderZ control plane on your own infrastructure
For teams whose compliance or data-residency posture rules out a shared-tenant platform. You bring your own Cloudflare account and dedicated Apple hardware; senderZ deploys, configures, and supports the workers, SDKs, and iMessage bridge. You own the infrastructure, the audit trail, and the contract with your regulator.
Who it's for
For teams that can't share infrastructure.
Three audiences carry constraints that force a self-hosted posture. If your team's regulator, vendor-risk policy, or data-residency rule belongs to one of these, this is the path.
Enterprise
Vendor risk teams need infrastructure under your own contracts, not shared with unknown tenants.
Healthcare
HIPAA-bound teams that need a BAA and message bodies kept out of shared processing paths.
Gov / legal / finance
Regulatory data-residency requirements that cannot be met with a shared-region multi-tenant platform.
What you get
Your boundary. Our runbook.
Live capabilities ship today. Available-on-request items engage on the scoping call. Planned items carry quarter-precision ETAs.
Deploy on your own Cloudflare account
Available on requestThe three senderZ workers (api, router, billing) deploy to Cloudflare Workers inside your account. You own the infrastructure bill, the domain, and the audit trail.
BYO Apple hardware
The iMessage bridge runs on dedicated Apple hardware you own, in a location you control. senderZ provides the device supervisor and ops runbook; you provide the machine.
Regional data residency
Because senderZ runs on your Cloudflare account, D1, KV, and Queue regions are whatever you configure. EU-only, US-only, or region-pinned — your call.
Custom domain
Your API lives at api.yourdomain.com with Wrangler custom routes. No senderz.com in a customer-visible path.
Private networking
Available on requestCloudflare Tunnel from your on-premise iMessage host into your Cloudflare account. No public IP, no inbound port exposed.
HIPAA BAA
Available on requestsenderZ signs BAAs only for Self-Hosted deployments because only Self-Hosted gives you the data-handling posture HIPAA requires. Standard API Cloud and Workspace plans are not HIPAA-compliant.
Open-source SDK
The @senderz/sdk and @senderz/mcp packages are MIT licensed. You can vendor them, fork them, or build on them without license risk.
SIEM integration
Planned — Q4 2026Forward security events (auth failures, admin actions, key revocations) to your Splunk, Datadog, or Sumo Logic instance.
Source escrow
Planned — Q2 2027Third-party source escrow arrangement so you retain the right to continue operating if senderZ exits the market.
How you use it
Four phases. Two-to-six weeks.
Most engagements run on a 2–6 week timeline depending on compliance scope and Apple-hardware lead times.
Phase 01
Scoping
We meet with your infrastructure and compliance teams. You share your residency requirements, HIPAA needs, expected volume, and SLA targets.
Phase 02
Provisioning
You provision a Cloudflare account with D1, Workers, Queues, KV, and Pages enabled. You buy or dedicate Apple hardware for the iMessage bridge.
Phase 03
Deployment
We deploy the three senderZ workers (api, router, billing), configure secrets, set up the Cloudflare Tunnel from your Apple hardware, and run through the pre-live checklist.
Phase 04
Operation
You use the same SDK, MCP server, and portal as API Cloud customers, pointed at your own api.yourdomain.com. senderZ holds a retainer for ongoing operations, upgrades, and on-call support.
How it compares
Same product. Different boundary.
Self-Hosted compared to API Cloud — the same product with different boundaries of ownership.
| Feature | Self-Hosted | API Cloud |
|---|---|---|
| Infrastructure ownership | Your Cloudflare account | senderZ Cloudflare account |
| Data residency control | Full — you pick regions | Cloudflare global network |
| HIPAA BAA | Available on request | Not offered |
| Onboarding time | 2–6 weeks with operator support | Minutes (free trial) |
| Pricing model | Custom annual contract | Published per-plan pricing |
| Support model | Retainer + SLA | Plan-tier support |
| Ballpark monthly cost | From $2,000/mo for operator retainer | From $49/mo (Starter) |
Cost ranges reflect typical engagements as of April 2026 and are indicative only. Every Self-Hosted contract is custom.
Pricing
Custom annual contract.
Custom annual contracts. Operator retainer starts around $2,000/mo for a minimum-scope deployment; total cost varies with client volume, HIPAA scope, SIEM and disaster recovery requirements, and support SLA. Cloudflare infrastructure costs bill directly to your account and pass through at cost.
FAQ
Frequently asked questions
Is this truly self-hosted or managed?
Hybrid. Your Cloudflare account runs the workers and stores the data; senderZ operates the deployment under a retainer. You hold the infrastructure contract and the audit trail; we hold the operational knowledge. This is how most enterprise messaging deployments work because running a dedicated iMessage bridge from scratch takes more ops expertise than most teams want to build.
Can I air-gap the deployment?
No. The architecture requires Cloudflare Workers + D1 + Queues at the edge. A fully on-premise, air-gapped deployment is not supported because the Cloudflare platform is load-bearing.
Is HIPAA BAA available?
Yes, for Self-Hosted only. We do not sign BAAs for the shared API Cloud or Workspace products because only Self-Hosted gives you the data-access posture HIPAA requires.
What is the minimum contract length?
One year. Self-Hosted is an enterprise commitment — the operator retainer, the commercial terms, and the pace of improvements all assume you plan to stay for at least 12 months.
How is pricing structured?
Custom annual contracts combine an operator retainer (starting around $2,000/mo for a minimum-scope deployment) plus any Cloudflare infrastructure costs on your account. We do not publish fixed tiers because enterprise deployments vary materially in scope.
Can I migrate from API Cloud to Self-Hosted later?
Yes. We have done it. Phone numbers, contacts, and consent logs migrate cleanly; message history can be backfilled if needed. Plan for a 2–4 week cutover with dual-write in the middle — we'll run the migration through our Migration Concierge service.
Start with a scoping call.
Self-Hosted only makes sense when the compliance or residency story requires it. A 30-minute conversation is the fastest way to know whether it fits your use case.