HNHacker News
TopNewBestAskShowJobs

kylegalbraith

574 karma · joined September 6, 2017

Founder of https://depot.dev/

Blog at https://blog.kylegalbraith.com

Previously at: Era Software, Thorn, Zapproved

Previously built: https://ultimatefantasysupercross.com/ https://kylegalbraith.com/learn-aws/ https://kylegalbraith.com/learn-by-doing/

kyle@depot.dev

submissionscomments
kylegalbraith··on Ask HN: Who is hiring? (August 2025)
Depot (W23) | Multiple openings | Remote (North America, Europe) | Full-time

Depot is the fastest place to build software. We accelerate builds for customers using GitHub Actions, Docker, Bazel, Gradle, and more. We're seeking the following roles:

- Solutions Engineer ($120k-$150k)

- Developer Marketer focused on Community & Events ($100k-$130k)

- Technical Content Writer ($90k-$110k)

We offer a fully remote working environment anywhere in North America and Europe with competitive salaries and equity.

For more details, and to apply: https://depot.dev/careers

kylegalbraith··on Reverse engineering the GHA cache to improve performance (2024)
Yeah this is a great point. Thank you for adding this. I didn’t post this but will try to flag up the chain.
kylegalbraith··on Reverse engineering the GHA cache to improve performance (2024)
Founder of Depot here. Looks like Blacksmith was inspired by our implementation from last May and wrote a similar post to ours here.
kylegalbraith··on Reverse engineering GitHub Actions cache to make it fast
Fun to see folks replicating what we’ve done with Depot for GitHub Actions [0]. Going as far as using a similar title :)

Forking the ecosystem of actions to plug in your cache backed isn’t a good long term solution.

[0] https://depot.dev/blog/github-actions-cache

kylegalbraith··on Basically Everyone Should Be Avoiding Docker
This reads less like an article about the downsides of Docker and more like an article about how someone doesn’t fully understand Docker.

Not that I think Docker should always be used. It’s a simple piece tech on the surface but explodes in complexity the more complicated you try to get.

All that said, this article feels detached from reality.

kylegalbraith··on How to harden GitHub Actions
Glad this got posted. It's an excellent article from the Wiz team.

GitHub Actions is particularly vulnerable to a lot of different vectors, and I think a lot of folks reach for the self-hosted option and believe that closes up the majority of them, but it really doesn't. If anything, it might open more vectors and potentially scarier ones (i.e., a persistent runner could be compromised, and if you got your IAM roles wrong, they now have access to your AWS infrastructure).

When we first started building Depot GitHub Actions Runners [0], we designed our entire system to never trust the actual EC2 instance backing the runner. The same way we treat our Docker image builders. Why? They're executing untrusted code that we don't control.

So we launch a GitHub Actions runner for a Depot user in 2-5 seconds, let it run its job with zero permissions at the EC2 level, and then kill the instance from orbit to never be seen again. We explicitly avoid the persistent runner, and the IAM role of the instance is effectively {}.

For folks reading the Wiz article. This is the line that folks should be thinking about when going the self-hosted route:

> Self-hosted runners execute Jobs directly on machines you manage and control. While this flexibility is useful, it introduces significant security risks, as GitHub explicitly warns in their documentation. Runners are non-ephemeral by default, meaning the environment persists between Jobs. If a workflow is compromised, attackers may install background processes, tamper with the environment, or leave behind persistent malware.

> To reduce the attack surface, organizations should isolate runners by trust level, using runner groups to prevent public repositories from sharing infrastructure with private ones. Self-hosted runners should never be used with public repositories. Doing so exposes the runner to untrusted code, including Workflows from forks or pull requests. An attacker could submit a malicious workflow that executes arbitrary code on your infrastructure.

[0] https://depot.dev/products/github-actions

kylegalbraith··on Disk I/O bottlenecks in GitHub Actions
Thank you for the kind words. We’re always trying to share our knowledge even if Depot isn’t a good fit for everyone. I hope the scripts get some mileage!
kylegalbraith··on Disk I/O bottlenecks in GitHub Actions
This is what we focus on with Depot. Faster builds across the board without breaking the bank. More time to get things done and maybe go outside earlier.

Trading Strategy looks super cool, by the way.

kylegalbraith··on Disk I/O bottlenecks in GitHub Actions
This is a neat idea that we should try. We've tried the `eatmydata` thing to speed up dpkg, but the slow part wasn't the fsync portion but rather the dpkg database.
kylegalbraith··on The Pain That Is GitHub Actions
Founder of Depot here. For image builds, we’ve done quite a bit of optimization to BuildKit for our image builders to make certain aspects of the builds fast like load, cache invalidations, etc.

