we built kache because our ci was spending more time moving cached artifacts around than actually building.
it's a build cache that doesn't double-buffer. artifact bytes go straight to object storage and come back without a copy through memory in between. dependency-driven prefetch warms the closure you're about to need instead of waiting for misses. runs direct-to-s3 or fully self-hosted, and degrades gracefully when the remote is down instead of falling over.
rust, open source, at 0.5 now. one of the releases along the way was community driven, which is the part i'm most happy about.
would love for your feedback and tell us where it breaks.
we built kache because our ci was spending more time moving cached artifacts around than actually building. it's a build cache that doesn't double-buffer. artifact bytes go straight to object storage and come back without a copy through memory in between. dependency-driven prefetch warms the closure you're about to need instead of waiting for misses. runs direct-to-s3 or fully self-hosted, and degrades gracefully when the remote is down instead of falling over. rust, open source, at 0.5 now. one of the releases along the way was community driven, which is the part i'm most happy about. would love for your feedback and tell us where it breaks.
[dead]