Managed RapidPro infrastructure — single-tenant, operated for you, and resilient across WhatsApp, SMS, Telegram, and web.
BotFlow Host runs and owns the operational lifecycle of your RapidPro deployment — monitoring, backups, upgrades, recovery, and controlled AI integrations — so your team can focus on the programme, not the plumbing.
From 1 October 2026, Meta will begin charging for outbound WhatsApp service messages that were previously free inside the 24-hour customer service window. For high-volume support and chatbot flows, this creates a new recurring cost layer.
Estimate exposure from historic message volumes and flow patterns, so the new cost layer is understood before it lands.
Tighten flows to cut avoidable outbound service messages without degrading the participant experience.
Design channel portability across WhatsApp, SMS, Telegram, web, and RapidPro so delivery is never tied to one provider's pricing.
A single operational partner for the infrastructure underneath your messaging programme — not another tool to manage.
Dedicated, isolated deployment. No shared multi-tenant layer between your programme and anyone else's.
We own the operational lifecycle: monitoring, patching, encrypted backups, and tested recovery.
Delivery across WhatsApp, SMS, Telegram, and web — so a single channel or provider is never a single point of failure.
Approved LLM, RAG, and decision-engine calls with logging, fallback logic, and operational oversight.
RapidPro is the concrete orchestration layer. BotFlow Host is the operator and governance layer around it.
Where the boundary sits: you own the programme logic and content. We own the infrastructure it runs on — its availability, integrity, and the controlled pathways in and out of it.
A clear boundary keeps the engagement honest and the infrastructure focused.
Practical, vendor-honest writing for teams weighing their messaging infrastructure. New guides are in progress.
Governance, cost, and operational ownership compared for teams running production WhatsApp flows.
Read the guideSelf-hosted RapidPro versus Landbot's per-seat SaaS costs — where owning the stack pays off.
Read the guideA practical playbook for modelling exposure and planning channel resilience ahead of October 2026.
Request a pricing impact reviewMessaging, cloud-provider, and optional AI-service costs are separate where applicable.
Smaller or special-case deployments can be scoped where there is a structural fit — for example client-owned infrastructure or older open-source RapidPro releases.
Pricing reflects operational ownership: monitoring, backups, upgrades, and recovery are included, not billed as incidents.
Share a little about your programme and we'll come back with an honest read on your exposure to the October 2026 WhatsApp changes — and the options worth considering.
BotFlow Host can help you understand the operational and cost implications, then design a reliable path forward.