We also do native multi-platform builds behind one build command. So you can call depot build —platform Linux/amd64,linux/arm64 and we will build on native Intel and ARM CPUs and skip all the emulation stuff. All of that adds up to really fast image builds.

Hopefully that’s helpful!

kylegalbraith··on The Pain That Is GitHub Actions
Just flagging that Depot now has macOS and Windows runners [0] as well if you're looking for even faster builds. I also recognize that constantly reevaluating runners isn't on everyone's priority list.

[0] https://depot.dev/docs/github-actions/runner-types

kylegalbraith··on The Pain That Is GitHub Actions
We're rolling out new pricing in the next week or two that should likely cover your use case. Feel free to ping me directly, email in my bio, if you'd like to learn more.
kylegalbraith··on The Pain That Is GitHub Actions
This was an interesting read and highlighted some of the author's top-of-mind pain points and rough edges. However, in my experience, this is definitely not an exhaustive list, and there are actually many, many, many more.

Things like 10 GB cache limits in GitHub, concurrency limits based on runner type, the expensive price tag for larger GitHub runners, and that's before you even get to the security ones.

Having been building Depot[0] for the past 2.5 years, I can say there are so many foot guns in GitHub Actions that you don't realize until you start seeing how folks are bending YAML workflows to their will.

We've been quite surprised by the `container` job. Namely, folks want to try to use it to create a reproducible CI sandbox for their build to happen in. But it's surprisingly difficult to work with. Permissions are wonky, Docker layer caching is slow and limited, and paths don't quite work as you thought they did.

With Depot, we've been focusing on making GitHub Actions exponentially faster and removing as many of these rough edges as possible.

We started by making Docker image builds exponentially faster, but we have now brought that architecture and performance to our own GHA runners [1]. Building up and optimizing the compute and processes around the runner to make jobs extremely fast, like making caching 2-10x faster without having to replace or use any special cache actions of ours. Our Docker image builders are right next door on dedicated compute with fast caching, making the `container` job a lot better because we can build the image quickly, and then you can use that image right from our registry in your build job.

All in all, GHA is wildly popular. But, the sentiment around even it's biggest fans is that it could be a lot better.

[0] https://depot.dev/

[1] https://depot.dev/products/github-actions

kylegalbraith··on Docker limits unauthenticated pulls to 10/HR/IP from Docker Hub, from March 1
This is just another thing in a laundry list of things from Docker that feel developer-hostile. Does it make sense? Sure, it might, given the old architecture of Docker Hub.

I'm biased (i.e., co-founder of Depot [0]) and don't have the business context around internal Docker things. So this is just my view of the world as we see it today. There are solutions to the egress problem that negates needing to push that down to your users. So, this feels like an attempt to get even more people onto their Docker Desktop business model and not explicitly related to egress costs.

This is why when we release our registry offering, we won't have this kind of rate limiting. There are also solutions to avoiding the rate limits in CI. For example, our GitHub Actions runners come online with a public unique IP address for every job you run. Avoiding the need to login to Docker at all.

[0] https://depot.dev

kylegalbraith··on Docker limits unauthenticated pulls to 10/HR/IP from Docker Hub, from March 1
As someone mentioned, GitHub has something to prevent this, but it's unclear (or at least undocumented) what.

We at Depot [0] work around this by guaranteeing that a new runner brought online has a unique public IP address. Thus avoiding the need to login to Docker to pull anything.

Subsequently, we also do the same unique public IP address for our Docker image build product as well. Which helps with doing image builds where you're pulling from base images, etc.

[0] https://depot.dev

kylegalbraith··on Show HN: Subtrace – Wireshark for Docker Containers
Do you envision going beyond just network calls from bpf?
kylegalbraith··on Launch HN: Promptless (YC W25) – Automatic updates for customer-facing docs
This idea is cool and well-scoped to a specific pain point that can be solved today. This is something that I think we need more of when it comes to YC batches.

However, you all should publish pricing before launching, and forcing me to book a call with you to use it is a nonstarter for me.

I don't want to get tied to this tool and then be charged for it in some weird way; give me your v0 pricing so that I can pay for it in a transparent way. As a fellow founder, I think you also know how little time I have for calls to check out demos for tools. So, just let me sign up and give it a spin.

kylegalbraith··on Ask HN: What country would you like to relocate to and why?
American here. Moved to France two and a half years ago. I speak French fluently as does my partner. It was probably easier for us because of that, but it still has it’s challenges. Integrating into a completely new culture where the language isn’t your mother tongue is exhausting at times.

Given all that. I’m quite happy not being back in the US. But I do long for an English first culture from time to time.

