01
Multi-tenant from day one
Carve one account into many. Independent billing, isolated suppression, separate approvals per sub-tenant.
Multi-tenant CPaaS · East Africa
Send, receive, and reconcile customer messages across SMS, WhatsApp, Email, and USSD — through a single console and a single API. Built for resellers, enterprise brands, and developer-led organisations.

Five channels behind one dispatcher, one billing ledger, and one audit log.
01
Carve one account into many. Independent billing, isolated suppression, separate approvals per sub-tenant.
02
Your marketing team uses the UI. Your engineers call the API. Same dispatcher, same gate, same audit log.
03
Timezone-aware sends, auto opt-out from inbound replies, maker-checker approvals on every dispatch path — API or UI.
Developers
Per-key bearer auth, scope-gated and idempotency-keyed, rate-limited per key. Endpoints for messages, batches, contacts, sender IDs, templates, surveys, suppression, and payments. Webhook fan-out on every event. Live OpenAPI docs.
{
"channel": "sms",
"sender_id": "OMNIHUB",
"to": ["+254700000000"],
"body": "Your order {{order_no}} is ready.",
"schedule_at": "2026-08-15T09:00:00+03:00"
}Carving one platform credential into N tenant accounts.
With existing BSP relationships, needing an orchestration + compliance layer.
That want operator-controlled dispatch with full audit, not a no-code drag-and-drop.
That need a first-class REST API with OpenAPI docs, webhooks, and idempotency.
Built for the market
Optimised for Safaricom, Airtel, Telkom, Equitel routing. M-Pesa-native billing. Sender ID registration and short-code workflows tuned to local carrier processes.
Contact the OmniHub team for tenant onboarding, API credentials, and a guided walkthrough of the console.