The official registry

One registry, one publisher

pack.openeng.ai is the official package registry of the Compiler.

  • Only OpenEng Labs publishes to it
  • Every version is signed
  • A published version never changes
  • The Compiler verifies every package before using it, whatever its host

Early preview

No official package is published yet. The registry lists a package only once it is published, so this page names package families, not packages.

Every package, official or privateby design

  1. Written in the language

    The Open Engineering Language, with no exceptions

  2. Shipped compiled and verified

    A private package ships without your source

  3. No bundled native code

    A package holds no code from another language

  4. No install scripts

    Nothing runs on your machine when a package is added

A package that talks to an outside system, such as a database or a model server, uses that system’s own interface, and you run that system.

Package families

Ten families of optional packages

These families are the designed scope of the official registry. A program carries only the exports it selects.

FamilyWhat it covers
Servers and APIsHTTP, gRPC, WebSocket and MCP servers.
Model providersLocal model servers, major cloud providers, and inference endpoints you run yourself.
Caching and messagingStreams, caches and message brokers.
Storage and databasesFiles on a local or mounted path, object storage, and SQL databases you run.
Vector storesIndexing and search of your knowledge for retrieval, in a database you run.
SkillsVersioned bundles of instructions, typed tools and functions.
Existing programs as toolsYour Python, JavaScript, Java or .NET programs and shell commands, with runtimes you provide.
RoboticsUnits, coordinate frames, sensor and actuator schemas, ROS 2 and DDS.
Scientific computingArrays, linear algebra, optimization, signal processing and automatic differentiation.
Quantum computingTyped circuits, simulators, and export to OpenQASM and QIR.

Private packages

Build one file, host it yourself

Your own libraries become packages that ship compiled, without your source. The official registry never hosts or lists them.

  1. Build

    oel package builds your library into a single package file.

  2. Host

    You host the file on your own release page, at any https address, or inside your project.

  3. Record

    Your project records the file’s address and fingerprint. Access tokens stay outside project files.

  4. Verify

    The Compiler refuses the file if it ever changes, and never treats it as an official package.

Repeatable builds

The same packages, every build

Package management is designed so that a build repeats exactly, with or without a network.

  • LockedOne manifest and one lock file for each folder of a project: pack.oel and pack.lock
  • OfflineThe lock pins exact versions, and nothing downloads when a program starts
  • AtomicAdding, updating and removing a package are safe to roll back
  • SelectiveYou select the exports you use, and only those ship

Resources

More on the Compiler

Request early preview access

Tell us which package families your application needs.