How the registry is published

The registry is a set of static files that OpenEng signs. It has no accounts, no upload interface and no search service.

  • Signed versions

    Only OpenEng publishes to the official registry; every version is signed, and a published version never changes.

  • Verified before use

    The Compiler verifies every package before using it, whatever its host: its fingerprint, its contents and how it was built.

  • No package listed yet

    No package has been published, so this site lists none. A package appears here only after OpenEng has published and signed it.

Official and private packages

Official packages, published by OpenEng

Package families of Compiler 1.0.0: servers and APIs, model providers, caching and messaging, storage and databases, vector stores, skills, running your existing programs as tools, robotics, scientific computing and quantum computing.

One language for every package

Every package, from OpenEng or from you, is written in the Open Engineering Language and ships compiled and verified, with no bundled native code and no install scripts.

Your own private packages

You build a package with the oel package command, which produces a single package file.

  • You host that file yourself: on your own release page, at any https address, or inside your project.
  • Your project records the file's address and fingerprint, and the Compiler refuses the file if it ever changes.
  • Access tokens for your private host stay outside your project files.
  • The official registry never hosts or lists private packages.

Builds that repeat

  • Your lock file pins the exact versions you built with, so builds repeat, even offline, and nothing downloads when an app starts.
  • Adding, installing, updating and removing packages are atomic and safe to roll back, and a package never runs an install script.

Early preview — message us for access

The Compiler is in early preview. Write to us and name the platform you need.