◍ Oam.js

A JavaScript and TypeScript runtime built on Rust and V8, aimed at TypeScript and MCP servers.

Beta. Oam.js runs real code today. Breaking changes are still possible before 1.0, and land in the changelog. From v0.18.0, releases are signed: a signed release manifest the installers verify, Authenticode on Windows, a self-signed identity on macOS (not yet notarized). See the repository for what is measured and what is deliberately different from Node.

What it is

Runs .ts, .tsx and .jsx directly, with no build step.
Node-compatible: the node: builtins, npm resolution and CommonJS interop.
Single binary, no runtime dependencies, fast to start.
Built for running MCP servers as sidecars.

How it compares

Oam.js is Node-compatible, not a Node replacement for every workload. Pick Node for native addons, the full ecosystem surface, or a long-lived production service today; Bun if single-process throughput is the axis you are optimising; Deno for its standard library and deploy platform. Oam.js is for running TypeScript and MCP servers — many small processes, where cold start and idle memory dominate. The numbers, with their denominators.

Install

macOS and Linux:

curl -fsSL https://oamjs.org/install.sh | sh

Windows:

irm https://oamjs.org/install.ps1 | iex

Both fetch the release binary for your platform, verify the binary's checksum (and, from v0.18.0, the release's signature), and install to ~/.oam/bin alongside the license and attribution files. No sudo.

Prefer to fetch it yourself, pin a version, or check the checksum before running anything? All downloads.

Docs

Debugging with the inspector, the diagnostic code reference, and the ODIF envelope — the pages the binary itself links to. The rest of the documentation ships in the repository, beside the code that has to stay true to it.