Once Docs
Guide Reference
Overview
Start Here
Overview
Getting Started
Why Once
Coding Harnesses
Scripted Automation
Overview
Caching
Manual Cache Access
Typed Graph
Overview
Ecosystems
Configurations
Testing and Scheduling
Linting
Toolchains
Android
Apple
Xcode Projects
Build on Linux
Swift Packages
Bazel
C and C++
CMake
Container Images
Elixir
Go
Kotlin
Nx
React Native
Rust
Zig
Local Execution
Memory Limits
Unchanged Builds
The Sound of Your Build
Terminal Integration
Infrastructure
Overview
Become a Provider
Artifacts
Connect A Project
Remote Execution
Triggers (Experimental)
Buildkite
Microsandbox
E2B
Daytona
Tuist
Memory
Overview
Evidence
Language Libraries
Overview
Rust
Swift
Ruby
JavaScript
C

Once documentation

Build once, then reuse the result. Start with a working project or one script, verify it locally, and share the cache when you are ready. No account is needed for your first build.

Getting Started

Install Once, reuse a script result, and restore an output in a self-contained example.

Why Once

Understand the model behind reusable automation.

Scripted Automation

Add caching to the scripts you already trust.

Typed Graph

Discover native projects or declare targets with explicit dependencies.

Infrastructure

Share cached results with your team or move suitable work to a sandbox.

Reference

The manifest, commands, and target kinds.