ORBITAL//cache  public release Aug 2026, target

Storage that never takes an artifact's word for it.

CACHE is verified binary storage: a store for build artifacts that re-verifies every artifact each time it is fetched, so nothing tampered with ever enters your build.

For regulated teams

Referrals unlock launch rewards, including access ahead of the release.

Launches August 2026, target. At launch the free tier has every feature, gated on usage.
Docs one click awaySeats freeSSO included on every tier
One line to adopt
extra-substituters = https://cache.orbital.example
Measured claim · pending

This slot ships with one measured performance figure and a link to the methodology behind it. Benchmarks are being finalized for the public release; we do not publish numbers we have not measured.

01

Why verified storage

a

Checked on every fetch

Most artifact stores verify an upload once, then trust the bytes forever. CACHE re-checks the cryptographic signature every single time an artifact is served. If storage was tampered with after upload, the fetch fails instead of your build.

b

Addressed by content

Artifacts are named by what they contain, not where they sit. Identical outputs are stored once, references cannot silently change meaning, and two teams building the same thing share the same cache hit.

c

Drop-in

CACHE speaks the standard remote-cache interfaces of the tools you already run. Adopting it is one line of configuration; removing it is deleting that line. No migration project on either end.

02

Benchmarks

TBDCold fetch, p50
TBDWarm fetch, p50
TBDUpload throughput
TBDVerification overhead
StatusFigures publish with the August release. Each will be labeled measured and link to its basis.
MethodPublished, reproducible methodology: pinned hardware, pinned workloads, raw logs, and the harness to rerun the whole suite yourself.
03

Quickstart

1

Create an account

Sign up free, no credit card. One Orbital account covers CACHE and every other Orbital product.

orbital login
2

Add the config line

Point your build tool at your cache. That is the whole integration.

extra-substituters = https://cache.orbital.example
3

Build

Your next build pushes and pulls verified artifacts. Every fetch is checked before it is handed to you.

nix build # or: bazel build //...

Commands shown are illustrative until the docs publish with the release; the final quickstart ships alongside them.

04

Better together

ORBITAL//build

BUILD, the typed build system, uses CACHE natively: same account, same bill, one more config line. If you adopt BUILD later, it reads your real build graph and tells you, from your own data, where caching saves you the most.

See BUILD
05

Look for yourself

GitHubSource and issue tracker, in the open. ChangelogEvery release, public and dated. StatusLive service status and incident history. LicensesWhat is open source and under which license.

One config line away.

Shipping August 2026, target. Join the early-access list and be first in the door.

ORBITAL © 2026 GitHub · Changelog · Status · Licenses · Pricing