Kynver Runtime · Early access

An agent that works on your machines,
not somebody else's cloud

Most AI agents do their work inside a vendor's sandbox — your code copied up, their model bundled in, their off switch. The Kynver runtime turns that around: the agent runs on a box you own, with the model you choose, and you can stop it any time.

Package@kynver-app/runtime
Node.js≥ 24.11
Runs onmacOS · Linux · Windows (WSL)
AccessEarly access, by request

Five reasons it runs at your place

Where an agent runs decides who holds the keys. These aren't features on a roadmap — this is how the runtime works today.

01

Your machine, your rules

The agent runs on hardware you control — a desktop that stays on, a spare laptop, a server in your office. You bring it online with one command, and you can stop it at any moment. Nothing runs that you didn't choose to run.

02

Credentials and code stay local

The work happens where your repositories and logins already live. Your code isn't copied into a vendor sandbox to be worked on — the agent checks out branches, runs tests, and opens pull requests from your own machine, using access you already have and can revoke.

03

Bring your own model

Run the work through the coding-agent subscription you already pay for, or point the runtime at any compatible model endpoint — including one running entirely on your own hardware. Switch anytime; your agent's memory lives with you, not inside any one model.

04

Verified instructions

Before your machine acts on an instruction, it cryptographically checks that the instruction was really issued by your workspace. Anything that doesn't check out is refused — your box takes orders from you, and it can prove it.

05

A paper trail

The work leaves a verifiable record. Access to your agent's memory is written into signed, tamper-evident receipts you can export and check yourself, and the work itself ships as pull requests you review before anything lands.

Three steps to an agent online

Once your workspace is approved for early access, standing up a box takes three commands. The setup guide walks through each one.

01
📦
Install

One package from npm: npm install -g @kynver-app/runtime. Needs Node.js 24.11 or newer on a machine that can stay on.

02
🔗
Connect

Run kynver bootstrap. You approve the machine from your browser — no keys to paste — and it's linked to your workspace with its own scoped credential you can revoke at any time.

03
Start

Run kynver start. Your agent comes online and picks up work; you watch it live in the Command Center. Stopping it is as simple as pressing Ctrl+C.

A sandbox in their cloud, or a box of your own

Hosted agent sandboxes are convenient — and everything about them belongs to someone else. Running the agent on your own machine changes who's in charge of every part of the arrangement.

DimensionHosted agent sandboxesYour machine
Where the work runsIn their cloud, on machines you'll never seeOn hardware you own and control
The environmentAn ephemeral sandbox, rebuilt from scratch and thrown awayA persistent box that keeps its setup, checkouts, and tools between tasks
Your credentialsUploaded into someone else's environmentStay on your machine, where they already live
The modelWhatever comes bundledYour choice — the subscription you already pay for, or any compatible endpoint
The off switchTheirsYours — stop it at any moment
Early access

Put an agent on your own hardware

The runtime is in gated early access while we harden it on real workloads. Request access with a free Kynver account — every request is reviewed, and approved workspaces get the full runtime.

Runs on hardware you control — stop it any time
Your model choice: your subscriptions, or any compatible endpoint
Signed receipts you can export and verify