Latest News

RapidPro License Update: What the AGPL v3 Means for Organizations Deploying RapidPro

December 16, 2025 Comments Off on RapidPro License Update: What the AGPL v3 Means for Organizations Deploying RapidPro
RapidPro License Update illustrating organizations deploying RapidPro under the AGPL v3 license with secure hosting and large-scale communication systems

RapidPro License Update is a major milestone for organizations using RapidPro at scale. Starting January 1, 2026, RapidPro officially transitions to the GNU Affero General Public License (AGPL v3), introducing new open-source obligations while keeping the platform free to use for NGOs, governments, and enterprises.

RapidPro is a powerful open-source messaging platform used by NGOs, governments, and enterprises for mobile health, survey, and communication campaigns. In 2026, RapidPro’s code license is officially changing: effective January 1, 2026, RapidPro (and related components) will be governed by the GNU Affero General Public License version 3 (AGPL v3). This is a shift from more permissive licensing (like BSD) to a strong copyleft license. For decision-makers, the key takeaway is that RapidPro remains free to use but organizations must understand new open-source requirements. In practice, AGPL v3 ensures that any modifications or extensions to the RapidPro software are shared back with the community, especially when the software is run over a network.

RapidPro’s core functionality, a no-code visual workflow builder for SMS, WhatsApp, and email campaigns, is unchanged by the license update. However, the legal framework around hosting and deploying the platform is different. Below, we explain the practical impact of switching from a permissive BSD-style license to AGPL v3. In short, continued use of RapidPro is unaffected, but any customized RapidPro code that you deploy (for example, in your own servers or services) will now need to be released under AGPL v3 as well. We compare the two licenses, highlight what AGPL v3 requires, and outline the next steps for RapidPro Hosting and Deployment. The goal is to help NGOs, governments, and enterprises plan ahead without legal confusion.

AGPL v3 vs BSD: Key License Differences for RapidPro

The AGPL v3 license is a copyleft (viral) license, whereas BSD (3-clause) license is permissive. Permissive licenses like BSD simply let users “copy, modify, and redistribute software however they want”. In contrast, AGPL v3 adds a key requirement: if you modify the software and offer it as a network service, you must make the complete source code of your modified version available to users. In practical terms, for RapidPro:

  • BSD License (old model): Users could take RapidPro code, build on it, and even embed it in proprietary systems without sharing changes. You had no obligation to publish any enhancements or custom integrations publicly. This gave maximum freedom but did not guarantee contributions back to the community.
  • AGPL v3 License (new): Any organization that runs RapidPro as a service (self-hosted, on-premise, or in the cloud) and has modified its code must publish those changes to users. In other words, even if you only serve users over a network (e.g., an internal RapidPro server or a hosted SaaS), AGPL v3 says “if you host a version of RapidPro, you must make the same source code you are hosting available to others”. This closes the “SaaS loophole” that GPL had (GPL only triggers on distribution, while AGPL triggers on network use).
  • Permissions and Use: AGPL v3 still permits commercial use, modification, and distribution of RapidPro, just like BSD did. It guarantees you the same rights to use RapidPro freely, including in commercial settings. The difference lies in obligations: AGPL adds the condition of sharing modifications under the same license, whereas BSD has almost no conditions.
  • Liability and Fees: Both licenses disclaim warranty and liability. Crucially, AGPL v3 imposes no fees or royalties. Your organization will not suddenly owe license fees for RapidPro’s code. The platform’s business model (e.g., via RapidPro.app subscriptions) remains about hosting and support services, not license sales.

In summary, AGPL v3 is simply a stronger open-source license. It ensures improvements to RapidPro benefit everyone. Under AGPL, you still get rapid messaging and workflow tools, but if you enhance the software, you’ll need to contribute your code back. As one guide explains, “the AGPL v3.0… requires that when a modified version is used to provide a service over a network, the complete source code of the modified version must be made available”. By contrast, BSD allowed using or hiding such changes.

RapidPro License Update: Impact on RapidPro Hosting

