# Trust ladder & plans

Autonomy in Automaintainer is something you **grant**, not something forced on
you. As trust grows you move up a ladder, from review‑only to fully hands‑off.

## The trust ladder

| Stage | Who reviews | Who merges |
|-------|-------------|------------|
| **Free** | You (self‑review) | You |
| **Pro** | AM reviews the PR | You merge |
| **Max** | AM reviews | AM [auto‑merges](/docs/auto-merge) after a green gate |
| **Enterprise** | AM reviews | AM auto‑merges |

The Verification Gate is enforced at **every** stage — the difference is who
presses merge. A red gate never produces a merge‑ready PR (it opens as a draft).

## What each plan unlocks

| Capability | Free | Pro | Max | Enterprise |
|---|---|---|---|---|
| Verified runs + PRs | ✓ | ✓ | ✓ | ✓ |
| BYOK (your provider keys) | ✓ | ✓ | ✓ | ✓ |
| AM code review on PRs | — | ✓ | ✓ | ✓ |
| Auto‑merge after gate | — | — | ✓ | ✓ |
| [Explore mode](/docs/explore-mode) — propose | — | ✓ | ✓ | ✓ |
| Explore mode — **autonomous** select & run | — | — | ✓ | ✓ |
| Runs / day | 3 | 30 | 150 | unlimited |

Limits are the single source of truth in the product; see
[Plans & limits](/docs/plans-and-limits) for the authoritative numbers.

## Picking where to start

- **Trying it out?** Free — you stay fully in control and review everything.
- **Steady maintenance?** Pro — AM does the work and reviews; you press merge.
- **Hands‑off cadence?** Max — AM merges verified work and can pick its own
  bounded tasks via [explore mode](/docs/explore-mode).

## Earned trust

Each repo also shows a **Trust score** (0–100) on its card and in its settings —
a read‑only signal of how reliably AM has performed there, from recent runs:
**ship rate**, **first‑try gate pass rate**, and **reliability**. It maps to a
recommended autonomy tier (*building → review & merge → auto‑merge ready*) plus
the single thing that would raise it.

`auto‑merge ready` is only reachable with a **verify gate** and an earned track
record — a repo with no gate can't get there, however well it ships. The score
is **advisory by default** — but enabling **"Only when trust is earned"** on a
repo's [auto‑merge](/docs/auto-merge) makes it enforced: auto‑merge then waits
until the repo reaches `auto‑merge ready` (and pauses again if reliability
regresses). Leaving that off, an `auto‑merge`‑enabled repo merges green PRs
without waiting on the score.

## Related

- [How it works](/docs/how-it-works)
- [Auto‑merge](/docs/auto-merge) · [Verification Gate](/docs/verification-gate)
- [Billing & cancellation](/docs/billing)