Company Runtime
Open source · Apache-2.0

The protocol underthe runtime,in the open.

The Runtime Protocol is how anyone asks a runtime to act on someone's behalf — and gets back proof that it happened. Its contract, reference implementation and official adapters are public, and depend on no product. Implement them, audit them, or replace any part.

See the repositoriesCompany-Runtime on GitHub
Fig. 01 — How the repositories fitDependencies flow one way
  1. Your productCompany Runtime is one
    registers
  2. runtime-adaptersOfficial adaptersbuilt with
  3. runtime-sdkReference implementationpinned to
  4. runtime-protocolSource of truth
Products depend on the SDK and adapters; the SDK is generated from a pinned protocol commit. The protocol never references a product — ours included.
The repositories

Three repositories, one contract.

Each one has a guide: what it is, what is inside, and how to use it, step by step.

01
Source of truth

Runtime Protocol

An open, vendor-neutral contract for asking a runtime to do something on someone's behalf — and getting back proof that it happened.

@runtime-protocol/spec
Read the guideGitHub
02
Reference implementation

Runtime SDK

The reference TypeScript implementation of runtime/0.1: validation, authority, policy, provider resolution, execution, evidence and receipts — with HTTP, MCP and events bindings.

@runtime-protocol/sdk
Read the guideGitHub
03
Official adapters

Runtime Adapters

Boundary translators that implement protocol capabilities on concrete systems — model APIs, team chat and issue trackers — built with the Runtime SDK.

@runtime-protocol/adapter-*
Read the guideGitHub
Guide · How adapters work

Any tool, one contract.

An adapter turns an agent's intent into an action on a real system — a vendor's API, a system inside your company, or a rule your team wrote — and brings back proof.

See how adapters work
  • For ownersHow the tools you already run — SaaS, internal systems, your own rules — become something agents can use.
  • For engineersThe request path, the container contract, and six steps from a tool to a published adapter.
  • Hosted or on-premiseThe same adapter image runs in our cloud or, under an enterprise licence, inside your network.
Where to start

Which one do you need?

Start from what you want to do. Most real uses combine the SDK with at least one adapter.

  • Understand or audit what a runtime may do on your behalf

    Read spec/0.1/protocol.md, then the semantic constitution.

    Runtime Protocol

  • Run a runtime inside your own service, or call a remote one

    createRuntime, then serve it over HTTP or MCP.

    Runtime SDK

  • Act on OpenAI, Anthropic, Slack, GitHub or GitLab

    Register the adapter as a provider and request the intent.

    Runtime SDKRuntime Adapters

  • Connect a system of your own

    Write a provider with defineProvider; the official adapters are the template.

    Runtime SDKRuntime Adapters
Status

Experimental.
In the open.

All three track the unreleased runtime/0.1. Nothing is on npm yet: install from Git at a commit, and pin it.

  • LicenseApache-2.0, for the protocol, the SDK and every adapter.
  • GovernanceHumans merge. Deterministic tooling enforces; AI only advises.
  • RuntimeNode.js 22.18 or later; TypeScript run natively.
  • Want the runtime?Company Runtime admits companies in small batches.Join the waitlist