BuildFetch (@buildfetch) header
BuildFetch (@buildfetch) profile picture

Build once, fetch a billion times. CI and Agents shouldn't waste time rebuilding same code again and again 📉 Free for Open Source. DM for trial credits.

United States
Joined April 2025
Photo by BuildFetch (@buildfetch)Photo by BuildFetch (@buildfetch)Photo by BuildFetch (@buildfetch)Photo by BuildFetch (@buildfetch)Photo by BuildFetch (@buildfetch)Photo by BuildFetch (@buildfetch)Photo by BuildFetch (@buildfetch)Photo by BuildFetch (@buildfetch)Photo by BuildFetch (@buildfetch)Photo by BuildFetch (@buildfetch)
👋 Proactively communicating: BuildFetch Systems are not affected by disasterous SSHHOLE vulnerability. - We have bruteforced password ssh attempts from internal network as per vulnerability spec with no positives - Our distributives are not musl libc based - Our clusters don't expose SSH to internet Our team continues to stay on high alert for the near future. Customer data protection and security of BuildFetch Systems are of utmost importance to us. Best regards, BuildFetch team.
*sshole is out if you run sshd on alpine, openwrt or any musl box with password auth on: update now official writeup: sshhole.com
1
2
14
54,578
Heads up: we will be performing DBs Optimizations across multiple clusters tonight. No downtime is expected, elevated latency might be observed. All updates available at status.buildfetch.com
1
256
Maintenance has been completed with zero downtime.
96
BuildFetch systems are NOT affected by: - PHP2Shell (we don't use PHP) - Railway secrets leak (we manage K8s clusters with different cloud providers) - Node.js RCE (we don't use Node.js in production) - GitLab RCE (we don't use GitLab) - HTTP/3 QPACK overflow (our load balancers have limits on header expansion and unaffected implementation of QPACK) - OpenCode (we don't use OpenCode) - eMudhra CA exposed private keys (we don't rely on this CA in the cert chains) In addition to automatic security scans and AI based vulnerability monitoring our team will stay on high alert for the near future. Thank you for your attention to this matter, CEO of BuildFetch Tommy Zinnatullin @its_tommy_zinn
2
8
872
We love @rustlang community Integrate our free Open Source build cache, it natively supports Rust via Sccache for Cargo and Bazel!
1
2
365
Impressive progress by Turborepo team!
Turborepo 2.11 is here! → Native support for Rust, Python, and Go → Up to 4x faster startup → ZERO ISSUES LFG → devEngines.packageManager support → nub and aube support → Omit dev dependencies when pruning nitter.gq/turborepo/status/21009…
188
Moon Remote Build Cache, ladies and gentlemen
We're releasing native Remote Build Cache support for Moon! It's free for open source.
4
357
We’re committing to Rust with io_uring for new microservices. We shall call them nano-services from now on with these tiny resource footprints
We have rewritten first production microservice at BuildFetch from Kotlin JVM to Rust… Less than 1 damn megabyte of memory for fully operating pods in Kubernetes! It has ClickHouse client, JSON & YAML serde, HTTP server we went straight with Compio (io_uring) instead of Tokio (epoll), few third-party HTTP libraries based on reqwest (Tokio), logging, metrics, basic crypto (SHA-256, HMAC, TLS) and so on. A bit of release-build optimizations, we build it via Bazel by the way: rules_rust + rules_oci, and voila! This isn't microservices anymore, it's nanoservice territory. And hey, if we had a Monolith instead of 15 separate microservices in a monorepo this would have been much much harder to pull off. And of course thank god AI models can deep research everything upfront, they code well in Rust, rustc error checking is extremely good for AI loops. The whole process took about a week of late night work in-between other product tasks, largely because we kept researching all necessary Rust libraries and other building blocks for months prior to actual migration. As technical CEO I'd say: Organizationally, just skip Go migration, no benefit in using less expressive and less type-safe language with Garbage Collection that will ruin tail latency anyway and result in bigger runtime memory footprint. Especially with coding agents. That said, there are things that drive me crazy with Rust, like this is ridiculous: - &str - &'static str - String - &mut String - &String - That's not even all! Also not the biggest fan of Rust async, coming from years of Reactive Programming. But nothing comes close to Rust in ecosystem, quality of tooling, type-system, etc for a native no-GC runtime. Zig is just too risky right now, current leadership is questionable and we don't have time to re-create all basic libraries. Maybe in few years, we will keep an eye on it for sure.
3
212
Small refinements to Setup page, less fields to fill, little bit of product info to make decision easier. Single sign-on via OAuth and SAML is in progress too The complication is that we need SSO to work both in Cloud and On-Prem the same way 🫠
1
1
4
2,427
Buildbarn Remote Bazel Execution joins BuildFetch first-class integration lineup today! Your Buildbarn owns Execution, BuildFetch owns the Cache — in Cloud and On-prem. While unlocking native support for Remote Cache in over 10 other build systems for Backend, Frontend, Mobile and AI/ML projects for the entire Org. Buildbarn Remote Cache support is free for Open Source projects. We believe quality infrastructure software is interoperable. This is our current take on Bazel Remote Execution and Remote Cache puzzle for our big customers already critically dependent on Buildbarn. It is a long term commitment, we will support this as long as it is technically reasonable.
1
1
3
676
Teams should not throw away hundreds of thousands of dollars of expensive engineering investments into Buildbarn while moving Remote Cache to BuildFetch to benefit from our extremely fast RAM + NVMe + SSD storage, observability, cloud regions. In such setup you get best of both worlds: almost stateless deployment of Buildbarn to maintain and leading class performant and scalable BuildFetch Cache platform whether in Cloud or On-Prem.
1
39
Build AI labs faster and type-safer (looking at you @typesafeai 👀) We support Nvidia CUDA GPU kernels Remote Build Cache in both C++ and Rust: ccache, sccache and Bazel
Introducing CUDA Rust! CUDA Rust lets you write GPU kernels natively in Rust, not just launch them from it. Two paths: cuda-oxide for SIMT kernels compiled to PTX, and cutile-rs for Tile-based programming on stable Rust. Both can catch aliasing errors at compile time. Technical blog: nvda.ws/4hm1bHS
7
205
Buck2 gets first-class BuildFetch Cache support today with: - End-to-end integration tests - Dedicated cache metrics, project type and documentation
We are releasing Buck2 Remote Cache support today 🦌
6
249
As part of preparation for compliance audits, BuildFetch now provides public Systems Status page. Externally tracked uptime from multiple regions at 30s intervals. Available at status.buildfetch.com
1
3
215
Our dashboards aren't just real-time across multi-region clusters We also render the data with attention to details 🌊
Small detail about BuildFetch project dashboard graphs: we render graphs/bars with relative transparency When you have 550 requests of type A in the same bucket as 6k requests of type B, type B matters more We calculate relative transparency and render all data points at the same time with visibly different importance This applies to Cache Reads / Write smooth graphs as well as Cache Hit Ratio bars Small details matter!
2
208
We're releasing native @Turborepo Remote Cache support today. It's free for Open Source projects. Setup is very smooth: set BuildFetch Url and Token in Turborepo config and get up to 90% faster builds and lower CI costs. BuildFetch Cache now supports 8 build tools, a new tool every week. Unified Remote Cache platform in cloud & on-prem. Try at buildfetch.com
1
1
2
5
10,854