{"id":79909,"title":"✨ Depot: Managed GitHub Actions runners for AWS","tagline":"30% faster compute, 10x faster cache, 1/2 the cost","body":"Hey, we’re Kyle and Jacob, the founders of [Depot](https://depot.dev), a hosted container build service for Docker images, and we’re excited to launch our new product: [managed GitHub Actions runners for AWS](https://depot.dev/products/github-actions)!\n\n![uploaded image](/media/?type=post\u0026id=79909\u0026key=user_uploads/956934/99034910-f435-44ef-8301-3610146d56bd)\n\n## The Problem\n\nWhile GitHub Actions is one of the most prevalent CI providers, Actions is slow for a few reasons:\n\n* GitHub uses underpowered CPUs.\n* Network throughput for cache and the internet at large is capped at 125 MB/s.\n* Total cache storage is limited to 10GB per repo.\n* Larger runners are expensive and take a long time to start running jobs.\n\n## The Solution\n\n**Depot-managed runners solve this!** Rather than your CI jobs running on GitHub’s slow compute, Depot routes those same jobs to powerful EC2 instances. And not only is this faster, it’s also 1/2 the cost of GitHub Actions!\n\nWe do this by launching a dedicated instance for each job, registering that instance as a self-hosted Actions runner in your GitHub organization, and then terminating the instance when the job is finished.\n\nWe've also integrated the runners with our existing distributed storage cluster that we use for Docker image builds for up to 10x faster cache throughput! 💪\n\n## Demo Video\n\n\u003chttps://www.youtube.com/watch?v=VX5Z-k1mGc8\u003e\n\n## Tech Details\n\nUsing AWS as our compute provider has a few advantages:\n\n* We launch fast `m7a` instances, which are typically 30%+ more performant than alternatives.\n* Each instance has high-throughput networking of up to 1.5 GB/s, hosted in `us-east-1`, so interacting with artifacts, cache, container registries, or the internet at large is quick.\n* Each instance has a public IPv4 address, so you’re not sharing any rate limits with anyone else.\n\nBy integrating the runners with the distributed cache system (backed by S3 and Ceph) that we use for Docker build cache, jobs automatically save/restore cache from this cache system, with speeds of up to 1.5 GB/s, and without the default 10 GB per repo storage limit.\n\nAdditionally, the runners are located in the same VPC as our [Docker build service](https://depot.dev), so for anyone using both, built containers are now able to `--load` back into CI for testing much faster than they would over GitHub’s default network.\n\nWe build our machine image from [GitHub's image definition](https://github.com/actions/runner-images), so all the same software you expect is pre-installed. Support for Arm runners, powered by Graviton instances, is in beta now.\n\n## Getting Started\n\nYou can sign up at \u003chttps://depot.dev/sign-up\u003e for a free trial if you’d like to try it out with your own workflows!","slug":"Kmr-depot-managed-github-actions-runners-for-aws","created_at":"2024-04-03T14:38:17.273Z","updated_at":"2026-04-29T23:57:14.487Z","total_vote_count":21,"url":"https://www.ycombinator.com/launches/Kmr-depot-managed-github-actions-runners-for-aws","share_image_url":"https://www.ycombinator.com/media/?type=post\u0026id=79909\u0026key=user_uploads/956934/99034910-f435-44ef-8301-3610146d56bd","company":{"id":27693,"name":"Depot","slug":"depot","url":"https://depot.dev","logo":"https://bookface-images.s3.amazonaws.com/small_logos/4bc0c4958bdeddfb5cee7883f042a17f65e1bd00.png","batch":"Winter 2023","industry":"B2B","tags":["Developer Tools","DevOps"],"search_path":"https://bookface.ycombinator.com/company/27693"}}