Registry formats
Every format below runs in the same self-hosted OrbitalReg instance, under the same projects, roles, retention policies and append-only audit log, and 36 of them are generally available. Each card says exactly what the adapter supports today, transcribed from the format support matrix, including the caveats.
Format guides
Maven
Deploy releases and snapshots, proxy Maven Central with release-hold and PGP verify-on-pull, match every JAR against advisories.
Helm
Classic index.yaml and OCI side by side in one repo, helm cm-push compatible, signed-chart provenance, charts next to the images they deploy.
npm
Publish scoped packages, proxy registry.npmjs.org, check every tarball against advisories, steer ranges to clean releases and answer npm audit yourself.
PyPI
twine upload, a cached pypi.org behind one index URL, release-hold and safe versions, and no more --extra-index-url dependency confusion.
Docker / OCI
Push your images, cache Docker Hub, GHCR and Quay, keep cosign signatures and SBOMs as OCI referrers, scan image layers with Trivy and Grype.
Terraform
A provider network mirror and private module registry. Mirror registry.terraform.io once, run terraform init air-gapped.
Formats whose clients read a generated repository index, which OrbitalReg builds and serves.
Formats with a REST/JSON registry protocol. The native client talks to OrbitalReg as if it were the public registry.
Formats with their own storage model: container images, Go modules, Git LFS and Terraform.
Artifacts that are not classic packages but still need versioning, scanning and access control.
Real adapters with integration-test coverage and a narrower feature set than the formats above.
Free forever · no contract
One Go binary, Postgres and S3-compatible storage. Coming from Artifactory or Nexus? The migration CLI moves repositories across formats in one plan.
