Hola 
Asking teams to do some work to gain access to solutions like remote caching or remote execution has always felt wrong to me, and I’ve had an appetite to address it for a long time. Tuist has been building infrastructure to enable that future, from our Kura caching technology for low-latency serving of cache artifacts to macOS & Linux compute capabilities packaged as a runner. However, it missed a technology that bridges infrastructure and existing projects, which has led me to tinker with what we called Once.
Once is a build system, like Bazel, Gradle, or swift-build. We are designing it so people, with or without the help of coding agents, can incrementally adopt those capabilities, from existing scripts down to their compiled build graphs, all while minimizing the changes that are required for that. The world of build toolchains is diverse, and while having organizations speak a single language, like Bazel, makes sense in some cases, we believe there’s room for bringing those capabilities to teams without having to change the language they use to define their projects, whether that’s an Xcode project, a Cargo.toml, or a Package.swift.
Coding agents pushed the cost of exploring this down, so I couldn’t resist the temptation. The project is in a very early stage, and need your help to iterate on it and make sure it works with any project shape out there. If you are intrigued by it and would like to support us in making Once a reality, send me a message here, on Slack, or just email me at [email protected].
Once is an empty canvas for us, and for a group of people like us, so obsessed with building great developer experiences, we are having a lot of fun rethinking how automation might look.