CloudketerWORKFORCE
Keter Workforce

Every machine.
One workforce.

Any computer running the keter agent becomes a node that runs headless Claude Agent SDK sessions inside your real repositories. Provision them in Console, set who can use them and how much they can spend, and let your apps start the work.

Sign in with id-kSee how it works
  • Nodes dial outNo inbound ports
  • Your keyAnthropic keys per tenant, sealed
  • Per sessionCost you can read
  • LiveEvery event, streamed

From a machine to a running session

Console provisions the node. Workforce runs the work.

  1. 01

    Add a machine

    In Keter Console, add it as an agent node and set its limits.

  2. 02

    Enable it

    The node dials out to Workforce and reports its stats.

  3. 03

    Start a session

    Pick a repo, a model and a budget. Workforce places it.

  4. 04

    Your app follows it

    Events stream back to whatever started the session.

  5. 05

    Read the bill

    Cost per session, per tenant, per month.

What you get

One door for every client: Task Genius, Champi AI, your scripts and other Keter apps.

Fleet

Every node with its free slots, CPU, disk and link speed in one table. Stats are pushed by the node, so a stale row says so.

Nodes

Integrate

Start sessions from a terminal, your code or an assistant, and follow every event from your own app. Workforce shows status, cost and the event log.

Integrate

Tenants

API keys for your products, a sealed Anthropic key, a monthly budget and a tool policy for each tenant.

Tenants
Guardrails

Agents on your machines, on your terms.

Nodes dial out to Workforce, so a machine behind NAT needs no open port. Each session is pinned to its node and capped by a budget that you set.

Budget
A hard cap per session, plus a monthly ceiling per tenant and per node
Tool policy
An allowlist per tenant, enforced on the node
Keys
Sealed at rest and never returned by the API
Network
Nodes connect outbound only; LAN first
Isolation
An OS user per session, containers per tenant later

Questions

On the nodes you add in Keter Console. A session stays on the node that started it. Workforce coordinates; it does not run your code.

Put a machine to work.

Sign in with id-k