Skip to main content

Fully Managed Rallly
as a Service

Deploy Rallly as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Rallly is an open-source group-scheduling tool — meeting polls, time-slot selection, and calendar invites — combining the convenience of Doodle with the security and control of self-hosted infrastructure.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

Rallly

Rallly

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Rallly Preview Image

ABOUT THE SOFTWARE

What is Rallly

Rallly is an open-source group-scheduling tool for finding meeting times that work for everyone. Participants vote on candidate slots; the organizer finalizes the winning option and the app issues a calendar invite. It is the self-hostable counterpart to Doodle, written by Luke Vella and released under AGPL-3.0.

Rallly is licensed under AGPL-3.0 and maintained on GitHub at github.com/lukevella/rallly. The codebase is TypeScript on a Next.js and Prisma stack against PostgreSQL, with bundled Traefik and Garage (S3-compatible) handling reverse proxy and uploads in the upstream Docker Compose stack.

On GitHub, Rallly has accumulated 5,000+ stars across 33 listed contributors and 85 releases. The hosted SaaS at app.rallly.co publicly disclosed a 45,000+ registered-user and 100,000+ poll figure in 2022, and both numbers have grown since. Public self-hosted deployments include data.coop, a democratically-run Danish association running a shared Rallly instance for its members. Project sponsors include Vercel, Sentry and Appwrite.

FEATURES

What Rallly does

Rallly handles three things end-to-end: it lets an organizer post candidate dates or time slots, it lets participants vote without creating an account, and it issues a calendar-ready invite once the winning option is chosen. Everything in between — timezone math, branding, calendar export, SSO — is configurable but works on defaults.

Account-free voting

Participants vote without registering. They enter a name and an email, click slots that work for them, and submit. The organizer sees who voted; the voters do not need a Rallly account.

Per-participant timezones

Each voter sees options rendered in their local time. The v4.8.0 release replaced the timezone modal with an inline combobox that shows city names and UTC offsets at the same time.

SSO and OAuth

Built-in OIDC, Google, and Microsoft Entra ID. Generic OIDC via OIDC_DISCOVERY_URL covers most identity providers. Native SAML is not in core but works through an OIDC bridge.

White-label branding

Custom application name, primary color, light and dark logos, and the option to hide the "Powered by Rallly" attribution. Shipped in v4.6.0 (January 2026) under the Enterprise license.

Date and time-slot polls

Two poll modes: a date-only month view for finding a day that works, and a time-slot week view for narrowing down to specific hours. Switchable per poll, mixable per option.

Calendar export

When a poll is finalized, Rallly emails an ICS attachment that drops into Google Calendar, Outlook, Microsoft 365 and Apple Calendar. No manual re-entry, no copy-paste of the time.

Spaces (team workspaces)

Multiple polls grouped by team, with roles and per-space settings. Spaces shipped in v4.3.0 and were refined through v4.6.0's collaboration features in early 2026.

Self-hostable

AGPL-3.0 licensed. The Docker image runs against any PostgreSQL backend and any S3-compatible upload store. Managed instances run on the same upstream image — no custom fork.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Rallly

Two things changed for Rallly self-hosters in late 2025 and early 2026: v4 introduced a paid license-key model for multi-user instances, and v4.7's Prisma 7 upgrade broke DATABASE_URL TLS validation against many managed Postgres providers. Combined with four authorization CVEs landed in November 2025, the case for handing patch cadence to a managed host stopped being theoretical.

Running Rallly yourself looks straightforward at install. The image starts, the welcome screen renders, you create your first poll. The work begins the second week, when the SMTP relay that worked on day one starts silently rate-limiting magic-link emails to one of your participants' inboxes. Self-hosters live in GitHub discussion #314 ("SMTP server details are not configured or are incorrect") for a reason: Rallly's entire user experience depends on email delivery, and nodemailer's failure mode is to log quietly and return success at the API layer.

The other recurring trap is Postgres. Since Rallly v4.7.0 in February 2026, Prisma v7 enforces stricter TLS validation against your DATABASE_URL. A team that pulls the latest image during a routine docker compose pull discovers their container refuses to start until they add ?sslrootcert=inline:<base64> or fall back to ?uselibpqcompat=true. That is not a five-minute fix at 9pm on a Thursday.

