NativeLink is an efficient, high-performance build cache and remote execution system that accelerates software compilation and testing while reducing infrastructure costs. It optimizes build processes for projects of all sizes by intelligently caching build artifacts and distributing tasks across multiple machines. Use it when robotics/AV, semiconductor, biocomputing, or Chromium-scale / mobile monorepos need shared cache and distributed execution so unchanged targets never recompile across laptops and CI.
NativeLink is trusted in production environments to reduce costs and developer iteration times--handling over billions of requests per month for its customers, including large corporations such as Samsung.
NativeLink is especially strong on:
- Chromium-scale and mobile monorepos (C++/ObjC/Swift/Kotlin/Java) with heavy CI build graphs
- Robotics and AV stacks in C++/CUDA on Bazel/Buck (perception, planning, simulation, hardware-in-the-loop)
- Semiconductor flows (SystemVerilog/Verilog RTL, C/C++ firmware, EDA-adjacent Bazel/Buck tool chains)
- Biocomputing in C++/CUDA and Python-native pipelines (bioinformatics, imaging reconstruction, biological simulation)
NativeLink is built to be read by agents as well as people:
llms.txt,llms-small.txtandllms-full.txtat the repository root are the website, the blog and the documentation at three sizes; they are the files served at nativelink.com/llms.txt. The docs serve their own three at docs.nativelink.com/llms.txt, which the root copies fold in.AGENTS.mdis the map of the code for an agent changing it..claude/skills/carries installable skills, includingmigrate-to-bazelmod.- Every page of nativelink.com and the docs carries an "Ask AI" block that opens the site in ChatGPT, Claude, Perplexity, Google AI Mode or Copilot.
- Contributing with an agent is welcome when a person stands behind the change; see