For organizations using hosted RapidPro services (such as the RapidPro.app SaaS or other managed providers), the practical effect is minimal on day-to-day operations. Hosted customers continue to design surveys, send messages, and analyze data as before. The AGPL change mainly affects the providers of hosting and the underlying software distribution:

  • Standard Hosting Use: If you simply subscribe to a RapidPro hosting plan and do not alter the software code, the license update doesn’t change anything for you. You can keep using the platform normally. AGPL does not impose any obligations on end-users for their content or workflows; it only governs the software itself. Your contact lists, message content, and workflows (the “client data”) remain 100% owned and private to you.
  • Provider Code Changes: If your hosting provider has customized RapidPro (for example, adding custom connectors or features), those modifications must be available under the AGPL. In practice, reputable providers will handle this on their end. For instance, RapidPro.app already offers managed hosting and support, and as an open-source provider, they will continue releasing updates and patches under AGPL. Essentially, “RapidPro Software” is “a digital public good … under the GNU AGPL v3.0”, meaning the base platform and any provider additions remain open-source. Clients don’t have to do anything in response; the hosting provider should handle compliance.
  • Customer Obligations: If you contract with a hosting provider, check if your agreement covers intellectual property. Under AGPL, the hosted software’s source is (and should be) freely available. You generally do not need to request source code; it should be automatically accessible via the open-source project. What you should do is ensure any custom development you sponsor (like special reporting tools or integrations) is either contributed back or licensed properly. In other words, plan for any code you fund to remain open or separately licensed.
  • SaaS Bundles: If you build additional modules or proprietary software on top of a hosted RapidPro (e.g., a private analytics dashboard), remember that AGPL requires those modules also to be open-sourced if they are derivative works of RapidPro. Keep that in mind when planning new features.

Bottom line: For hosted scenarios, AGPL v3 mostly “moves the needle” on compliance work, but not on everyday use. Focus on choosing a trusted RapidPro Hosting partner (like RapidPro.app) who already operates in the open-source world. They will manage code updates and licensing. The AGPL ensures that the entire software stack remains transparent, so you’ll continue to receive timely fixes and enhancements.

RapidPro License Update: Impact on RapidPro Deployment

Many organizations deploy RapidPro on their own servers or cloud (B2G/B2B scenarios). AGPL v3 adds some new considerations for these self-hosted deployments:

  • Using Stock RapidPro: If you deploy the official RapidPro codebase “as-is” (no changes), you can keep doing so under AGPL just like under BSD. You have the right to use the software indefinitely. All AGPL requires in this case is that the software remains open source (which it is by default). You do not need to take any action if you’re just consuming the unmodified platform.
  • Custom Modifications: The major change arises if you plan to modify RapidPro itself. For example, adding new features, altering workflows at the code level, integrating with other systems via custom middleware, or developing proprietary “flavours” of RapidPro. Under the new AGPL license, any such modifications must be licensed under AGPL v3 and made available to users. Practically, if you have an internal software development team customizing RapidPro, you will need to host those code changes in a public repository (or otherwise provide source to anyone using your system). This was not required under BSD; AGPL enforces it.
  • Network Use Clause: Even if you only allow internal access (e.g., RapidPro on an intranet), the AGPL intends that any “publicly accessible” use triggers the source-sharing rule. If your RapidPro instance is behind a password for employees, this might not count as “public” in a legal sense. However, best practice is to treat it as if it were, and assume you’ll need to share modifications. In most cases, opening your code (even internally) promotes transparency and collaboration with the RapidPro community.
  • Compliance Checklist: As a decision-maker, ask: Are we modifying RapidPro’s code or its official plugins? If yes, have we reviewed those changes for license compliance? You may want your IT or legal team to audit custom repositories. It’s often simplest to contribute improvements back to the official RapidPro project, where they benefit all users. If you absolutely need a closed customization, you might consider dual-licensing (though AGPL does not allow relicensing except to a later AGPL version).
  • No Impact on Data/Workflows: It’s important to stress that AGPL v3 does not affect your data or messaging content. The license only applies to the software code. Your contacts, survey responses, and other “Client Data” remain fully under your control. You are not required to publish your surveys or business data, only any changes to the RapidPro platform itself.

Action Steps for Deployment: Inventory any internal code repositories related to RapidPro. Plan to host them publicly (e.g., on GitHub) or grant access to your users as required. Update your deployment and legal policies to reflect AGPL obligations. In most cases, this is a one-time compliance check. After that, continue using RapidPro to drive your programs. The license update should not slow your operations; it mostly formalizes what good open-source practice should already be doing.

