Usage, limits and data retention

What counts toward the plan, what happens at a limit or at the end of the trial, and how long PostDeploy keeps your data.

What counts

Each organization can store 1 million error events and 100 GB of logs per calendar month (UTC).

Log usage counts the bytes of each accepted log entry once.

At a limit

When an allowance is used up, ingestion answers 429 with Retry-After until the next month starts, and stores nothing from that request.

PostDeploy also limits request rates for each project. Over a rate limit, ingestion answers 429 with Retry-After.

After the trial

When the trial ends without a subscription, ingestion stops. Stored errors and logs stay readable until they expire.

Retention

Errors are kept 90 days from the time PostDeploy receives them.

Logs are kept 90 days from the time PostDeploy receives them, even when the log entry carries an older timestamp.

Where data is stored

PostDeploy uses Cloudflare Workers, isolated Durable Object SQLite storage for each organization, and Cloudflare R2 archives. PostDeploy commits accepted logs to organization storage before it returns success. If R2 is unavailable, archive writes retry. If the archive backlog is full, ingestion answers 429.

Search limits

A log search reads a bounded part of the history per request. An archived search can return a cursor. Pass the cursor to continue further back.