Browse the documentation

Early preview

Runtimes and adapters

An adapter knows how to bundle one kind of application with its runtime at build time, and how the supervisor launches it at run time. You choose it with workload.adapter in oee.yaml, or let oee init --lang auto detect it.

The adapter matrix

RuntimeBuild inputsHow oee build packages itHow oee-stub runs it
Native binaries (Go, Rust, C, C++)A compiled ELF, PE (.exe) or Mach-O executableCompresses the binary with zstd into segment 4; segment 3 is empty (0 bytes).Launches the binary from the verified runtime path (or memfd on Linux when configured), forwarding stdin, stdout, stderr, environment variables and command-line arguments.
Python (3.10 to 3.13)A .py entry point, .whl wheels, requirements.txt, pyproject.toml, or a full directory (for example uvicorn, FastAPI or Celery)Resolves dependencies deterministically and bundles a relocatable python-build-standalone interpreter with its site-packages into segment 3.Sets PYTHONHOME to the read-only extracted runtime and PYTHONNOUSERSITE=1, isolating it from host Python packages, and launches your command, such as python -m uvicorn app.main:app.
Java and Kotlin (JVM) (17, 21, 25)A fat .jar, a .war, or a modular JAR directoryRuns jlink and jdeps at build time to assemble a minimal stripped JRE (about 35 to 50 MB) in segment 3.Runs the bundled java with container- and sandbox-aware heap sizing (-XX:MaxRAMPercentage) and clean SIGTERM shutdown-hook support.
Node.js, Deno, BunA .js, .mjs or .ts entry point, package.json with its lockfileEmbeds a static Node.js or Deno runtime binary in segment 3 and a deterministic node_modules bundle in segment 4.Launches the bundled runtime with module resolution rooted inside the Executor bundle directory.

Detection

oee init detects the project from its files and scaffolds the manifest:

File foundDetected as (--lang)
pyproject.toml or requirements.txtpython
go.modgo, a native binary
pom.xmljava
package.jsonnode

Choose explicitly with oee init --lang <auto|python|go|java|node|binary>; binary wraps any compiled executable.

Passing everything through

Whatever the runtime, the wrapped application sees what it would see if you started it directly:

  • Arguments. With workload.passthrough_cli_args: true, arguments given to the binary reach your application.
  • Environment. Environment variables pass through, except exit-event secrets that the Executor scrubs from the guest (scrub_from_guest_env, on by default).
  • Standard streams. stdin, stdout and stderr are forwarded and flushed on stop, so final log lines are never truncated.
  • Exit codes. On a normal exit, the application's own exit code (0 to 255) is passed on unchanged.
  • Workers. Multi-worker spawning works as usual; every worker belongs to the supervised process tree.

A Python example

workload:
  adapter: "python"
  python:
    version: "3.12"
    requirements: "./requirements.txt"
    bundle_paths:
      - "./app"
      - "./configs"
  entrypoint: ["python", "-m", "uvicorn", "app.server:api", "--host", "0.0.0.0", "--port", "{{port}}", "--workers", "4"]
  passthrough_cli_args: true
  working_dir: "."

oee.yaml reference lists every key of workload.