Our Terms of Use change on 1 December 2026, and our Privacy Policy and Subscription Agreement on 15 and 21 December 2026. The updates cover account holders, fraud and abuse prevention, including device checks at signup and login, optional sign-in text messages, Hosted Inference for Fleet organizations, how Kenaz connects to AI tools and platforms made by other companies, automatic memory capture, personal files, encryption, and what your organization’s administrators and team leads can see. Privacy Policy · Terms of Use · Subscription Agreement · About text messages · Questions: dpo@kameas.ai

FreeNo accountmacOS on Apple Silicon

The secure AI workbench.

Kenaz gives an AI agent its own virtual machine on your Mac, not the run of your machine. A profile sets what it can reach, policy checks what it does, and a signed ledger on your Mac records what happened.

Not on a Mac? The open-source Kenaz Harness runs on its own on macOS, Windows and Linux.

  • A VM for every workbench

    Agents and their tools run in a Linux virtual machine, with one folder you choose shared in.

  • A network you decide

    Allowlist or air-gap a workbench. The VM's firewall drops everything else and Kenaz shows you what it blocked.

  • Policy before action

    Every tool call is checked against Cedar policy before it runs, with five autonomy levels on top.

  • A record you can verify

    Workbench events and policy denials land in a hash-chained, Ed25519-signed ledger on your Mac.

Why a workbench

Agents are useful because they act. That is also the risk.

You can't see it

Which files an agent read, which commands it ran and where it connected are rarely shown to you.

Nothing contains it

An agent on your laptop runs with your credentials, your files and an open network.

Nothing records it

When something goes wrong, there is no record of what ran, which files it touched, or where it connected.

The workbench

A separate computer for each job you hand to an agent.

A workbench is a Linux virtual machine that Kenaz starts on your Mac from a profile and opens in its own window, with one tab per app. The agent works in there. The Kenaz desktop app runs on macOS 13 or later on Apple Silicon, and is free with no account.

01

Start from a profile

A profile is a saved recipe: which apps run inside, how much CPU, memory and disk the VM gets, which folder on your Mac is shared into it, which AI provider the Harness uses, and which network destinations it may reach.

  • Kenaz Harness, VS Code Server, Jupyter Lab, a terminal and a browser, each in its own tab
  • Provider keys stay in your OS keychain; the profile holds only a reference
  • Clipboard sharing is two separate switches, one for each direction
Profileresearch-1
Apps
HarnessVS Code ServerJupyter LabTerminal
Resources
4 CPU · 8 GB · 40 GB disk
Shared folder
~/work/churn-analysis
AI provider
Anthropic key in keychain

Egress tier

The VM reaches only the destinations allowed for this profile: endpoints you add, the hosts its apps and MCP connectors need, and an optional preset.

  • api.anthropic.com:443
  • github.com:443
  • registry.npmjs.org:443

Example profile. Rules are set in the VM's firewall when the workbench starts.

02

Policy is checked before anything runs

The Harness checks every tool call against Cedar policy first. Inside a workbench the VM is the boundary, so the agent has a shell by default and asks before a command no rule covers. An organization's Fleet policy can turn the shell off, and takes precedence over local defaults.

default

File reads and edits run without asking. Shell commands, network calls and destructive actions ask first.

PolicyCedar
// No MCP servers started through npx.
forbid (
  principal == User::"local",
  action in [Action::"add_recipe",
             Action::"spawn_recipe"],
  resource is MCPRecipe
) when {
  context.recipe_command == "npx"
};

A forbid rule wins at every autonomy level.

03

Keep a record that can't be quietly edited

The host keeps an append-only ledger of workbench events and policy denials. Each row is chained to the one before by its SHA-256 hash and signed with an Ed25519 key kept on your machine, so editing or deleting history breaks verification.

The Harness keeps its own hash-chained audit log of every prompt, response, tool call and permission decision. You can verify the chain and export it as JSONL, CSV or PDF.

Ledgerchain verified
RowKindDetailHash
#1824vm.spawnworkbench=research-13c8f…7b21
#1825egress.allowhost=api.anthropic.com9a10…4e0c
#1826egress.allowhost=github.com0f44…2cd8
#1827egress.denyhost=paste.eeb63e…18a9
#1828policy.denyaction=spawn_recipe7f22…d4e5
#1829vm.teardownworkbench=research-1c41a…09be

Example rows.

04

See what happened on your Mac

The desktop app runs an observer daemon, sigild, that records activity metadata on your Mac so you can see what happened in a session. It stores it locally and makes no network requests in its default configuration.

Observermetadata, on your Mac
SourceWhat is recorded
Filespaths, sizes, times
Processeswhat ran, and for how long
Terminal & gitcommands, repositories, branches
Clipboardtype and size, never contents
Typingkeystroke counts, never keys
App contextfrontmost app and window

Kenaz Harness

The agent is open source.

The Kenaz Harness is the agent runtime inside every workbench, and a standalone app you can run on its own. It is Apache 2.0 at github.com/kameas-ai/kenaz-harness. The desktop app and Fleet are closed source today.

Models

Your keys, or local models

Bring your own key for any of these, or run local models through Ollama. Keys stay in your OS keychain.

  • Anthropic
  • OpenAI
  • OpenRouter
  • AWS Bedrock
  • Azure OpenAI
  • Google Gemini
  • Ollama
  • OpenAI-compatible

Tools

