Early beta Local-first AI employee

On your machine. The work stays in the room.

An AI employee that sees your calls, mail, and files, drafts the next step, and waits. Local by default. Any model you want. Starting with the hour after the meeting.

Cloud from $5/mo
Connector marketplace
Free local app
K-AI
Call - 2026-08-19 18:49 Agent: Review emails from the last 24 hours Share

Listening to your call

Live transcript is being captured.

You: Get the recap out today — owners and dates.

Them: Yes. And triage the inbox after.

You: Pull need-to-respond from the last day. Archive the rest.

Them: Fine. Draft it here. Don’t send until I look.

You: Draft the follow-ups. I’ll review before anything sends.

Call ended — generating meeting notes…

Worked · 3 steps

Meeting notes are ready. Summary saved · 2 action items · 2 memories stored

Call Listen ran on the machine. Drafts are waiting.

  • Review emails from the last 24 hours
  • Draft the recap email

Review emails from the last 24 hours. Draft the one that needs a reply.

Get email thread
{"account":"local","range":"24h"}
Get email thread
{"account":"local","unread":true}

Worked · 3 steps

Here are the threads from the last 24 hours:

One thread needs a reply. Draft is open on the right. Nothing sent.

Font Size B I S Notes

Call - 2026-08-19 18:49

Live transcript

You: Get the recap out today — owners and dates.

Them: Yes. And triage the inbox after.

You: Pull need-to-respond from the last day. Archive the rest.

Them: Fine. Draft it here. Don’t send until I look.

You: Draft the follow-ups. I’ll review before anything sends.

Call - 2026-08-19 18:49

Call Listen ran locally. Action items extracted. Drafts waiting — nothing sent.

Email review request

  • Summarize mail from the last 24 hours
  • Split need-to-respond from archive

Next steps

  • Review emails from the last 24 hours — You
  • Draft the recap email — You

Transcript

You: Start Call Listen. After this, pull the asks and draft the follow-ups.

Undo Copy
Replying in thread: Recap — Aug 19
Font Size B I S

To the room

Subject Recap — Aug 19

Quick recap from the call. Owners and dates below — reply if I missed something.

Still open:

  • Inbox triage — you, today
  • Recap to the room — you, today
  • Vendor invoice — already closed
  • Standup notes — archive

Drafts stay here until you send them. K-AI does not.

Undo Copy

Bring your own models

OpenAI
Anthropic
OpenRouter
Ollama
llama.cpp
vLLM

The first job

Call ends. Drafts are waiting.

01

Listen to the call

Audio and transcript stay on the machine.

02

Extract what matters

Action items, not a recap you never open.

03

Draft the execution

Email and code, queued for you. Nothing ships until you approve.

04

Same desk underneath

Chat, mail, files, and agents — one desk, not five tools.

What it is

An employee.
On your computer.

Allowed

On the data

Calls and client files that never get a DPA. Already in the room.

Routed

Any model

Local when it must stay — and when you do not want a token bill. Claude when the job is hard.

Gated

You approve

Drafts, not autopilot. Same rule for mail and for the Cursor connector.

Explore

See it in the app

Hover to play — recordings from the desktop workspace.

Call → Actions
Marketplace
Agent Execution
Workspace
Documents
Agentic Browsing

Compare

They hired a chatbot.
The work is still there.

Granola

  • Clean summary
  • You still write the email
  • You still write the change

Claude

  • A plan, if you paste it
  • The context is the problem
  • Lives in their cloud

Cloud hire

  • A real employee
  • In Slack, on their servers
  • The room still cannot go there

K-AI

  • Hire sits on your disk
  • Drafts the work. Waits.
  • Review before ship

Cloud notes

  • Audio on their servers
  • Cloud-only
  • Vendor retention policies

Chat UIs

  • Self-hosted data
  • No call listening
  • No execution loop

K-AI

  • Calls on your disk
  • Local by default
  • Cloud replica sealed on-device

IDE agents

  • Strong in-editor agent
  • No call layer
  • Context starts in IDE

Capture

  • Always-on recording
  • General purpose
  • No codebase context

K-AI

  • Call → code pipeline
  • Memory across calls + files
  • Local models or APIs

Control

Local by default.
Cloud sealed on-device.

01

Your machine

  • Call audio stays local
  • Local models: no per-token bill
  • Works offline

02

Sealed Cloud

  • Encrypted on your device before it leaves
  • We do not hold the key
  • From $5/mo

Start

Live in minutes

01

Open Cloud or download

Use the browser workspace — or the Mac app for local models.

02

Connect mail if you want

Gmail, calendar, and Drive stay optional.

03

Review before it ships

Approve sends and purchases. Desktop is optional.

FAQ

Common questions

A local-first AI employee. It lives on your computer, drafts the next step, and waits for you to approve.

Notetakers stop at the summary. K-AI drafts the follow-up — email and code — for you to review. Calls stay on your machine.

Yes — live in beta. Call Listen and drafted emails are available today. The Cursor connector ships end of August.

The local app is free. Cloud is optional — sealed replica, always-on agents, billing. Meeting audio does not require it.

Preparing a public release. Email team@getk-ai.com for early access.

On your disk by default. Cloud sync is sealed on-device; we do not store the key with the replica. Schedules stay readable so jobs can fire. An unlocked cloud agent decrypts in memory for that job.

Local app is free. Cloud Basic $5/mo · Pro $20/mo. See our pricing page for details.

No per-token bill. Local models (Ollama, llama.cpp, vLLM) run on your hardware. You still pay electricity and the machine. Cloud credits are only if you route through K-AI Cloud or a third-party API key.

In beta, for teams that need weights that never leave their hardware. We help stand up an open-source stack on your machines — not a hosted fine-tune we keep. Email team@getk-ai.com.

End of August. Installs from the marketplace and pushes drafted code into Cursor for review.