Say hi 👋 to the new Tuist.
Today we are rebranding Tuist. We started as a small command line tool that made Xcode projects easier to reason about, and somewhere along the way we turned into build infrastructure, so the brand stopped matching what the company had actually
As teams write and validate more code in parallel, from laptops to CI to increasingly AI agents, build systems lean harder on the network for cache. Most caching backends weren't built for that.
So we built our own: Kura 蔵 (Japanese for "storehouse"), a multi-build-system cache
@buildkite has been a reference for us on how to build a great product, and therefore we couldn't be more excited to share that we added support for plugging our runners into it:
Teams try to fix slow builds by throwing hardware at them. It works for a while, then the build is slow again and nobody can say why.
Build performance behaves like physics. We wrote down what we've learned about graphs, caches and queues 🧵
