Plans and limits

A plan tier is a value stored on your user. It changes one thing, a cap on scheduled launches. The rest of this page lists the limits that apply whatever the tier.

The tier¶

The tier is a field on the user, not on the organization. A new user starts on free. Pentr sets the tier; nothing in the console or the API changes it, and neither of them shows it. The one place it appears is the reason recorded when a schedule's occurrence is skipped for the cap, which names the tier.

What the tier changes¶

The tier sets how many engagements the organization may have queued or running at the same time:

Tier	Cap
free	1
pro	3
enterprise	10

A tier the table does not list gets a cap of 1.

The cap is checked in one place: when a schedule fires. The count covers the whole organization's queued and running engagements, and the tier is read from the user who created the schedule. At or above the cap, the occurrence is skipped. An engagement you submit from the console or the API is never refused for the cap, and counts towards it once it is queued. Caps and skips describes how a capped schedule behaves.

The cap does not change how fast runs start. The scheduler runs one engagement at a time and the rest wait in the queue, whatever the tier (Running an engagement).

What the tier does not change¶

Nothing else reads the tier. Every organization has the six frameworks, share links, reports in PDF, SARIF and CSV, locker exports, schedules and the API, on the same terms.

Limits that apply to every organization¶

Limit	Value	Described in
Agent steps in one run	500	When a run fails
Consecutive failing steps before a run aborts	5	When a run fails
Time one command may run	300 seconds	Rules of engagement
Size of one artifact	10 MiB	Artifacts
Share link lifetime	1 to 365 days, default 30	Share links
Share requests from one address	60 a minute	Share links
Failed share-token lookups from one address	10 a minute	Share links
Locker downloads through one share link	10 an hour	Share links
Shortest gap between a cadence's fire times, on the local clock	1 hour	Cadence
Life of an ownership attestation	90 days	Ownership verification
Retention of a run's progress trace	24 hours	Running an engagement
Events kept in a run's progress trace	5,000	Running an engagement

Reaching the step limit or the consecutive-failure limit ends the run, which is then recorded as completed, the same as a run that finished. A command that reaches its time limit is killed and the run continues. An artifact over its size limit fails the step that produced it.