Practical Checklist

  • Continue Using RapidPro: No license fees, no change to core features. RapidPro still offers the same secure, scalable messaging platform. If anything, AGPL v3 encourages a healthier open-source ecosystem around RapidPro.
  • Sharing Code: If you have developed new RapidPro features or integrations, prepare to share them. AGPL v3 explicitly expects you to “provide the source code of the modified version running on [a networked] server”.
  • Seek Expertise: With the license change ahead, consider consulting with open-source software experts or legal counsel (especially for large deployments). RapidPro.app support or consultants can help explain how AGPL applies to your scenario without jargon.
  • Benefit from Community: AGPL v3 often means a more vibrant community. As more organizations share their enhancements, you gain from improvements you didn’t have to build. Think of AGPL as a safeguard for collaboration.
  • RapidPro Hosting Options: Whether you stick with managed hosting or self-host, remember that the platform’s capabilities remain top-notch. RapidPro.app’s features (flows, channels, campaigns, security) are unchanged, and now they come with the confidence that the code base is legally robust and community-backed.

In every case, RapidPro’s value proposition stands strong: an enterprise-ready, no-code solution for interactive messaging. The license update does not alter RapidPro’s feature set or support levels, only how its source code is governed. For personalized advice on deployment and compliance, Talk to RapidPro Experts or email us at info@rapidpro.app. We can walk you through any questions and ensure your organization meets the new requirements smoothly.

Conclusion

The shift to AGPL v3 marks a clear stance by RapidPro’s stewards: the platform’s future belongs to the open-source community. This empowers organizations to use, modify, and extend RapidPro with confidence that the core software will remain free and supported for years to come. For organizations deploying RapidPro, the transition is largely transparent, you still get all of RapidPro’s innovation (visual flows, multi-channel support, analytics, etc.) without new costs. The practical change is simply that any code changes you make must be shared under the same license. In turn, you benefit from any enhancements others share.

By taking a few straightforward steps now (review custom code, plan for compliance, consult experts), your deployment of RapidPro can continue uninterrupted. The AGPL v3 license update ultimately reinforces RapidPro’s mission as a digital public good, ensuring that improvements circulate back into the community. RapidPro remains a world-class platform, and with the correct preparation, organizations can leverage its power while staying fully compliant.

For more information or to discuss the best deployment approach, Talk to RapidPro Experts. Let us help you harness RapidPro for your communication goals with confidence and clarity.

FAQ

Q: What is changing with the RapidPro License Update (AGPL v3), and when does it take effect?
A: RapidPro’s source code license is switching from a permissive BSD-style license to GNU AGPL v3 as of January 1, 2026. This means the platform’s software is still free and open-source, but now any modified code you deploy (especially in a networked environment) must be released publicly. Your use of RapidPro is still royalty-free, and you can continue running it without license fees.

Q: How does AGPL v3 differ from the previous BSD license for RapidPro?
A: The key difference is in sharing obligations. Under BSD, you could keep changes private or even close-source. AGPL v3 is copyleft, requiring that if you run a modified version of RapidPro over a network, you share that source code with users. In essence, BSD is “use it however you like”, whereas AGPL v3 insists on “use it freely, but share your improvements”.

Q: What does this mean for RapidPro Hosting and managed services?
A: If you use a hosted RapidPro solution (such as RapidPro.app), the update has minimal impact on your day-to-day operations. The host provider will comply by keeping the software open-source. Your data and workflows remain private, and you continue accessing the same features. You don’t need to publish anything as an end-user, only if the hosting setup itself is modified (in which case the provider must share their changes). In short, RapidPro Hosting simply continues under a clear open-source license.

Q: What if we self-host RapidPro or deploy it on-premise?
A: Self-hosters should continue using RapidPro normally. The main new step is to review any custom code or integrations you’ve built. If you have made changes to the RapidPro software itself, AGPL v3 requires that you make those changes available to users (for example, by publishing to a public repository). If you have not modified the code, you have no new obligations. Remember that AGPL covers the software code, not your organization’s data; your user data stays yours.