Skip to content

Roadmap

Katra’s roadmap is ordered around complete usable loops and evidence gates. It does not publish speculative delivery dates.

Status reviewed: August 11, 2026

Available now

Channels & direct messages

Threads, reactions, mentions, edits, unread state, and realtime delivery.

Attention & search

Explicit attention requests and authorization-first global message search.

Meeting coordination

Scheduling, guest invitations, notes, decisions, action items, chat, and reactions.

In progress

Live meeting media

Self-hosted audio, video, and screen sharing through LiveKit.

Planned

Work items & manual workflows

Human tasks, decisions, approvals, returns, and versioned visual workflows.

Agent profiles & execution

Optional agent executors, prepared workspaces, and multi-step handoffs.

Installer & production deployment

Supported installation, upgrades, backup, restore, rollback, and recovery.

  1. Complete and verify self-hosted LiveKit audio, video, screen sharing, reconnect, trusted TLS, direct UDP, and TURN fallback.
  2. Define the installer, first administrator, operating organization, interrupted-install recovery, and safe rerun behavior.
  3. Define internal teams and the authoritative Work Item model.
  4. Implement manual-first workflows with durable human tasks and decisions.
  5. Prove one bounded agent workflow with Katra-managed Git, a prepared Workspace, two Agent Profiles, two agent steps, and one human approval.
  6. Publish supported single-server deployment, upgrade, backup, restore, rollback, and recovery evidence.
  • Desktop and mobile packaging from the shared Katra Client
  • Optional external Git import, mirror, and export
  • Additional identity providers where they remain optional
  • Adaptive memory and learning only after controlled experiments justify product dependence
  • Cluster packaging only after single-server behavior is measured
  • Manual workflows come before agent execution.
  • Agents remain optional executors, not the owner of workflow policy.
  • Product screenshots do not establish implementation status.
  • Features move to available only after their decisions, contracts, tests, operational guidance, and reproduced evidence are complete.