Skip to content
Roadmap

Where we're headed

OCX is under active development. Here's what we're building and what's coming next.

In Progress Planned Shipped

Composable Packages

Multi-layer OCI artifacts that let publishers compose packages from reusable building blocks. Share stable internals across releases and apply infrastructure-specific patches without rebuilding from scratch.

Multi-layer artifacts
Infrastructure patches
Shared internals
Delta downloads

Dependencies

Packages declare dependencies on other packages, enabling automatic resolution for composable toolchains. A Java application can require a specific JRE version, and OCX resolves the full graph.

Dependency resolution
Dependency declarations
Transitive constraints
Composable toolchains

System Requirements

Packages declare required host capabilities like glibc version, musl compatibility, or specific CPU features. OCX validates the host before installation and selects the best matching variant.

Package variants
Host capabilities
Pre-install validation
Variant fallbacks

Referrer API

Attach SBOMs, signatures, and attestations to existing releases using the OCI Referrers API. No need to re-publish a package to add supply-chain metadata after the fact.

OCI referrers
SBOM attachment
Post-publish attestations
Signature discovery

Interoperability

First-class integrations with the tools and platforms where developers already work. From build systems to CI pipelines to local development environments, OCX meets you where you are.

Bazel module
GitHub Actions
DevContainer features
Shims & lazy loading
Air-gap export/import

Hardening

Stabilizing the CLI interface and package metadata format for long-term reliability. Improved error messages, better documentation, and a commitment to backwards compatibility.

Stable CLI semver
Schema validation
Idempotent PATH setup
Relocatable symlinks
API documentation

Get Involved

OCX is open source. If any of these milestones matter to your workflow, we'd love to hear from you.