Roadmap and status

What is shipped, what is in beta and what is planned, so you can plan around it.

Last reviewed 2026-09-28. Status words used across the docs:

  • Stable: deployed, tested end to end, shape unlikely to change.
  • Beta: deployed and usable; names or fields may still move.
  • Planned: designed, not shipped.

Shipped

AreaStatus
Flutter SDK: client, WebSocket/SSE transports with replay, chat UI, launcher, 30 built-in blocks, custom components, actions, host data bindings, theming (server brand + dark), notifications host, push handoffStable
Runtime: sessions, conversations, realtime, agent loop (OpenAI-compatible and Anthropic providers), HTTP tools with SSRF guard and confirmations, built-in tools, triggers, FCM push, server notificationsStable
Dashboard: agents with versions and live preview, tools, visual workflow builder, components with sync from code, triggers with simulation, conversations and events inspectors, API keys, secrets vault, webhooks configuration, members and roles, environmentsStable
Protocol kletso.ui/v1, kletso.events/v1, realtime frames, components manifest, workflow schemaStable
Demo backend for the Acme sample (/demo/acme/*)Stable

Beta

AreaNotes
WorkflowsThe visual builder, publish and Test run work end to end. Attaching a workflow to an agent or trigger is stored, but live turns and events do not dispatch to the runner yet.
Analytics and Users pagesRead from live data; charts and filters are basic.
ui.patchApplied by the SDK; the runtime does not emit it yet.

Planned

AreaNotes
Knowledge baseUpload and URL sources, chunking, vector index (R2 + Vectorize), retrieve tool. Dashboard page exists as a stub.
Webhook deliveryEndpoints and signing secrets can be configured; the delivery queue with retries is not live yet.
APNs and Web PushFCM works today; iOS-native and browser push are next.
Android and iOS native SDKs, JavaScript widgetSame protocol and runtime.
Region pinning, EU-only placementEnterprise.
Human handoff destinations (Slack, Teams) and hand-backHandoff marks the conversation and stops the assistant; the Kletso inbox is the destination. Slack, Teams and handing back to the assistant are planned.
Conversation retention and deletionEvent logs are kept indefinitely today; retention windows and end-user deletion are planned.
Rule delayThe delay field on trigger rules is stored, not applied.
Self-hosting on your own Cloudflare accountEnterprise.

If a page in these docs describes something on the planned list as if it worked, that is a docs bug. Tell us at hello@kletso.ai.

Last updated 2026-09-28 · Report an issue with this page