BotFlow Host sets up and runs your dedicated RapidPro platform. We handle monitoring, backups, upgrades and recovery, so your team can focus on reaching people and delivering your programme.
We’ve been running RapidPro for mission-driven organisations for seven years.
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.
Plan journeys across connected channels such as WhatsApp, SMS, and Telegram, with each route designed for its audience and provider.
Approved LLM, RAG, and decision-engine calls with logging, fallback logic, and operational oversight.
Since 1 October 2026, Meta charges for delivered outbound service messages after the first 1,000 per business phone number each month. Service messages remain free beyond that tier for eligible government and nonprofit organisations through 31 December 2027; eligibility must be confirmed for each account. For other high-volume chatbot flows, this can create a recurring cost layer. Check Meta's current pricing rules.
Estimate exposure from historic volumes, the free tier, and your account's eligibility before changing a working flow.
Tighten flows to cut avoidable outbound service messages without degrading the participant experience.
Design channel options across WhatsApp, SMS, and Telegram so delivery plans are not tied to one provider's pricing. Explore the channel guide.
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 and channel options.
Multi-channel chatbots and journeys with control over the code, database and hosting region.
Read the guideAssess the October service-message fees, audience reach and the work involved in a phased channel move.
Read the guideGovernance, cost, and operational ownership compared for teams running production WhatsApp flows.
Read the guideCompare self-hosted operations with Landbot's plans, usage charges and channel options.
Read the guideTrace failed AI-assisted conversations across flows, integrations and infrastructure. Understand RapidPro licences, access rights and provider boundaries.
Read the guidePlan a RapidPro upgrade with exact versions, licence checks, flow and channel tests, recovery evidence and clear go/no-go criteria.
Read the guideMessaging, 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 AGPL-licensed RapidPro releases.
Pricing reflects operational ownership: monitoring, backups, upgrades, and recovery are included, not billed as incidents.
Tell us about your programme, your current platform, and what you need help with — whether that’s managed RapidPro infrastructure, integrations, or a review of your messaging costs.
BotFlow Host can help you understand the operational and cost implications, then design a reliable path forward.