MCP servers, with per-tool permissions

Built-in tools cover files, shell and web. Connect MCP servers for the rest; each server gets its own grant, and newly added ones ask every time.

On its own

A starter policy on your computer

Run outside a workbench, a fresh install reads files and edits inside the workspace without asking. Shell commands, network calls and writes outside the workspace ask first. You can loosen or tighten it.

Platforms

macOS, Windows and Linux

Signed installers for macOS and Windows. Linux builds are unsigned and best-effort. Free, with no account.

Architecture

Three layers, each with one job.

The desktop app is the control plane, the host keeps the record, and the workbench VM runs the agent.

L0

Desktop app

control plane
  • UI shellWails v3 · Preact
  • Workbenchesprofiles · lifecycle
  • PolicyCedar · org policy
  • Audit viewersigned · verifiable

launches the VM · applies policy

L1

Host Mac

record and runtime
  • Observer daemonsigild · Go
  • Audit ledgerSQLite · hash-chained
  • VirtualizationTart · Apple VZ
  • Image cacheworkbench images

events over vsock · egress filtered

L2

Workbench VM

where the agent runs
  • Kenaz Harnessagent · served UI
  • VM reportersigild · vsock
  • Workbench appsVS Code · Jupyter · browser
  • Egress filternftables allowlist
LayerTechnologyWhy
App frameworkWails v3 · Go + Preact/TSNative desktop, single binary, no Electron.
Local storeSQLite · WAL · modernc.org/sqlitePure Go, no CGo. Holds the observer events and the ledger.
Workbench VMTart · Apple Virtualization · NixOSA Linux VM per workbench, built from a Nix image.
AgentKenaz Harness · Go · MCPMulti-provider agent runtime, Apache 2.0.
AuditEd25519 · SHA-256 chainTamper-evident, independently verifiable.
PolicyCedar · nftablesAgent actions checked before they run; egress filtered in the VM.
FleetGo · Postgres · AWSHosted by Kameas. Self-hosting is on our roadmap.

On Linux there is a desktop build, but Kenaz does not start a virtual machine there: workbenches run as processes on the host.

Privacy

What stays on your machine, and the exceptions.

On your machine by default

Stays local unless you choose otherwise.

  • Observer events and the audit ledger
  • What's inside your workbenches and shared folders
  • Model provider keys, in your OS keychain
  • Harness conversations and memory, unless you sign in to Fleet and sync is on

What can leave, and when

Every exception, written down.

  • Model calls go to the provider you choose, with your key
  • Signed in to Fleet: device enrollment, organization policy checks, and workbench profile reports, which include profile names
  • Fleet telemetry: usage summaries (counts, timings, cost) that members turn on or their organization requires, never prompts or code
  • On paid plans, settings, context and memory sync as described in the Privacy Policy
  • Update checks: a plain request to downloads.kameas.ai with no account or device ID
  • Inside a workbench, its egress tier decides which hosts the VM can reach. Web pages shown from workbench apps load in the desktop window, outside the VM's firewall

Read the code

The Kenaz Harness, which runs your agents, is open source at github.com/kameas-ai/kenaz-harness. What Fleet receives is listed field by field in the Telemetry Disclosure.

For teams · Kameas Fleet

One policy across every workbench, and a clear picture of adoption.

Fleet is the optional, paid service behind Kenaz. Everything on your machine keeps working without it.

Workbench policy

Push workbench policy and Cedar rules to every device, see which devices applied it, and lock down in an emergency.

Adoption analytics

Adoption tiers, session counts, tool mix, as team totals or per person, where your organization has it on.

Usage and cost

Model usage and cost by team, or per person where your organization has it on.

Audit

An audit log of administrator actions in Fleet, next to each device's signed workbench ledger.

Kameas hosts Fleet. Self-hosted and dedicated deployment is on our roadmap. Compare every plan.

Questions

Before you download.

Do I need an account?

No. The desktop app and the Harness are free and work without one. Kenaz offers a sign-in on first launch; you can skip it and sign in later. An account matters only for Kameas Fleet, which is paid.

What does it run on?

The desktop app needs macOS 13 or later on Apple Silicon. There are no Windows or Intel Mac builds of the desktop app. The Kenaz Harness runs on its own on macOS and Windows; its Linux builds are unsigned and best-effort.

What do workbenches need?

On a Mac, workbench VMs run on Apple's Virtualization framework through Tart. Kenaz offers to install Tart the first time you open a workbench. Tart has its own licence; see the first-run guide.

Can a workbench be cut off from the network?

Yes. On the air-gapped tier all outbound traffic from the VM is blocked. On the allowlist tier it reaches only the destinations the profile allows. One thing to know: web pages shown from workbench apps load in the desktop window, outside the VM's firewall.

How do updates work?

Kenaz does not install updates itself. It checks the release list on downloads.kameas.ai at most once a day and tells you when a newer version is out. The check sends no account or device ID, and you can turn it off.

How does the Fleet trial work?

Pro and Team start with a 14-day free trial. We collect a payment method at signup and don't charge it during the trial; cancel before it ends and you pay nothing. Full terms are on the pricing page.

Give your agents a workbench.

The desktop app and the Harness are free with no account. Pro and Team add Kameas Fleet and start with a 14-day free trial: we collect a payment method at signup and don't charge it during the trial; cancel before it ends and you pay nothing. Need a custom enterprise rollout instead? Talk to us.