Early preview
Compiler packages
The core stays lean. Servers, model providers, storage and whole domains are optional packages: signed ones from the official registry, and private ones you build and host yourself.
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
Written in the language
The Open Engineering Language, with no exceptions
Shipped compiled and verified
A private package ships without your source
No bundled native code
A package holds no code from another language
No install scripts
Nothing runs on your machine when a package is added
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.
| Family | What it covers |
|---|---|
| Servers and APIs | HTTP, gRPC, WebSocket and MCP servers. |
| Model providers | Local model servers, major cloud providers, and inference endpoints you run yourself. |
| Caching and messaging | Streams, caches and message brokers. |
| Storage and databases | Files on a local or mounted path, object storage, and SQL databases you run. |
| Vector stores | Indexing and search of your knowledge for retrieval, in a database you run. |
| Skills | Versioned bundles of instructions, typed tools and functions. |
| Existing programs as tools | Your Python, JavaScript, Java or .NET programs and shell commands, with runtimes you provide. |
| Robotics | Units, coordinate frames, sensor and actuator schemas, ROS 2 and DDS. |
| Scientific computing | Arrays, linear algebra, optimization, signal processing and automatic differentiation. |
| Quantum computing | Typed 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.
Build
oel packagebuilds your library into a single package file.Host
You host the file on your own release page, at any https address, or inside your project.
Record
Your project records the file’s address and fingerprint. Access tokens stay outside project files.
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.oelandpack.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
Compiler overview
What the Compiler is, how you write, check, build and run a program, and where programs run.
Features
The designed scope by area: language, agents, models, services, tooling, deployment and devices.
Agents
Agents, nodes and edges as typed source files, with teams, subagents and built-in guardrails.
Compiler 1.0.0
What the early preview covers today, area by area, and how to follow each update.
Get the Compiler
Early preview access by message, per platform. No public download is published.
Questions and answers
Platforms, access, packages, security reports and support, answered in one place.
Documentation
The language guide, agents, packages, platforms and the command-line reference.
Release notes
The record of every Compiler release, on the releases site.
Request early preview access
Tell us which package families your application needs.