Plans & Quotas
Plans determine how many uploaded runs, events, and retained artifacts your team gets in Cloud.
Plans
| Free | Pro | Team | |
|---|---|---|---|
| Uploaded runs / month | 1,000 | 6,000 | 50,000 |
| Events per run | 2,000 | 10,000 | 50,000 |
| Run history | 7 days | 30 days | 90 days |
| Artifact storage | 500 MB | 5 GB | 50 GB |
| Projects | 1 private + 1 public | 5 | Unlimited |
| Team members | 5 | 15 | 50 |
| Email alerts | — | ✓ | ✓ |
| Slack / webhook alerts | — | — | ✓ |
| Flaky test detection | — | — | ✓ |
| Prometheus export | — | — | ✓ |
| SLA guarantee | — | — | ✓ |
How runs are counted
One run = one glubean run --upload execution, regardless of how many tests or events it contains.
Examples:
- A run with 3 tests and 50 events = 1 run
- A run with 200 tests and 5,000 events = 1 run
- Running
glubean run --upload10 times in CI = 10 runs
Runs without --upload (local-only) are never counted.
What counts as an event
Events are the individual data points inside a run:
| Event type | Source |
|---|---|
assertion | Each ctx.expect() call |
log | Each ctx.log() call |
trace | Each HTTP request/response captured |
result | Each test’s pass/fail outcome |
If a run exceeds the event limit, additional events are dropped. The run itself still uploads and counts.
Run history retention
Runs older than your plan’s retention window are automatically deleted. Artifacts associated with expired runs are also removed.
| Plan | Retention |
|---|---|
| Free | 7 days |
| Pro | 30 days |
| Team | 90 days |
Checking your usage
Current usage is visible in Project Settings → Usage. The CLI also warns when you approach your monthly limit.
Next
Last updated on