Skip to content

Rallly is an open-source scheduling and collaboration tool designed to make organizing events and meetings easier.

2.8 KB
Raw Blame
---
icon: "house"
title: "Introduction"
description: "Self-host Rallly on your own infrastructure."
---

Self-hosting Rallly gives you full control over your instance and your data. The self-hosted distribution is designed to be easy to install and maintain on a single server — everything you need is bundled into one Docker Compose stack.

## Rallly Cloud vs Rallly Self-Hosted

Rallly comes in two flavours built from the same codebase.

**[Rallly Cloud](https://rallly.co)** is the hosted service we run. It is designed to scale horizontally across distributed infrastructure and serve a large number of users. It is the fastest way to get started and is maintained by us.

**Rallly Self-Hosted** is optimised for simplicity of deployment. Out of the box, the application, database, object storage, and TLS termination all run on a single machine via Docker Compose — you own the data, you own the server, and updates are a single command. If you already run a managed Postgres or S3-compatible service, you can point Rallly at those instead and the bundled containers are skipped automatically.

<Note>
  Some Cloud features (billing, metered quotas) are compiled out of the self-hosted image. Licensing for multi-user self-hosted instances is covered on the [Licensing page](/self-hosting/licensing).
</Note>

## Differences from Rallly Cloud

The user guides describe Rallly Cloud. On a self-hosted instance, these work differently:

- **Open polls**: there is no [open poll limit](/faq). Every account can have any number of polls collecting votes at once.
- **API**: the [Rallly API](/api-reference/introduction) is only served by Rallly Cloud. Self-hosted instances do not have it.
- **Spaces**: [collaboration](/spaces/collaboration) is always on and the setting is not shown. The instance is already the boundary of your organization, so adding someone to a space is how you work together.

## What's included

A self-hosted install is a batteries-included stack. You do not need to provision these services separately.

- **Traefik** — reverse proxy with automatic HTTPS via Let's Encrypt
- **Rallly** — the web application
- **PostgreSQL** — primary database
- **Garage** — S3-compatible object storage for file uploads

Only Traefik binds to host ports (80 and 443). Everything else is isolated on the internal Docker network.

## Next steps

- **[Installation](/self-hosting/installation/docker)** — set up Rallly on your server.
- **[Configuration](/self-hosting/configuration)** — environment variables reference.
- **[Management](/self-hosting/management)** — update, back up, and operate your instance.
- **[Control Panel](/self-hosting/control-panel)** — manage users and instance settings.
- **[Licensing](/self-hosting/licensing)** — when a license is needed and how to apply one.

If you would rather not run a server, use [Rallly Cloud](https://rallly.co).