ttl.sh

What ttl.sh is

ttl.sh is an ephemeral container registry for pushing and pulling OCI artifacts through the web or API. It requires no account or authentication: users can work without tokens, passwords, or API keys. Each artifact has a time-to-live that can be set from minutes up to 24 hours, with one hour as the default. When the TTL expires, images disappear permanently, so their configured lifetime determines how long they remain available. ttl.sh says it works with Docker, Podman, Helm charts, and OCI-compliant tooling. It describes its infrastructure as global and CDN-backed and says it does not track or log users or know what they push. Named CI/CD workflows include GitHub Actions, GitLab CI, CircleCI, and Jenkins; examples cover Docker, Helm, and GitHub Actions. The service is presented for CI/CD pipelines, integration testing, open source projects, and local development, serving users from solo developers through large CI/CD pipelines. The Free plan costs nothing and supports OCI artifacts and retention policies, with no sign-up or authentication requirement.

Who it suits

It suits developers and teams needing short-lived OCI artifacts for CI/CD pipelines, integration testing, open source projects, or local development. It can serve solo developers as well as large CI/CD pipelines.

Limits

The Free plan defaults to a one-hour TTL and allows a maximum TTL of 24 hours. Images are deleted permanently when that period ends.

Getting started

1. Open https://ttl.sh/
2. Use the web interface or API
3. Push an OCI artifact with Docker, Podman, Helm, or compatible tooling
4. Set a TTL from minutes to 24 hours, or use the one-hour default
5. Connect the workflow through GitHub Actions, GitLab CI, CircleCI, or Jenkins

Verdict

ttl.sh offers a simple path to temporary OCI artifact storage without account setup. Its defining constraint is brief retention: artifacts expire at their TTL, which cannot exceed 24 hours.