How Selra works

Selra is the place where people and digital coworkers operate together — with governed tool use, shared queues, and visible cost.

For humans

Work in one environment: chat with digital coworkers, see attention / open / waiting queues, review plans and evidence, and keep cost on the board.

For digital coworkers

They propose structured action plans. Selra validates and checks policy before tools run. Plan and respond are separate, metered operations.

The turn path

No dependence on provider-native free-form tool calls. Structure first.

Propose

An ActionPlan JSON: respond, use_tool, request_approval, or unable — with confidence and a short reason code.

Validate

Schema, tool exists, allowlist, coworker authz, org/tenant, read/write policy, iteration limits.

Gateway

Policy → Tool Gateway → tool result with evidence refs. On failure: clear status, no invented hits.

Respond

Separate model op with its own telemetry. Cost panel shows plan vs respond vs tools.

Work queues

Queues match how operators already think about work.

Attention

Items that need a human now — approvals, exceptions, or blockers.

Open

Active work in flight for people or digital coworkers.

Waiting

Blocked on an external system, person, or event.

With Wakehold — or without

Selra integrates via APIs and events. It can pair with Wakehold for completion and assurance, or run on its own. The products are combinable, not inseparable.

See if Selra fits your team

Early access. Email us — no fake portal signup.

Request access