Build once, fetch a billion times.
Big Tech -grade software R&D infrastructure to Startups & Enterprises: Build Cache, Artifacts.
Free for Open Source.
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 https://t.co/H0SN4HKqTb
@dhh Hey David,
We'd love to provide unlimited remote build cache for all Omarchy builds and subprojects
Ccache, Sccache, Bazel, Nx, etc
Anything to speed up Omarchy releases and engineering work!
Side note: switching to Bazel would likely put Omarchy into its own R&D league
We've rolled out native Nx Remote Cache support
BuildFetch Cache now provides extremely fast build cache for
TypeScript and JavaScript frontend - backend Monorepos, React Native and Electron desktop apps.
Free for Open Source π«‘
BuildFetch Cache now supports Sccache projects https://t.co/lXHHpJWEDK
Free for Open Source.
Available now at https://t.co/jJ3dYHFYo4 both in Cloud & On-Prem.
Read more in BuildFetch Engineering Blog
https://t.co/b4yhG35W4X
Sccache Remote Storage is now natively supported by @BuildFetch Cache allowing long compilation tasks to be cached and reused across machines.
Free for Open Source!
Sccache includes support for caching the compilation of @rustlang, Assembler, C/C++, NVIDIA CUDA through nvcc and clang, and AMD ROCm HIP for AI and ML.
There are extremely complicated projects like @zeddotdev (written in Rust), as well as AI labs with @NVIDIAAI and @AMD native code that will benefit from native Sccache support in addition to our native support of @bazelbuild build system.
BuildFetch is moving quickly towards being a unified Cache system for the full stack: Backend, ML / AI, Frontend & Mobile.
Both in Cloud and On-Prem.
BazelCon 2026 schedule got published!
Most of the sessions are by Bazel Remote Cache & Execution companiesβ¦
Customer acquisition and Happy hour after should be fun π
BuildFetch Cache now supports Ccache.
Accelerating builds with distributed cache for demanding C-like toolchains.
It's free for Open Source, try it out at https://t.co/l2eMLWf4Gc
@relizarov Kotlin is indeed great.
All of our backend is currently Kotlin JVM, 16 microservices in 6 clusters to be exact.
Kotlin Native could outcompete Golang should JetBrains focus on that.
We have backlog items to switch hottest services to Rust + io_uring though!
Refined Landing Page experience shipped today.
BuildFetch makes infrastructure software
Naturally, we gravitate towards monospace fonts, clear graphics & technical data.
Under-the-hood details on system architecture, performance & security, all gets published here and in blog.
@i_mika_el@artem_zin Indeed!
Real-world p50 of ~6ms as of today.
After we ship ccache & sccache ~ next week, we will work on getting p50 to ~4ms, then all the way down to ~2-3ms by September.
Additionaly, we'll publish recurring open source benchmarks to back up our performance claims πͺ
Hi friends! Haven't posted much lately.
Because I went sleep at 4am, built a small team and we finally launching our first Distributed Cloud product β BuildFetch Cache.
Company registered just over a year and 10 days ago, great state of Wyoming actually issued the Certificate of Incorporation early morning of July 4th, 2025 πΊπΈ
We're starting public rollout, after a year of extensive development, internal and open source testing the platform is ready.
The company is "@BuildFetch", we do exceptional quality infrastructure software, cloud & on-prem.
Our first product is BuildFetch Cache β extremely fast, real-life observed p50 as low as 3ms by already running Cloud Projects,
It's a high-performance geo-distributed Remote Cache for Gradle & Bazel with ccache rolling out in few weeks and sccache after that.
- Allows build systems to store & reuse built task outputs for real-life observable speedup up to 90%
- When CI, engineers, AI agents build freshly rebased branches with BuildFetch Cache build completes in seconds because another machine already uploaded shared results of its hard work that took minutes
- Our own monorepo project routinely observes rolling 30 day cache hit ratios of over 90% dramatically saving on CI cost and boosting engineers
- In even bigger corporate projects with 100+ active engineers from my past Staff Infra SWE experience building without Remote Cache was pretty much a suiΡide mission, CI would timeout after hour+ jobs, developers would see 10+ minute builds many times per day
Product-wise BuildFetch Cache offers:
- Cloud version with unified user experience, automatic billing experience with Stripe, choice of cluster locations for best latency: US West and EU Central today, US East coming later this year
- On-premise deploy on any K8S environment of your choice: AWS EKS, GCP, Azure, DO, you name it, BuildFetch does not need any "DB as a Service" or "S3 as a service", we just need reasonable amount of 4vCPU 8GB+ machines with local NVMe and network SSD volumes and scale from there, competitors routinely cause $10k+/m bills for hardware they need, BuildFetch on-prem requires ~$1k-$3k/m with lower latency and higher throughput
- Real-time dashboards with byte-level precision
- Unlimited number of users on any plan, no "per seat" pricing
- Unlimited number of Projects on Cache Pro
- All resources can be used over the included plan limits with transparent pricing
- Gradle & Bazel Remote Cache supported today, ccache & sccache in few weeks, Turborepo & more after
Technology behind BuildFetch Cache:
- Distributed, replicated CAS storage utilizing tiered in-memory, server-mounted NVMe and network SSD storage with LUKS encryption at rest
- Low-latency, high-throughput bus bar networking, the more machines in given BuildFetch Cluster, the higher IO cluster can handle directly to users
- Encryption in transit & at rest for all DBs, files, etc. mTLS interconnect between clusters
- Leader β Many Followers eventually-consistent clusters topology, it already runs on different Cloud providers for different regions to avoid centralized failures and downtimes
- Every internal component is K8s native with no "Something as Service" dependencies for best in class performance and cost efficiency
- Each file is checked against its upload-time calculated SHA-256 on each GET request to ensure correctness for users
- Very large suite of constantly growing unit, integration and end-to-end automated tests that our CI and team grind through for every feature change
The C Corp is registered in Wyoming, US, I (Founder & CEO) live and work from beautiful state of Colorado as EB-1A Extraordinary Ability green card, previously held two O-1A talent visas. Last 10 years I worked in bigtech infra projects: Lyft, Juno, Yandex, NYTimes: network frameworks, reactive architectural layers, then exclusively on more massive CI/CD infrastructure, build systems, compilers, developer tooling, K8s, tons of open source.
---
I'm both excited and worried, gladly not because of the technical aspects of the product, living & trying to grow your family in US is very demanding, especially when you're starting a Cloud Infra startup.
BuildFetch Cache is just the first product of @buildfetch, later this year we will roll out BuildFetch Artifacts: Maven, NPM, Docker Registries and more with unmatched performance and ease of use.
I'll be writing more on all this, in fact I'm starting another big company later this year and then another next year, all with their own very different products π These endeavors will require quite large VC funding after we finish the prototypes. Likely ~10-20 people team spread across US and EU, if you do Rust β stay tuned and feel free to connect and tell what you specialize on, we're gathering pool of candidates for the teams.
π½