> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aciona.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Plans and limits

> How plan limits work, what blocks and what only warns.

The plan belongs to the **root organization** (the tenant). Child organizations inherit the plan and **share** the same limits.

## How limits are counted

All counts sum the root organization and every child:

* **Members** — distinct active people plus pending invites. Someone who belongs to both the root and a child counts as **one** seat. Re-sending an existing invite does not consume an extra seat.
* **Teams, organizations and alert sources** — a direct sum across root and children.
* **Incidents per month** — a monthly tenant counter, summing every organization.

<Note>
  **Services are not enforced.** That is deliberate: aciona.me never fails to create an incident because a new service showed up.
</Note>

## Soft limit vs. hard limit

<Columns cols={2}>
  <Card title="Soft limit — incidents" icon="bell-ring">
    **Never blocks.** The counter keeps going even above 100%. You get warnings at **80%** and **100%** of the monthly limit.
  </Card>

  <Card title="Hard limit — resources" icon="lock">
    **Blocks creation** of members, teams, child organizations and alert sources once the limit is reached. The operation returns `402 Payment Required`.
  </Card>
</Columns>

<Warning>
  When monthly incidents reach **100%** of the limit, creating **any resource** also becomes blocked — but incidents keep being created and notified normally. Your operation never stops because of a limit.
</Warning>

## Subscription

* Only the **owner** of the root organization manages the subscription.
* You can switch between monthly and annual billing, update payment details and cancel.
* Cancellation takes effect **at the end of the period already paid for** — you keep using it until then.
* After expiry there is a grace period before any downgrade.
* A downgrade **preserves existing resources**: nothing is deleted. What changes is the ability to create new resources above the new limit.

## Retention

Each plan defines how long history stays available. Independently of that, raw alert payloads have their own automatic purge policy — the original content is removed after the configured retention window, preserving the incident and its timeline.

<Note>
  The current limits, prices and retention for each plan live on the product's pricing page and in the subscription screen of the dashboard. Check there for up-to-date numbers.
</Note>

## When you hit a limit

<Steps>
  <Step title="Check what is being counted">
    Remember the count sums root and children, and that pending invites consume seats.
  </Step>

  <Step title="Free up what is unused">
    Remove stale pending invites, deactivate inactive members, and delete alert sources that no longer receive anything.
  </Step>

  <Step title="Consider changing plan">
    Under **Settings → Plan**, the root owner sees current usage and can upgrade.
  </Step>
</Steps>