Oro Runtime

Build native applications from web projects.

Oro Runtime keeps the web programming model, then adds native windows, files, notifications, service workers, storage, background work, packaging, and signed updates.

Start learning Read the docs JavaScript APIs CLI GitHub

Start with the obvious commands

Guide

oroc run .
oroc run src/index.html
oroc config --describe window.width
oroc build . --platform=macos-aarch64
oroc install-app build/app

Start from a project, a single HTML file, or a JavaScript entry point. Add configuration when the app needs it.

Programming model

The web platform is the UI toolkit. Oro Runtime adds a deliberate native capability layer and a CLI workflow that turns a project directory into a native package.

Service workers

Route offline assets, custom protocols, and app-local requests through the same web model you already know.

Service worker guide

Files and notifications

Use sandboxed file APIs, file pickers, clipboard, notifications, and desktop integration where those capabilities create real user value.

Desktop integrations

Window management

Open secondary windows, send messages between windows, coordinate shared workers, and keep local app state predictable across native shells.

Windows guide

Docs map

A short path through the CLI, configuration, and the full JavaScript API surface.

Hello world, CLI input forms, reading path, and the runtime’s programming model.

Project layout, build and package, and windows and messaging.

oroc build, run, init, setup, install-app, config, env, versions, MCP, and update tooling.

oro.toml, .ororc, copy_map, and the build, webview, window, and permissions surfaces.

JavaScript APIs

Overview and exhaustive reference for application, OS, networking, storage, worker, and service APIs.

Manifest scaffolding, signing, verification, bundling, extraction, validation, and update servers.