Puck docs

Limits and the free tier ​

Retention, the Ingest cap and what the free tier includes.

The free tier ​

Every new Team starts on the free tier:

Free tier
Ingest cap1 GB (1 000 000 000 bytes) of telemetry per UTC day
Retention7 days
Active credentials per Source2

For more, write to us. We set a Team's limits by hand for now.

Ingest cap ​

The Ingest cap is how many bytes of telemetry a Team may send per UTC day. It is counted for the Team as a whole, across all its Sources, and the day rolls over at 00:00 UTC.

The bytes are counted after decompression, so gzip on the wire doesn't change it. Whether your Collector compresses or not, the same Log records cost the same.

Not enforced yet

Puck stores each Team's cap, but its gateway does not refuse anything over it today: no Team receives a 429 yet. Enforcement is tracked in LOG-109. The rest of this section is what will happen when it is.

Over the cap, the gateway refuses the Team's records until the day rolls over. The answer depends on how you send:

  • OTLP over HTTP and Loki push: HTTP 429 Too Many Requests.
  • OTLP over gRPC: RESOURCE_EXHAUSTED.

Other Teams are not affected. A Collector treats 429 as a temporary error and retries, and a Host Collector's queue on disk holds the records meanwhile; an SDK keeps them in memory and may drop them (see OTel SDK). Records refused are not stored. To stay under the cap, see the troubleshooting page.

Retention ​

Retention is how many days of Log records a Team keeps, counted from each record's own time, not from when it arrived. It is 7 days on the free tier.

  • Older records are dropped when they arrive. A record whose time is more than Retention plus one day in the past is not stored. That matters when you first connect a Host that has old logs: only the last 8 days of them arrive. A record dated in the future is kept.
  • Expiry is not by your Retention yet. Storage still expires every Team's Log records after 90 days, whatever its Retention. Until expiry follows Retention, records can stay searchable longer than your Retention says. Don't rely on it. Expiring them by Retention is the next step.

Other limits ​

  • Credentials: a Source has at most two active credentials, so one can replace the other. See Credentials.
  • Filters: at most 100 conditions, nested at most 10 deep, and a regular expression of at most 1 KB. See the Filter language.