English
Rallly Hosting
Find the best time for groups to meet using simple collaborative scheduling polls.
No setup fees-
One click deploy -
4 GB RAM Memory needed -
50 GB Disk Space Needed -
From 10 € Price
Official links
Rallly’s official links and original website
Rallly Website
More
Tech
- Docker image
- lukevella/rallly:latest
- Default port
- 3000
- Database
- postgres
How Rallly works
An organiser creates a poll, proposes dates or times, and shares its link with participants. Voters open the page, enter their name, and mark which options work for them without creating an account. The organiser reviews the combined availability, comments, and responses before choosing a final option or updating the poll.
Poll management belongs to a signed-in organiser. The upstream self-hosted edition uses emailed magic links for normal authentication unless a separate single sign-on provider is configured. It also uses email for notifications. That dependency matters on the AvaHost service because application email delivery is disabled.
Key Rallly features
Group polls present candidate times in one shared grid, reducing the need to compare replies across separate messages. Participants can add comments and revise responses while the poll remains open. Organisers can set deadlines, limit choices, and close or finalise a poll when a decision has been reached.
The application supports localisation, administration controls, and optional branding or identity configuration depending on the upstream edition and setup. Those options are separate from the basic polling workflow and should not be assumed to be bundled with the catalogue image.
Rallly vs Doodle
Rallly is a self-hosted group-poll application focused on collecting availability and letting an organiser control the installation. Doodle is a provider-managed scheduling platform that combines group polls with calendar connections, booking pages, one-to-one scheduling, reminders, and video-meeting integrations.
Doodle may suit teams that need a ready-operated scheduling account and managed calendar integrations. Rallly is a better conceptual fit when poll data and infrastructure control matter, but its email-based organiser authentication must work before the self-hosted service can be used reliably.
Who uses Rallly
Volunteer groups compare dates for meetings, families coordinate gatherings, and project teams gather availability from people outside their normal calendar system. Because participants can vote from a link, the poll is useful when the invited group spans several organisations or does not share one scheduling platform.
Rallly is not a substitute for resource booking, appointment payments, or a full calendar suite. It helps a group reach a scheduling decision; the final event may still need to be created in another calendar or meeting service.
Self-hosting Rallly: requirements and cost
Usage is driven by poll count, participant volume, comments, active organisers, and retained response history. PostgreSQL stores users, polls, options, votes, and settings. AvaHost provisions that database beside Rallly, but the PostgreSQL container remains unmanaged and the application-only RAM figure does not cover its footprint.
The corrected recommendation is Plan 4 at €20 for the Rallly and PostgreSQL stack. One-click deployment, a custom domain, automated HTTPS, automatic application updates, and scheduled backups are included. However, AvaHost disables application email, while Rallly requires SMTP for magic-link sign-in; organiser registration and authentication are therefore unavailable in the current hosted configuration.
F.A.Q
Rallly maps to €20 on Plan 4 after accounting for both the application and its PostgreSQL container. The plan includes the hosted stack, a custom domain, automated HTTPS, application updates, and scheduled backups. Poll volume, participant responses, comments, retained history, and organiser activity shape future resource use.
AvaHost provisions PostgreSQL beside Rallly and configures the application to use it. Accounts, polls, proposed times, votes, comments, and settings depend on that database. The container is included but unmanaged, so its records and the persistent application configuration should be treated as one installation when planning maintenance, exports, or recovery.
The web interface can use a custom domain with automated HTTPS after the required DNS records point to the hosted service. The final address should be chosen before poll links are circulated. Changing it later requires testing organiser access, participant links, comments, and any references that still use the former hostname.
No functional organiser sign-in path is available in the current service configuration. Rallly normally sends magic-link emails through SMTP, while AvaHost disables application email and does not bundle an alternative identity provider. Participants can vote without accounts only after a poll exists, so the hosted application should not be treated as production-ready until authentication is changed.