Reference / Retention and limits

Reference

Retention and limits

How long files are kept, and the limits that apply to uploads and jobs.

Retention#

GuardPkg keeps your files only as long as it needs to. During the alpha:

  • Uploaded binaries are deleted 7 days after upload.
  • Job output and diagnostics are deleted 7 days after the job finishes.

The exact time is always in the expires_at field of the binary, job or artifact, and on the dashboard.

When something expires, the files are deleted but the record stays, so your job history still makes sense:

  • A binary disappears from lists and returns 404. Jobs that ran on it show "binary_purged": true.
  • A job keeps its status, settings, counts, stats and timeline. Its purged_at is set, it has no artifacts, and its output and diagnostics return 410 Gone.

You can delete a binary yourself at any time; see Binaries.

Limits#

Limit Value
Upload size 50 MB
File types PE32+ (x86-64) executables and DLLs
Job run time 10 minutes; longer jobs fail with a message saying so
Diagnostics stored per job 5,000 (counts include all of them)
JSON request body 64 KB
limit on job lists 200