Does self-hosted Rallly cost less than Doodle?
It depends on how many people vote in your instance, how many years you keep it running, and who operates it. Doodle charges per seat: its Pro plan is USD 11 and Team is USD 16 per seat per month billed annually, and Enterprise starts at USD 15k. Rallly is free for personal use with one user, and multi-user instances buy a license key: Plus covers up to 5 users at $49, Organization covers up to 50 users at $499, and Enterprise covers 50 or more users from $999 by quote. For a team of a few people, the one-time key price can be far below a year of per-seat Doodle fees, but for a large group the gap narrows and the license is only one line.
Rallly keys are perpetual for the v4.x versions, so the license cost does not recur within that major line. Confirm with Rallly before you buy whether a move to a later major version requires a new key, and check the honor system terms in the Rallly licensing documentation. The instance also keeps working past its user limit with an upgrade reminder, which is a licensing agreement you should record in your own policy rather than a technical control. Guest voters without accounts are not counted, which changes the user count you actually need to license.
The subscription line is only one of several costs on the self-hosted side. You pay for a server or cloud instance, a PostgreSQL database, outbound email delivery, and staff time for upgrades, backups and patching, including security releases such as v4.15.5. Support is also yours unless you buy it separately, so ask whether an internal team or a partner will answer when the instance fails. Get written quotes for each of these items, then compare the three-year total with Doodle's per-seat invoices for the same number of users, not only the first-year figure.
Which cost components change when you move from Doodle to Rallly
This table sets Doodle's per-seat subscription and Enterprise minimum against the components of a self-hosted Rallly instance: license key, compute, PostgreSQL, email, and the people who install, upgrade and support it. Read each row for who is paid, whether the cost is one-time or recurring, and what drives it up. The main takeaway is that Rallly moves most spend from a seat count to infrastructure and internal or contracted operations time.
| Cost component | Commercial side (Doodle) | Self-hosted side (Rallly) | One-time or recurring |
|---|---|---|---|
| Subscription or license | Per-seat Pro and Team plans billed per seat per month on annual billing, or Enterprise starting at USD 15k with SSO | Free for personal use with 1 user; multi-user instances buy a license key (Plus, Organization or Enterprise tier by user count) | Doodle recurring; Rallly keys are one-time and perpetual for v4.x |
| Server hosting | None for the organizer; Doodle runs the service | Cloud or on-premises compute for the Rallly container, sized to your user count and traffic; you pay the provider or your data center | Recurring |
| PostgreSQL database | Included in the hosted service | Self-run PostgreSQL or a managed database service, including backups and patching of the database | Recurring |
| Email delivery | Included in the hosted service | A transactional email provider or your own SMTP relay for poll invitations and notifications, which is usually a separate recurring charge | Recurring |
| Implementation and setup | Account setup only | Initial deployment, domain, TLS, SSO decisions and license activation; done in house or under a fixed-scope written agreement | One-time |
| Migration of existing polls | Excel export of group poll data is available on Pro, Team and Enterprise plans | Time to export poll history, recreate Spaces and tell participants about new links | One-time |
| Upgrades and security releases | Handled by Doodle | Your team applies releases such as v4.15.5, which upgrades Next.js to 16.4.2, and tests them before rollout | Recurring |
| Support and internal skills | Doodle vendor support tied to the plan | Staff or a retained partner for operations, incident response and troubleshooting; confirm what the license covers with Rallly support | Recurring |
How Rallly license keys change the subscription math
Rallly's cost model is closer to a one-time purchase per tier than a recurring per-seat charge. Self-hosting is free for personal use with one user. Once more people use the instance, the organization is asked to buy a license key: Plus covers up to 5 users at $49, Organization covers up to 50 users at $499, and Enterprise covers 50 or more users from $999 by quote, according to the Rallly licensing documentation. Keys are perpetual for the v4.x versions, so the spend does not recur each year within that line. Compare that with Doodle's per-seat monthly rates on the same headcount, and the difference grows with every seat you add.
The honor system matters more than the price table. An instance keeps running past its user limit and shows an upgrade reminder, so nothing breaks when headcount drifts above the tier. Treat that as a compliance question, not a technical one: the license obligates you to buy the right tier, and an auditor or board will expect the count to be accurate. Guest voters who respond without registering are not counted, which keeps large invitee lists from pushing you up a tier. Activation needs the server to reach licensing.rallly.co over HTTPS, so confirm that outbound rule with your network team before go-live, and plan how an air-gapped or egress-restricted environment will activate.
When the user count crosses a tier boundary, the cost jumps to the next one-time key rather than rising smoothly, so model your headcount against the 5 and 50 thresholds before you buy. Ask Rallly support whether a key bought for one tier can be upgraded and what the price difference is, because that figure is not in the facts supplied here. Non-profit organizations can request a discount through the Rallly support channel, so ask before purchase and get the outcome in writing. Finally, budget for the components the key does not cover: the server, PostgreSQL, outbound email and the staff time for upgrades.
What moves the comparison most
The gap between Doodle's per-seat pricing and a self-hosted Rallly instance depends less on the software than on a handful of inputs. User count sets the Rallly tier, seat growth drives the Doodle bill, and the operating burden of hosting is what you carry yourself. Work through these drivers with real numbers from your own organization before comparing totals, because each one can move the answer in a different direction.
User count against tier boundaries
Rallly's license is priced by the number of users on a multi-user instance, with Plus covering up to 5 users, Organization up to 50, and Enterprise from 50 or more by quote. Count the people who will actually create polls or sign in, not everyone who votes, because guest voters without registration do not count toward the limit. If your headcount sits just above a boundary, the next tier's cost can outweigh the savings, so model both sides of the line. Confirm the current user definition with Rallly before you buy.
Doodle seat growth
Doodle bills per seat per month on its Pro and Team plans, so every new scheduler adds a recurring line item. A Rallly license key is a one-time purchase for v4.x, which means its cost does not rise with each hire in the same way. Growth is therefore the main reason the comparison shifts over time. Ask Doodle for the seat count and billing terms in writing, and project the seat count for the next three years.
Spaces needed for shared polls
Rallly Spaces are shared workspaces where members create and manage polls together, and each tier caps members per Space at 5, 50 or 100. Map your teams to Spaces before you choose a tier, since one large department may need a higher cap than the total headcount suggests. Splitting the organization into several small Spaces can keep you on a lower tier, but it may fragment who can see which polls. Check how Spaces handle membership changes when people move teams.
Email volume and delivery setup
Rallly sends notifications for new votes, comments and finalized dates, so poll activity drives mail volume. Self-hosting means you own an SMTP relay, its sending reputation, SPF, DKIM and DMARC records, and bounce handling. Doodle handles delivery as part of the service. Estimate outgoing messages per month from your typical poll count, and budget for a transactional mail provider or internal relay if your own mail servers are unsuitable.
Availability and backup windows
A self-hosted instance is only as available as the server, the database and the network path to licensing.rallly.co, which must be reachable over HTTPS to activate keys. Decide how long a poll outage or failed restore can be tolerated during a scheduling peak, and whether that needs redundancy or a tested recovery procedure. Doodle's uptime is contractual only if your agreement says so, so ask for the terms in writing and compare them with the window your own team needs.
In-house operator capacity
Someone must run Docker, PostgreSQL, TLS certificates, patching and Rallly upgrades, including security releases such as v4.15.5, which upgraded Next.js to 16.4.2. If an existing platform or infrastructure team already operates these components, the marginal effort is small. If nobody does, the work either becomes a retainer with an implementation partner or a new recurring internal duty. Price that operator time honestly, since it is the cost most often left out of self-hosting comparisons.
How to build the cost model with your own numbers
This sequence turns Doodle's invoices and your user counts into a side-by-side model in which both options carry the same assumptions. The output is a multi-year total you can defend to finance and procurement.
Pull current Doodle seats and plan from invoices
The finance or procurement owner exports the last several Doodle invoices and records the plan name, the number of paid seats, the billing cycle and any add-ons. Doodle lists Pro at USD 11 and Team at USD 16 per seat per month billed annually, and Enterprise starting at USD 15k with SSO, so confirm which of these your contract matches. The step is done when you have one annual Doodle figure that reconciles to the invoices.
Map active organizers and participants
The scheduling admin counts people who create polls each year and separately counts the invitees who vote. Rallly's license tiers count registered users, and unregistered guest voters are not counted, so split the two groups clearly. The step is done when you have a registered user count and a note on how many outside participants vote as guests.
Select the Rallly tier by registered users
Using the registered count from the previous step, choose the tier from Rallly's licensing documentation: free personal use for 1 user, Plus for up to 5 users at $49, Organization for up to 50 users at $499, and Enterprise for 50 or more users from $999 by quote. Keys are perpetual for v4.x, so record the one-time amount separately from any recurring hosting cost. The step is done when the tier and its one-time price sit in your model.
Estimate hosting, PostgreSQL, email and backup
The infrastructure owner prices a small application server, a PostgreSQL database, outbound email delivery and backup storage using your own cloud or data center price lists, since no supplied figure covers these. Ask whether the compute, database and backup costs already sit in an existing platform budget, because that changes the incremental cost. The step is done when each component has a monthly figure from a named price list.
Price implementation and migration from a written scope
Request written quotes from implementation partners, including DeployOpen, based on a fixed scope that covers installation, SMTP configuration, Spaces setup, data handling and the move of regular participants to new links. DeployOpen does not publish prices, so the quote follows from the written scope. The step is done when you hold a one-time figure tied to named deliverables.
Set an annual upkeep line for upgrades
Budget recurring effort for upgrades and security releases, such as the v4.15.5 release published on October 18, 2026, which upgraded Next.js to 16.4.2. Decide whether your team applies these in-house or retains a partner, and ask any partner whether upgrades and testing are included or billed separately. The step is done when you have an annual line for upkeep with a stated owner.
Compare totals over a fixed period with equal assumptions
Choose one comparison period in years and apply identical user growth, price escalation and staffing assumptions to Doodle and Rallly. Show the one-time costs and recurring costs in separate rows so the break-even point is visible. Label any scenario that uses hypothetical user growth as illustrative. The step is done when both columns total over the same period and the assumptions are written next to the numbers.
Which costs are one-time and which recur each year
The main split is simple: the Rallly license key is largely a one-time purchase for a given tier, while almost everything that keeps the instance working is recurring. Rallly's licensing documentation describes its v4.x keys as perpetual, so the Plus, Organization or Enterprise fee is paid once for that tier. The one-time work is the initial deployment: standing up the Docker image, connecting PostgreSQL, configuring email and setting up single sign-on if you need it. Ask whoever quotes that work to name it as a separate line, so it does not get mixed into the run cost.
The recurring costs are the ones Doodle's fees hide inside its subscription. They include the server or cloud account that hosts Rallly, the operation of PostgreSQL (backups, restore tests and version upgrades), the transactional email service that delivers invitations and notifications, security patching, and upgrade testing. The v4.15.5 security release, which upgraded Next.js to 16.4.2, is a concrete example of the patching work that repeats. Doodle's Pro and Team fees are charged per seat every year, so they grow with headcount. Its Enterprise tier carries a starting price of USD 15k, which recurs annually and is set by a sales conversation. Confirm the current figure on Doodle's premium page before you compare.
Growth changes the license cost in steps rather than gradually. A Rallly key covers a tier, so moving from Plus, which covers up to 5 users, to Organization, which covers up to 50 users, is a new purchase at the higher tier. Plan for that step when you forecast, and ask your team how many people will create polls in the next two renewal cycles. Confirm with Rallly whether a tier change requires a new key or an upgrade path, and whether the honor-system limit gives you time to act.
Questions buyers ask about Rallly running costs
How much ongoing effort does a self-hosted Rallly instance need?
Ongoing effort depends mostly on how often you apply upgrades and how much monitoring you already run. Rallly ships as a Docker image, so the routine work is pulling new versions, running database migrations, keeping the host patched, and checking backups. Security releases matter here: v4.15.5, published on October 18, 2026, was a security release that upgraded Next.js to 16.4.2, so plan a fast path for applying such updates. Your team also owns TLS certificates, the reverse proxy, outbound email and PostgreSQL maintenance. Ask DeployOpen or your internal platform team to estimate these recurring tasks against your own change calendar and on-call model, because the workload varies with your hosting setup.
How long does a migration from Doodle to Rallly take?
The duration depends on the number of polls you need to carry over, how many users will sign in to Spaces, the state of your existing infrastructure, and how much email and identity work is needed. Exporting poll history from Doodle, provisioning the server and database, configuring email delivery, and choosing a license tier are separate tasks, and each can add time. No researched figure for migration duration is available here, so ask for a written timeline against a defined scope before work begins. Most engagements are fixed-scope, with scope, deliverables and timelines agreed in writing first.
Can a small team run Rallly without outside help?
A team with working experience in Docker, PostgreSQL, reverse proxies and transactional email can usually run a single instance internally, provided someone owns upgrades and backups. Teams without that experience, or without a clear owner for security patches, often choose outside help for setup and handover. Whichever route you take, confirm who will apply Rallly security releases within your own change window, who restores the database if it fails, and who answers when participants stop receiving invitations. DeployOpen offers implementation, hardening, backup, upgrade and documentation work, plus ongoing support and upgrades as retainers.
What skills and time does the internal team need to give?
Your staff need access to a Linux host or container platform, the ability to manage DNS and certificates, a PostgreSQL administrator or someone comfortable with database backups, and a mail administrator who can configure SMTP or an equivalent sending service. Rallly needs the server to reach licensing.rallly.co over HTTPS to activate a paid key, so network egress rules must allow that. Expect a named technical owner and a backup owner, plus periodic time for reviewing release notes. The exact hours depend on your environment, identity setup and monitoring, so have your platform lead size them before committing.
Does a Rallly license key cover guest voters who have no account?
Yes, paid keys do not count unregistered guest voters toward the user limit. Participants can vote on a poll without an account, and those guests are not counted. The count applies to registered users on the instance, such as organizers and members who sign in. Before you choose a tier, list how many people will hold accounts, including those who will use Spaces to create and manage polls together. Plus covers up to 5 users, Organization up to 50, and Enterprise 50 or more by quote, so accurate counting of account holders determines the cost.
What happens if our instance goes over its user limit?
Rallly license keys work on an honor system. An instance keeps running past its user limit and shows an upgrade reminder, so the software does not stop working. That behavior does not make the license optional, because the keys are how multi-user self-hosting is meant to be paid for. Keys are perpetual for the v4.x versions, so the one-time cost does not recur for those releases. Review your user count each quarter, and confirm with Rallly's licensing documentation how future major versions will be handled before you plan a multi-year budget.
Is there a non-profit discount for Rallly licenses?
Rallly offers non-profit discounts on request through its support channel. Ask before purchasing, state your organization type and user count, and request the discount in writing so the terms are on record. The discount amount is not stated in the supplied material, so confirm it directly with Rallly. Non-profits should also confirm which tier their user count falls into, since the discount would apply to the tier you select.
When staying on Doodle is the lower-cost option
Doodle stays the cheaper choice for a small team that only schedules occasionally. Doodle's Free plan includes one booking page, and the researched pricing shows Pro at USD 11 and Team at USD 16 per seat per month billed annually. If a handful of people need a group poll a few times a year, a free account with no hosting, no PostgreSQL and no email relay to maintain may cost less in staff time than any self-hosted option. Check the Free plan limits against your real poll volume and recipient count on the Doodle premium plans page before you assume the free tier is enough.
The second case is feature need. Rallly covers date and time polls, anonymous voting, the availability grid, comments and finalizing a date. It does not replace Doodle's booking pages, sign-up sheets or video integrations. If your scheduling depends on those, a Rallly migration leaves you running two tools, which removes the savings. The sibling pages on Doodle vs Rallly and Doodle vs Cal.diy for booking pages list the gaps in detail. Use them to tally which Doodle features your staff actually use each month.
The third case is that nobody on your side can run the service. A self-hosted Rallly instance needs a server, a PostgreSQL database, outbound email, certificate renewal, and an upgrade path for releases such as the v4.15.5 security release. Rallly's license keys for v4.x are perpetual, but the instance still needs to reach licensing.rallly.co over HTTPS to activate, and someone must apply upgrades. If no team can own that work, or a fixed-scope deployment and support retainer costs more than your Doodle seats, staying on Doodle is the rational decision. Confirm the number of users first, since Rallly's personal use tier covers only one user.
How DeployOpen scopes a fixed-price Rallly implementation
DeployOpen is a Chainscore Labs company that plans, implements, hardens, backs up and supports self-hosted open-source platforms inside the client's own infrastructure. For a Doodle replacement, we agree the scope in writing first, then build and hand over a Rallly instance that your team can run.
How we scope
- Count the users who will organize polls and the participants who vote, since license tiers depend on user count.
- Confirm where the instance will run, which cloud account or data center, and whether it reaches licensing.rallly.co over HTTPS.
- Agree the scope, deliverables and timeline in writing before work starts, with no fee figures drawn from this page.
How we build
- Deploy the Rallly Docker image with PostgreSQL, email delivery and TLS configured inside your own network.
- Test poll creation, anonymous voting, the availability grid, comments, notifications and finalizing a chosen date end to end.
- Check Spaces membership limits against your team structure and configure access for existing organizers before go-live.
How we hand over
- Document the installation, configuration keys, backup routine and the upgrade steps for future v4.x releases.
- Provide a runbook that explains license key activation and what happens when user counts pass the purchased tier.
- Walk your administrators through restores and export your existing poll history as agreed in the written scope.
How we support
- Ongoing support, upgrades and continuous testing are available as a retainer that follows the initial fixed-scope delivery.
- Scope security patch handling, such as the v4.15.5 Next.js update, so your team knows who applies it and when.
- Ask any provider, including DeployOpen, which party owns the instance, the license key and the upgrade calendar after handover.