We pin a known-good Rallly version and a known-good Postgres version. We pre-wire a transactional SMTP provider with SPF, DKIM and DMARC on a sub-domain you control, so invitations land in inboxes from the day you provision. We back up the Postgres nightly to a separate region. We track Rallly's release notes — including breaking ones like the Prisma 7 cutover — and roll them out on a maintenance window we announce in advance.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Rallly on DANIAN

These are representative team types we set up most often. Each starts with the same flat €9 plan.

12-PERSON DESIGN AGENCY

Switched off Doodle Team after the annual line item crossed €1,000

Provisioned in Germany for proximity to clients. Google Workspace OAuth wired via GOOGLE_CLIENT_ID so designers sign in with their @studio accounts. Transactional SMTP pre-configured on polls.studio.com so client-facing invitations carry studio branding. White-label v4.6.0 add-on applied: primary color, dark-mode logo, attribution hidden.

25-STAFF MANAGEMENT CONSULTANCY

Moved off Doodle when an InfoSec review flagged participant data leaving their jurisdiction

Hosted in UK with backups kept in-region. Microsoft Entra ID SSO pre-wired via MICROSOFT_TENANT_ID so consultants sign in with their corporate identity. ALLOWED_EMAILS scoped to the consultancy's primary domain by default. Custom domain at schedule.consultancy.example with auto-renewing TLS.

8-PERSON ACADEMIC RESEARCH GROUP

Switched from a shared Doodle Pro account after a department audit flagged shared-credential use

Deployed in a US region. Generic OIDC configured against the university's Keycloak federation via OIDC_DISCOVERY_URL. Co-authors at three institutions gated by ALLOWED_EMAILS. Default instance timezone set to UTC so cross-continental polls don't render in the host's local time.

COMPARISON

Four ways to run Rallly

The choice between four paths comes down to two questions: what do you pay per month, and how many hours of your week go to keeping the thing alive. The math at 5 and 10 voters favors managed Rallly by a margin that grows with the team.

Doodle (the SaaS)Self-host on a VPSSelf-host on a home serverDANIAN managed Rallly
Cost at 1 user
$8.95/mo (Pro, monthly)~$44/mo + ops time~€210/mo amortized + electricity€9/mo
Cost at 5 users
$44.75/mo · $537/yr (Team, annual)~$44/mo + ops time~€210/mo amortized + electricity€9/mo
Cost at 10 users
$89.50/mo · $1,074/yr (Team, annual)~$44/mo + ops time~€210/mo amortized + electricity€9/mo
Reference setupDoodle's hosted SaaS, ad-free Pro or Team tier$24 production-class VPS, 2 vCPU / 4 GB / 80 GB SSDHP ProLiant ML30 or Synology DS923+, 24/7 uptimeSingle-tenant Rallly + Postgres in the region you pick
Ops time per monthNone (vendor runs it)5–10 hrs setup, then 1–2 hrs/month2–4 hrs/month + hardware on-call0 hours
SMTP for invitesBundled (ads shown on free tier)DIY: configure, monitor, fix when it breaksDIY: same, plus residential ISP egress blocksTransactional SMTP pre-wired, SPF/DKIM/DMARC
Updates and CVE patchingVendorYou (Prisma 7 TLS, v4.5 CVEs, etc.)YouWe track upstream and patch in the same week
Backup disciplineVendor-managed, opaqueYou configure and verify pg_dump cadenceYou configure off-site targetNightly Postgres + weekly uploads, off-site, 30-day retention
Data residencyVendor's choiceYour VPS regionYour homePick the region; 21 datacenter locations

BY INDUSTRY

Rallly for specific industries

Four buyer profiles see meaningful day-one benefit from managed Rallly. Each puts a different demand on the instance — branding for client-facing, SSO for staff-facing, data-minimization for participant-facing, or jurisdictional control for inter-agency working groups.

Consulting firms working with named clients run into the same scheduling problem every kick-off: pinning a meeting across five external stakeholders whose calendars are public to no one outside their own organization. Doodle Team at $8.95 per user per month is the obvious answer; at a ten-person practice, that is $1,074 a year.

