Same tools.
Every machine.
ocx.toml lists your tools; ocx.lock pins each to a digest. Laptops and CI on Linux, macOS and Windows run the same version, served from the registry you already run.
Could not load this.
Same project. Three Node.js versions.
apt-get install nodejsNode 18 · end of life since 2025apt-get install nodejsNode 20 · end of life since Aprilbrew install nodeNode 26 · whatever is newestwinget install OpenJS.NodeJS.LTSNode 26 · the current LTSnvm installper shell, from .nvmrc · no Windowsuses: actions/setup-node@v7one more syntax per CI vendorOne line in ocx.toml. Node 24 on macOS, Linux, Windows and CI.
Locked once. Same version on every machine.
One ocx.lock covers every platform, so the Linux CI runner, the Mac laptop and Windows match. Digests move only on ocx update, and ocx exec refuses a stale lock.
| ocx.toml · node = "ocx.sh/nodejs/node:24" | |
|---|---|
| ocx.lock | |
| linux/amd64 | → sha256:e8c4…12bf ← CI runner |
| linux/arm64 | → sha256:2334…057c |
| darwin/arm64 | → sha256:1e34…e370 ← laptop |
| windows/amd64 | → sha256:8e7e…9214 |
| tag 24 floats · digests stay put | |
Ship tools where your images live.
Push tools next to your container images. The logins and permissions you already have apply, with no package server to stand up.
- GitHubghcr.io
- GitLabregistry.gitlab.com
- Artifactorycloud or on-prem
- Amazon ECR*.ecr.aws
- Azure*.azurecr.io
- Harborself-hosted
Automation-first.
JSON output, clean environments, composable commands and an exit code per failure. Bazel, CMake, Python and CI read the same ocx.toml and ocx.lock.
Could not load this.
Know what you run. Even offline.
ocx never runs package code at install. Signature checks and SBOMs, by digest. Pull once, then run with no network.
Could not load this.
Pin once.
Run everywhere.
ocx is in early development. The CLI is functional but APIs may change.