What is RapidPro?

What does RapidPro actually do?

A team designs a flow: send a question, interpret a reply, branch on the answer, save a result, or hand the person to another step. Contacts can be grouped, journeys can be triggered or scheduled, and results can be used by other systems through an API. These are the building blocks for registration, reminders, surveys and conversational support, not just a fixed menu of chatbot replies. RapidPro's project overview describes the core features.

Why self-host RapidPro?

With many SaaS messaging products, the vendor operates the application and database. You work through the access, exports, hosting regions and price structure it offers. That convenience is valuable, but it can become a constraint when a programme needs deeper troubleshooting, a particular hosting location or a different commercial model.

Full access to code and database

RapidPro can instead be deployed on infrastructure controlled by your organisation or a specialist operator. The application source is available to inspect in the older AGPL repository and the newer Temba upstream. The authorised operator has direct access to the deployed code, PostgreSQL database and surrounding services. That makes it possible to investigate a failed message beyond a dashboard, build agreed integrations and exports, and plan an exit without depending solely on a vendor's interface. Client access to production systems should still be governed by security roles and the service agreement.

Choose where the core system runs

You can select the region for the RapidPro application and primary database, and specify how backups and operator access are handled. This can support a programme's jurisdiction and governance requirements, but it is not a claim that all data stays in that region: WhatsApp, SMS gateways, AI services and other providers may process information elsewhere. Those boundaries still need to be mapped and contracted.

See the full cost picture

A self-hosted deployment has infrastructure, operations, support and any applicable software-licence costs, plus channel charges. It is not automatically cheaper than SaaS. The benefit is that you can examine those components, size the system for your programme and compare them with a hosted provider's subscription, usage charges and exit terms. The relevant question is total cost and control over several years, not whether the code has a price tag.

Why do multiple channels matter?

An NGO may reach one group reliably by SMS, while another prefers WhatsApp. A community using Telegram may make sense for a different service. The best route depends on access, consent, language, message format and the job the conversation needs to do. Committing the whole programme to one channel makes a later change harder.

RapidPro models channels as connections for sending and receiving messages, and an organisation can configure more than one. Its contact model can also hold different addresses for the same person. That gives a programme a common place to manage contacts and journeys while using different delivery routes. See the official channels and contacts documentation.

That does not mean every flow can simply be copied between channels. SMS has short text and different delivery constraints; WhatsApp has interactive formats and platform rules; Telegram requires its own bot and audience. Channel-specific prompts, routing and testing remain part of a sound implementation. Moving a participant between channels also requires a reliable way to match identities and honour their consent.

What might a multi-channel programme look like?

Consider a learning programme enrolling educators. A short SMS can reach someone with limited data access. A richer WhatsApp journey can deliver resources and collect feedback. A Telegram channel could serve a group already using that app. RapidPro can hold the programme logic and outcomes in one operational system, while the team designs the right experience and provider connection for each route.

This is an example architecture, not a promise that participants automatically switch between channels or that all channel features are interchangeable. The team still decides which channel is appropriate for each message, what happens when delivery fails, and how replies are attributed to the right contact.

What does it take to run?

RapidPro is software, not a complete messaging service on its own. You need a hosted RapidPro instance, connected channel accounts or gateways, monitoring, backups and people responsible for incidents and upgrades. Its hosting documentation is explicit that production operation has several components and should be handled by an experienced operator.

AGPL or BSL: which release can you use?

RapidPro has two relevant licensing paths. An older AGPL-licensed release offers an open-source route. More recent releases in the Temba upstream use the Business Source License (BSL), which is not an open-source licence and restricts use as a commercial hosted messaging platform without a separate licence. BotFlow Host can provide either an AGPL-based deployment or a newer BSL-licensed deployment for eligible nonprofit organisations under an agreement with the upstream developers. We will identify the exact release, licence, source-access rights and upgrade path in each proposal rather than treating the two options as interchangeable. Hosting, support, WhatsApp platform charges, SMS transport fees and other provider costs remain separate.

When is RapidPro a good fit?

• You already use, or expect to use, more than one messaging channel.
• You need direct access to the deployed code, database and operational evidence rather than dashboard-only access.
• You want a defined hosting jurisdiction for your core system and a clear map of third-party data flows.
• You need to own your programme's workflows and data model over several years.
• You have a real plan for operating the infrastructure, whether in-house or with a specialist.
• You are willing to design and test the experience separately for each channel.

If you need one simple campaign on one channel and have no capacity to operate a platform, a hosted tool may be quicker to launch. The right decision comes from your audience, governance needs and operating model, not a feature count.

Where BotFlow Host fits

BotFlow Host provides managed, single-tenant RapidPro infrastructure for organisations that want the control of a dedicated deployment without operating it alone. We take responsibility for the infrastructure lifecycle while your team retains ownership of programme logic and content. Together we can define the hosting region, access model, data and backup boundaries, and channels that fit the people you need to reach.