Deploy history and retention

Rollback artifacts, build logs, live logs, and monitoring history

Ask your agent

Explain how long Percher keeps my logs and old versions.Read the guide at percher.app/docs/retention

How it works, with exact details

Every deploy is tracked with full metadata (status, timestamp, build log, error message). The plan's rollback number is how many recent deploys keep their image and source tarball for fast rollback. Older deploys keep their metadata, but those heavy artifacts are cleaned up automatically.

Deploy history and retention
Plan	Deploy artifacts kept	Build logs	Monitoring history
Free Deploy artifacts kept 5 most recent · Build logs 3 days · Monitoring history 1 day	5 most recent	3 days	1 day
Starter Deploy artifacts kept 15 most recent · Build logs 14 days · Monitoring history 7 days	15 most recent	14 days	7 days
Maker Deploy artifacts kept 30 most recent · Build logs 30 days · Monitoring history 30 days	30 most recent	30 days	30 days
Max Deploy artifacts kept 60 most recent · Build logs 90 days · Monitoring history 90 days	60 most recent	90 days	90 days

Runtime logs are live, rotating output. percher logs reads the current container's Docker log, capped at about 30 MB per container. It is not a day-based archive and disappears when the container is replaced or deleted. Use build logs, crash reports, or an external log service when you need durable history.