Privacy by architecture

Your code never leaves your machine.

OpenEng is local-first by design, not by policy. The browser is a thin client; all the work happens in an engine you run yourself. Every frame between your browser and engine is sealed end-to-end — the broker that relays them can't read a byte.

The model

Four guarantees, enforced by design.

Execution is local

Every command, cluster call, git operation, and database query runs in an engine on your own machine. There is no server-side execution of your work.

Sealed end-to-end

The browser and engine establish a shared key at connect, then seal every frame with a fresh, unique key — end-to-end, so the broker that relays the frames can’t read a single one.

No inbound port

The engine runs only on your own machine and binds no inbound port — it dials out to OpenEng’s broker. There is nothing on your network for anything else to connect to.

Your credentials stay yours

Git uses your credential helper, Kubernetes your kubeconfig. Secrets and tokens are resolved locally and never cross the wire.

What we never see

If it’s sensitive, it stays on your hardware.

There is no telemetry of your work and no server-side copy. Every frame between your browser and engine is sealed end-to-end — the broker that relays them can’t read a byte.

Run it yourself
Never leaves your machine
  • Your source code or repositories
  • Your terminal commands or output
  • Your kubeconfig, cluster data, or logs
  • Your databases and connection strings
  • API keys, passwords, or private keys

Under the hood

How the channel is sealed.

1

Handshake

On connect the surface and engine each generate an ephemeral keypair and exchange public keys (the only unsealed call).

2

Key derivation

A shared secret is derived and used to produce per-direction symmetric keys.

3

Per-frame seal

Every request and response frame is sealed with authenticated encryption — a fresh, unique key and nonce per frame.

4

Auth floor

Every call is authenticated end-to-end, and the schema carries no field for any secret, key, or password.

The same model powers all 5 apps — Terminal, Kubernetes, Data, Git, Chat.