Rallly

Self-hosted group scheduling polls and meeting coordination.

  • AWS
  • DigitalOcean
  • Railway
  • Linode
  • Vultr
  • Hostinger
  • LumaDock
Customer-operated Servers / containers Open Source / Open Core

5 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    Cloudron package; Application platform deployment

  2. Operated by

    Your team

    Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Cloudron Store ↗ · Source checked 2026-11-19

  • DigitalOcean: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Cloudron Store ↗ · Source checked 2026-11-19

  • Linode: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Cloudron Store ↗ · Source checked 2026-11-19

  • Vultr: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    Cloudron Store ↗ · Source checked 2026-11-19

  • Hostinger: Customer VPS account · Customer-operated

    An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.

    Cloudron Store ↗ · Source checked 2026-11-19

  • LumaDock: Customer VPS account · Customer-operated

    An application on a virtual server in the customer's hosting account. Review root access, backups and application maintenance separately.

    Cloudron Store ↗ · Source checked 2026-11-19

  • Railway: Customer platform workspace · Customer-operated

    Customer-controlled application services in a hosting-platform project. The platform operates the underlying infrastructure.

    Railway ↗ · Source checked 2026-11-19

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodCloudron package; Application platform deployment
InfrastructureServers / containers
Rallly application, PostgreSQL, persistent storage and outbound email. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure.
Licensing modelOpen Source / Open Core
GNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.
LicenseGNU AGPL-3.0 for the reviewed upstream edition; optional commercial services and bundled components have separate terms.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

5 of 12 fields researched (42%) · 5 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

The self-hosting guide documents Google, Microsoft Entra ID and generic OIDC login from v3.4 onward. Configure callback URLs, verified email claims and linking policy; multi-user licence entitlements are a separate consideration.

Rallly self-hosted user identity; review the selected v4 deployment and license · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The official installer provisions a Compose stack, generates secrets and supports external database, object storage and reverse-proxy settings. Review the downloaded script before execution, pin compatible images and plan backups; this is not a production HA template.

Current official self-hosting stack and installer · Source ↗ · Deployment artifact ↗ (Moving official installer; inspect and pin the selected application/stack release) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The Cloudron package declares 2048MB minimum app memory. The platform additionally requires at least 2 GB RAM and 20 GB disk; this is not whole-system, data-volume or HA sizing.

Selected Cloudron application package; add database, files, backups and concurrent workload requirements · Source ↗ · Cloudron platform requirements ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The current self-hosting guide states free personal use and asks multi-user installations to purchase a licence key. It lists Plus at $49, Organization at $499 and Enterprise from $999; keys cover Rallly v4.x with tier/user/space limits. Activation requires the licensing service. These runtime-plan terms add detail beyond the repository’s AGPL notice.

Published Rallly v4 self-hosting licence-key tiers; confirm applicable user/space allocation and quote · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Reviewed upstream v4.17.1 release. Provider images and packages have separate versions; this snapshot does not establish support duration or a future release cadence.

Rallly upstream application; verify compatibility with the selected package · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (7 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Security controls
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery.

Community & maintenance

The reviewed upstream contributor history includes lukevella, snyk-bot, jonas-hoebenreich, alongside the project installation and maintenance history. This establishes community participation, not a commercial support or production-capacity guarantee.

Category fit

Collaboration
Self-hosted group scheduling polls and meeting coordination.

Compare within Collaboration

  • 3CX Self-HostedCommercial business communications and PBX platform installed into the customer's public-cloud account.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Commercial Only
  • Apache AnswerSelf-hosted community questions, answers and knowledge content.
    • AWS
    • DigitalOcean
    • Railway
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • BigBlueButtonSelf-hosted conferencing and virtual classroom platform.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Hetzner
    • Scaleway
    Customer-operated · Open Source / Open Core
  • BookStack Self-HostedSelf-hosted wiki and documentation organized into books, chapters and pages.
    • AWS
    • DigitalOcean
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • Campfire (ONCE)Self-hosted group chat and team conversation application.
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Collabora Online (CODE)Community office editing server for integration with a document platform.
    • AWS
    • DigitalOcean
    • Hetzner
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • Confluence Data CenterCommercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
    • AWS
    • Google Cloud
    • DigitalOcean
    • Hetzner
    • Linode
    • Vultr
    Customer-operated · Open Source / Open Core

Showing 8 of 25 other listings in Collaboration. These products address related workflows; read their category-fit notes before comparing scope. See all of Collaboration →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Cloudron Store ↗ · AWS, DigitalOcean, Linode, Vultr, Hostinger, LumaDock

      Package platform documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      The reviewed Cloudron application package runs on the customer server. Pair it with Cloudron’s named-provider installation procedure; Cloudron subscriptions, package updates and upstream support are separate.

    • Railway ↗ · Railway

      Community template · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.

      Rallly application, PostgreSQL, persistent storage and outbound email. Scheduling polls are separate from a full enterprise calendar service. Email-based login requires configured, reliable SMTP delivery. This source is distinct from the Cloudron package.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory