# Editions

> Cloud, self-hosted and Community — which deployment fits, and what each one gives you.

> For the complete documentation index, see [llms.txt](https://helpdesk.orangescrum.com/llms.txt).

Source: https://helpdesk.orangescrum.com/guide/cloud/plans/editions

---
Orangescrum ships in three forms. The feature set and who operates it are the
two things that differ.

- [Cloud](https://helpdesk.orangescrum.com/guide/cloud/get-started/introduction): We host it. Full feature set, three tiers, unlimited users.

- [Self-hosted](https://helpdesk.orangescrum.com/guide/self-hosted/get-started/introduction): Same product, your infrastructure. Commercially licensed.

- [Community](https://helpdesk.orangescrum.com/guide/community/get-started/introduction): Free and open source under AGPL v3. A focused core.

## Choosing

**Choose Cloud if…**

    You want the full product without operating it. No servers, no upgrades, no
    backup schedule, no on-call. This is the right default unless something
    below pushes you elsewhere.

**Choose self-hosted if…**

    Data residency, regulatory requirements or internal policy mean the data
    must stay on infrastructure you control — and you still need agile,
    reporting, resourcing and integrations. See the
    [Self-hosted guide](https://helpdesk.orangescrum.com/guide/self-hosted/get-started/introduction).

**Choose Community if…**

    You want projects, tasks and manual time entry on your own server, for free,
    and you can live without agile boards, Gantt, reporting, resourcing and
    integrations. Also the right choice if you want to read or modify the source.

## What Community leaves out

The Community Edition was carved out of the commercial codebase. It keeps
projects, tasks, subtasks, milestones, checklists, labels, comments,
attachments and manual time entry — and removes everything else:

| Not in Community | Where it lives |
| --- | --- |
| Sprints, backlog, epics, velocity | Cloud Pro and above |
| Gantt, critical path, dependencies | Cloud (Gantt from Basic, critical path Premium) |
| Reports and dashboards | Cloud Premium |
| Resource management and availability | Cloud Premium |
| Budget, cost and invoicing | Cloud Pro and Premium |
| Test case manager and defects | Cloud Premium / Pro |
| Wiki and documents | Cloud |
| Git, Azure DevOps, Google integrations | Cloud Pro and above |
| SSO, teams, business units, audit trail | Cloud Premium |
| Developer API and MCP | Cloud Premium |
| Running timer, timesheets, approvals | Cloud Pro and above |
| Custom fields, custom statuses, automation | Cloud Pro and above |

> **Removed, not locked**
>
> These are not paywalled toggles — the code is not in the Community Edition.
> There is no licence check to circumvent and no seat counter.

## Licensing

| Edition | Licence |
| --- | --- |
| Cloud | Commercial subscription |
| Self-hosted | Commercial licence |
| Community | [GNU AGPL v3.0](https://helpdesk.orangescrum.com/guide/community/project/licence) |

The AGPL's network clause matters if you plan to modify the Community Edition
and offer it to others over a network — read the
[licence page](https://helpdesk.orangescrum.com/guide/community/project/licence) before building on it.

## Moving between editions

Community → Cloud or self-hosted is an **assisted migration**, not a
configuration change: the Community schema was trimmed to roughly 149 tables
against the full product's ~310. Talk to Orangescrum before planning dates.

- [Migration guidance](https://helpdesk.orangescrum.com/guide/community/project/upgrade-to-cloud): What moving involves.

## Next

- [Plans and limits](https://helpdesk.orangescrum.com/guide/cloud/plans/plans-and-limits): The three Cloud tiers in detail.

- [Feature matrix](https://helpdesk.orangescrum.com/guide/cloud/plans/feature-matrix): Feature-by-feature, tier by tier.