A trust layer for AI agents

Give AI work.
Keep the keys.

Kerna connects your models and MCP tools, stops unreviewed actions, and leaves a readable receipt for every run.

Kerna terminal output showing workspace initialization and installation of the productivity pack.
Actual first-run output: a fail-closed workspace and curated productivity tools.

Install Kerna

Choose the path that fits your machine.

Every option installs the same verified runtime. Copy a command, then initialize a local workspace.

npm

npm install -g @premxai/kerna

Node.js 16+ on Windows, macOS, or Linux.

macOS / Linux

curl -fsSL https://raw.githubusercontent.com/premxai/kerna/main/install.sh | sh

Downloads the matching release binary and plugins.

Windows PowerShell

irm https://raw.githubusercontent.com/premxai/kerna/main/install.ps1 | iex

Installs into your user location and adds a PATH hint.

Source fallback

cargo install --git https://github.com/premxai/kerna --bin kerna

For unsupported platforms or source-based development.

Create your workspace

kerna init --ci --provider mock

Start with a deterministic demo provider and fail-closed policy.

Install productivity tools

kerna pack install productivity

Add local notes, calendar, weather, web reading, and optional search.

THE
CONTROL
PLANE
Local-first

Policies, receipts, and workspace data are yours to inspect locally.

Fail-closed

Ungoverned tools do not run. Consequential actions pause for review.

Model-flexible

Use the provider and MCP tools that fit the work, without giving up the guardrails.

One loop, made visible

Useful work should not require a leap of faith.

Kerna is not another chat window. It is the narrow control plane between an agent and the tools that can change your world.

01

Ask

Describe an outcome. Kerna discovers only the tools your workspace has explicitly allowed.

02

Check

Policy, scope, and budget are evaluated before an MCP tool ever runs.

03

Decide

Writes and external actions can stop in a local approval queue for a human choice.

04

Receipt

Review the outcome, decisions, and trace without treating an agent as a black box.

THE MOMENT THAT MATTERS

Approval is a feature

When work becomes consequential, the machine should ask.

Writing a note, creating a calendar event, or reaching an external service can be queued for a clear, one-time decision. If the answer is no, nothing happens.

Follow one run
Kerna notes connector risk card showing read-only tools and an approval-required add note tool.
Actual connector review: reads are visible, writes explicitly require approval.

First useful run

From install to a governed task.

Start in demo mode or bring your own provider. Curated packs keep local productivity tools close to hand.

ONBOARDING
IN THREE MOVES
01 / INSTALL

Put the runtime on your machine.

npm install -g @premxai/kerna
02 / CONNECT

Choose a pack, then inspect its risk.

kerna pack install productivity
kerna mcp risk google-calendar
03 / REVIEW

Run work and keep the receipt.

kerna run "Prepare my morning brief"
kerna trace last

Start with a bounded job

Make your first routine useful before making it automatic.

Explore read-first workflows for meeting preparation, research, and a calm daily brief.

Explore workflows