Own vs Rent: Data Sovereignty & Donation Platforms

This is written for the CTO, CIO, or VP of Technology who inherited a donation platform and now has to decide whether to renew it. Most organizations should rent. The sections below set out where that stops being true, and what owning actually requires of the organizations that cross the line.

When Does Renting a Donation Platform Stop Making Sense?

Renting stops making sense at the point where the platform fee exceeds what running the platform would cost, and that crossover is arithmetic your finance team can do this week. Hosted donation platforms commonly charge a platform fee as a percentage of funds raised, separate from payment processing. That model is well matched to organizations early in their growth, because cost stays proportional to results and there is no infrastructure to staff.

The model changes character at scale, because a percentage fee tracks fundraising success rather than the cost of serving the account. Run the numbers with your own figures. At a 2% platform fee, an organization processing $10 million a year is paying $200,000 annually for the platform layer before processing costs; at $50 million, $1 million. Those figures are illustrative rather than a market benchmark, and the point is the shape of the curve rather than any particular rate.

Three other conditions push organizations across the same line, independent of volume. Donor data that has to reside in a jurisdiction you select rather than one the vendor offers. Campaign requirements that outrun a shared roadmap, which is common for federated organizations running many markets at once. And integration depth that a published API surface does not reach.

What Actually Differs Between Renting and Owning?

The differences cluster in six areas, and hosted platforms hold genuine advantages in two of them. Speed to a first live campaign favors a hosted product, sometimes by months, because there is no implementation project. Operational responsibility also favors it, since hosting, patching, and uptime belong to the vendor rather than to your team.

Hosted vs. Owned Donation Platform: The Six Trades

Read the table as a set of trades rather than a scorecard. Every row that moves control toward your organization also moves responsibility there. That exchange is worth making at a certain scale and clearly not worth making below it.

What Does Data Sovereignty Actually Give a Nonprofit?

Data sovereignty means your organization determines where donor data is stored, which parties process it, how long it is retained, and how it leaves. It is a set of decisions rather than a feature, and owning the platform is what moves those decisions from the vendor's side of the boundary to yours.

In practice it shows up in three places. Residency, where the region holding donor data is something you select and can evidence to a regulator. Retention, where deletion schedules follow your policy rather than the vendor's defaults. And integration, where connecting to your CRM, marketing stack, and BI tools is an engineering decision rather than a support request.

How Does AI Change the Sovereignty Question?

AI turns sovereignty into a live question rather than a settled one, because every AI feature added to a donation platform is a decision about which model provider processes your content. On a hosted platform that decision generally arrives already made. On an owned platform it stays yours: which providers, what data reaches them, whether a private option handles sensitive workloads, and where the request logs go.

What Does Owning a Donation Platform Actually Require?

Owning a platform removes the license fee and adds four standing obligations, and an evaluation that skips them will produce the wrong answer. Open source means no vendor charges you for the software. It does not mean the platform runs itself.

1. Security maintenance on a cadence. Core and contributed module security releases need to be applied promptly rather than quarterly, which requires someone accountable for the queue.
2. Major version upgrades. Drupal moves forward on a published release cycle, and staying on a supported major version is planned work rather than an emergency. The near-term marker is concrete: Drupal 10 reaches end of life on 9 December 2026, in the same release window as Drupal 12.
3. Hosting and uptime. Infrastructure, scaling for campaign peaks, backups, and failover become your responsibility, held internally or contracted to a managed services partner.
4. Capability, internal or contracted. Either a team that knows the platform or a partner retained to keep it healthy. Organizations that own a platform without funding this are the ones who end up wishing they had rented.

Vardot's position: most nonprofits should rent, and the sector would be better served if more vendors said so plainly. Ownership earns its keep in a specific band: enterprise fundraising operations running multiple markets, at volumes where percentage fees have become a budget line rather than a rounding error, with governance requirements a shared platform cannot evidence. Below that band, the operational obligations above outweigh the control they buy. The useful question is not which model is better in principle, but which side of the threshold your organization is on this year.

Which Questions Should You Answer Before Deciding?

Answer these five before the renewal conversation rather than during it. Each has a number or a document behind it, which keeps the decision out of the realm of preference.

Question two is the one most often skipped and most often decisive. Workaround time is real cost, and it rarely appears in a platform comparison because no invoice records it. Our note on common mistakes in donation platform selection covers where those costs tend to hide.

How Do You Move Without Disrupting Live Fundraising?

Move in four stages with campaigns running throughout, which is how these transitions avoid a fundraising gap. The sequence follows the Vardot Delivery System, our four-phase implementation method, which begins with alignment on scope and measurement rather than with a build.

1. Discover and plan. Map markets, currencies, payment methods, integrations, and the measurement plan before any configuration begins.
2. Configure and brand. Layouts, content blocks, donation forms, thank-you pages, permissions, and SEO defaults.
3. Integrate and validate. Payment gateways, CRM sync, tracking, and end-to-end testing against real transaction scenarios.
4. Enable and launch. Team training, initial campaigns, then iteration against performance signals.

Duration depends on market count, currency and language coverage, and integration depth, and it is scoped during Discover rather than quoted in advance. A single-market build and a federated rollout across dozens of markets are different projects on the same sequence.

Vardot builds enterprise donation infrastructure on Drupal as a Drupal Diamond Certified Partner, with 200+ platforms launched, a 4.9/5 Clutch rating across verified reviews, standing among the top 20 Drupal contributors worldwide, and Gold Sponsorship of the Drupal AI Initiative.

What Should You Decide Next?

Do the arithmetic before the renewal date, because a platform decision made under contract pressure is a platform decision made badly. Annual platform fees plus workaround time, against annual cost to own including maintenance and capability. One of those numbers is larger, and it will keep moving in the same direction for as long as your fundraising grows.

If renting still wins, renew with confidence and revisit the calculation next year. If owning wins, the work is a planned transition rather than a rescue, and it is worth starting while the current platform is still serving you well.