Depot
Day 29 after signup
Durable logs are now live for Depot CI and Sandboxes
Investigate failures and compare past runs, even months later.
Why it works
- Start with a recognizable problem so readers understand why the capability matters before introducing it.
- Explain the feature through specific use cases and concrete ways to use it, then offer a deeper resource for readers who want more detail.
How it is built
- Personal greeting
- Problem with old logs
- Durable logs overview
- Use cases and SDK methods
Email copy
Hi [First name], When a CI job fails intermittently or a sandbox run goes wrong, you need the logs to figure out what happened. That gets hard when the run was months ago or the sandbox has already stopped. We built a new log platform so those logs stick around: Depot CI logs are kept indefinitely. Pull up a failing run from months ago and compare it with today’s build. Sandbox logs stay available after the sandbox stops. Query them through the Sandbox SDK with the sandbox ID: sandbox.logs.tail() for the latest lines, .fetch() for a time range, or .stream() to follow live output. If an agent is doing the investigating, it can read the last 100 lines or a single step, then pull in more context only if it needs it. The blog post covers how we built durable logs and how to use them. Read the blog post Looking for your CI logs? See the docs → The Depot team You are receiving this email because you opted in to receive updates from Depot Technologies Inc. Depot Technologies Inc., 9450 SW Gemini Dr Suite 52521 Beaverton, OR 97008 Unsubscribe