kylegalbraith··on Docker Bake is now generally available
It's cool to see bake go GA. We've been supporting bake at Depot [0] for a while now and it is a unsung hero when it comes to building multiple images in parallel.

We help many folks adopt it for their monorepo setups in particular. With Depot, folks can get the highly parallelized builds right out of the box, but bake takes it to another level by allowing you to define all your image builds in one place like an HCL, Compose, or JSON file. We've added some extra spice to fan out builds across multiple BuildKit instances [1].

If you're interested in bake and want a go-to guide, we wrote this blog post a while back: https://depot.dev/blog/buildx-bake-deep-dive.

[0] https://depot.dev

[1] https://depot.dev/changelog/2024-06-07-depot-cli-bake-multip...

kylegalbraith··on Thank HN: My bootstrapped startup got acquired today
Just want to say congratulations on the journey and reaching such a massive accomplishment!

Seeing a post like this on HN with all of the positive comments and thoughts is truly an inspiration.

kylegalbraith··on Show HN: I made a mini golf in my lunch time
This is a lot of fun. Thank you for making this.
kylegalbraith··on No Calls
This is an interesting read and take. I don't think it's applicable to everything because not everything fits neatly into "if I explain it, you will buy". This also cripples any kind of outbound motion, which for some businesses, they may never need so that's fine.

On an unrelated note, that squashed font look they're using everywhere is really killing my eyes.

kylegalbraith··on GitHub Linux ARM64 hosted runners now available for free in public repositories
Yeah, this is definitely lacking on our pricing page; thank you for flagging it.

We charge $0.08/minute for macOS runners [0] which has 8 CPUs, 24 GB of memory, and 150 GB of disk. They run with M2 chips, so the closest GitHub-hosted macOS runner is the arm64 one with 6 CPUs at $0.16/minute [1].

It's also worth mentioning that we charge by the minute but track by the second. Whereas GitHub actually rounds up to the closest minute. So a 10-second build on Depot is 10 seconds, and you don't get charged a minute until you've accumulated a minutes worth of build time.

[0] https://depot.dev/docs/github-actions/runner-types#macos-run...

[1] https://docs.github.com/en/billing/managing-billing-for-your...

kylegalbraith··on GitHub Linux ARM64 hosted runners now available for free in public repositories
This is exciting to see as arm64 is really a growing space, as we've seen since first launching our Docker image build acceleration [0]. Free for public repos is definitely a strong pull if you can live with some of the quirks.

Even with this, building multi-platform Docker images with fast persistent caching in GitHub Actions will still be slow in the worst case and tedious in the best case.

We've also expanded into GitHub Actions runners, bringing our fast caching and faster compute into the actual runner.

We've done some cool things like making caching and disk access faster using ramdisks, Ceph, and blob storage [1]. We're offering Intel, ARM, and macOS runners at half the cost of what GitHub offers to private repos. We're also focused on accelerating even more builds outside of the runner. [2]

[0] https://depot.dev/products/container-builds

[1] https://depot.dev/blog/introducing-github-actions-ultra-runn...

[2] https://depot.dev/blog/introducing-depot-cache

kylegalbraith··on Gitlab names Bill Staples as new CEO
One of the founders of Depot here. Always feel free to ping me directly (email in my bio) if you ever want to chat more about container builds in general.
kylegalbraith··on Creating a social photo frame from scratch
This is the type of project I still absolutely love reading about on HN. It feels like we use to see these types of things much more frequently than we do now. But I’m sure that is just my own browsing habits changing.
kylegalbraith··on Amazon S3 now supports the ability to append data to an object
I got excited until I saw the one zone part. That is a critical difference in terms of cost.
kylegalbraith··on London, Paris, Seoul Show Commuting Power of Fast Regional Rail
This was a great read. As an American who is currently living in France, I'm always blown away by how easy it is for me to get just about anywhere via train.
kylegalbraith··on Making EC2 boot time faster
Other founder of Depot here. AWS is pretty close to this idea with their Warm Pools [0]. But for our use case, they're just too slow to react to changes. We observed 60s+ to notice a change and actually start the machine. That doesn't work when we need to launch the machine as quickly as possible in reaction to a pending GHA job.

That said, I think this is a problem they could likely solve with that functionality, and we'd love to use it.

[0] https://docs.aws.amazon.com/autoscaling/ec2/userguide/ec2-au...

kylegalbraith··on Show HN: See your current Spotify song in the menu bar
It's very strange how these types of nice UX things seem to be lacking in big modern apps nowadays. I think we all know why, they aren't revenue drivers. But, surely this wouldn't be that hard for Spotify to do themselves.

Shout out to this project and all the others mentioned in this thread that are adding the niceties that seem to be missing.

← PreviousPage 2 of 6Next →