We provision managed Rallly with a white-labelled poll page on a sub-domain of the firm's primary marketing domain, with branding from v4.6.0 — custom color, light/dark logo, attribution hidden. Participants vote without creating accounts; once a slot is finalized, the ICS attachment drops into Outlook or Google Calendar automatically. Setup is under an hour, and the line item lands well below what Doodle would charge for the equivalent ad-free experience.
Departmental committees and PhD viva panels routinely span three or four time zones, and the people involved often hold institutional identities at different universities. The instance is provisioned in the region nearest the chair's home institution. Generic OIDC is wired against the university's Shibboleth or Microsoft Entra tenant via OIDC_DISCOVERY_URL, so committee members sign in with their institutional credentials.

The instance timezone defaults to UTC so a Tuesday 14:00 slot does not silently render as a Monday evening for a Vancouver collaborator. ALLOWED_EMAILS gates registration to the relevant institutional domains. A 25-person committee replaces a $2,685-a-year Doodle Team subscription with a flat hosting fee.
Non-profits coordinating volunteer rotations face two simultaneous constraints: budgets that cannot absorb per-seat tooling pricing, and donor-data hygiene rules that rule out ad-supported free tools. Rallly's account-free voting model fits: volunteers vote on shift coverage with name and email only, and no third-party advertising network sees the participant list.

We deploy in the region closest to the org's primary supporter base, with a brand-customized email sender so invitations don't look like spam to volunteer Gmail accounts. A 40-volunteer organization that would otherwise face $4,296 a year of Doodle Team gets the same workflow inside a single shared instance, since voters are not users.
Public-sector procurement frameworks routinely require regional data residency and source-available software. Rallly's AGPL-3.0 license clears the source-available clause; managed hosting in the buyer's jurisdiction clears the residency one.

We pin the instance to the agency's region of record, wire SAML-or-OIDC against the agency's identity provider via OIDC_DISCOVERY_URL, and scope ALLOWED_EMAILS to the agency's domain. Calendly Enterprise, the only Calendly tier offering SAML SSO, starts at $15,000 per year; managed Rallly delivers equivalent OIDC integration at a small fraction of that cost, on infrastructure the buyer can name.

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

Poll options are stored in UTC and rendered per-viewer in their chosen timezone. The v4.8.0 release replaced the old timezone modal with an inline combobox that shows city names and UTC offsets and fixed an issue (GitHub #2289) where unauthenticated guests could not change their timezone correctly. We set the instance default to UTC unless you ask otherwise, which keeps cross-continental polls from accidentally rendering in the host's local time.
PostgreSQL. The schema covers polls, options, participants, votes, comments, spaces (workspaces) and user accounts. Poll content is stored unencrypted at the application layer — disk-level encryption and TLS-in-transit are the relevant controls. We back up Postgres nightly to a separate region with 7-day retention, plus weekly snapshots of the uploads bucket.
OIDC and OAuth: yes. Built-in providers are Google (GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET) and Microsoft Entra ID (MICROSOFT_TENANT_ID, MICROSOFT_CLIENT_ID, MICROSOFT_CLIENT_SECRET). Generic OIDC is supported via OIDC_DISCOVERY_URL, OIDC_CLIENT_ID and OIDC_CLIENT_SECRET. Native SAML is not in core — if your identity provider only speaks SAML, you can front Rallly with an OIDC bridge. We wire any of these on request, including ALLOWED_EMAILS scoping to your domain.
Set DISABLE_EMAIL_LOGIN="true" (v4.4.0+) to turn off magic-link auth. Pair it with DISABLE_USER_REGISTRATION="true" to lock the instance to your SSO provider. On managed Rallly we apply both when you provision with an OIDC, Google or Microsoft Entra integration; we leave magic-link enabled by default since most self-hosters start without an identity provider attached.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.
There is no official Doodle-to-Rallly import. Rallly's data model differs from Doodle's, and the community has not produced a working converter. The standard migration is forward-only: finish any in-flight Doodle polls on Doodle, then run all new polls on Rallly. Most teams move within a single billing cycle once invitations start going out from the new instance.
Personal single-user self-hosting is free. From v4.0.0 (early 2025), multi-user self-hosted Rallly requires a paid license key — introduced at $299 launch / $499 target, perpetual one-time, up to 50 users per tier.
Not in core. GitHub discussion #163 ("Recurring meetings") is the longest-running feature request, with the maintainer pointing to a planned when2meet-style availability grid in a future release. Today, recurring schedules are created by issuing a new poll each cycle. The workflow is still meaningfully faster than chasing replies in email.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Rallly for 7 days

No card. Cancel from the dashboard.