Keeping our AI assistant working well is a human responsibility at Depot. PostHog's AI engineering features turned our never-ending reviews into 30 minutes a week.
Sherlock can now analyze Depot CI workflows and jobs directly from the dashboard, using run context, attempts, step details, logs, summaries, and resource metrics to help you understand failures and slow jobs faster.
Sherlock, our AI assistant, just got smarter. It can now analyze your builds and GitHub Actions jobs, break down your CI analytics, check your project settings, and even open support tickets on your behalf.
We built Sherlock, an AI assistant for the Depot docs. Sherlock searches our documentation with direct access to the markdown source, so answers come exclusively from our content with links to the docs it referenced. We also think Sherlock is outrageously cute.
Not every self-hosted runner failure is actually a runner problem. GitHub Actions and third-party actions often expect environmental features that GitHub-hosted runners provide by default. When your setup differs, you may get cryptic errors that point to the wrong cause. Here are three real support cases where the symptoms looked like runner issues but weren't.
BuildKit's DAG solver transforms your Dockerfile into an optimized execution plan, finding every opportunity to run things in parallel. Learn how stage parallelism, instruction parallelism, and work deduplication combine to dramatically speed up your container builds.
