Skip to content

Roadmap

What we’re building.

Shipped work is separated from work still under proof. Capabilities move to “live” only after their production endpoint, entitlement path, and customer surface pass the relevant verification. Bee Ignite is an active from-scratch foundation research programme, not a customer tier, and has no released checkpoint.

Live — Bee production platform

Done

The customer product, API, model ladder, billing controls, and governed evidence surfaces are running as one production platform.

Shipped

  • Six production tiers — Cell, Brood, Comb, Buzz, Hive, and Swarm — plus Enclave deployment contracts
  • OpenAI-compatible chat, streaming, document RAG, memory, projects, artefacts, scheduled tasks, and notifications
  • Image generation, voice input/output, Android push infrastructure, and metered OpenQuantum hardware jobs
  • Per-plan usage enforcement, per-API-key controls, billing, credits, gifts, and premium-routing settlement
  • Signed product facts, public capability evidence, post-quantum coverage register, and release-gated adapters

Now — complete Bee-family capability parity

In progress

Expose every foundation capability that Bee can support safely and reproducibly, then advertise it only after the running endpoint passes the corresponding probe.

In flight

  • Cell and Brood native multimodal routing, thinking controls, tool calls, and structured response support
  • Automatic and manual multimedia context compaction with visible token-recovery events
  • Workspace image/video creation controls and completed-job media URL preservation
  • Site-wide model, documentation, metadata, download, and Open Graph reconciliation from canonical facts

Exit criteria

  • Live vision, video, tool-calling, and structured-output probes archived for every tier that claims them
  • Capability register, model cards, API docs, llms.txt, and product facts regenerate from the same evidence
  • No customer-facing page contains a stale base model, context window, price, download, or feature claim

Now — Android production distribution

In progress

Ship one maintained Android client through Google Play while retaining a signed direct-download channel for controlled distribution.

In flight

  • Signed release APK and Android App Bundle produced from the same workspace WebView shell
  • Google Play listing, app-content declarations, reviewer access, and production release workflow
  • Foreground, background, closed-app, and notification-tap delivery matrix on physical Android hardware

Exit criteria

  • Google Play production review accepted and release available in approved countries
  • Website download manifest and store listing resolve to the current signed release
  • Real FCM delivery enabled only after the published subprocessor notice period expires

Now — shared team workspace boundary

In progress

Finish the tenant boundary so membership, invitations, role changes, projects, conversations, documents, encryption keys, and notifications follow the selected workspace consistently.

In flight

  • Team creation and membership administration
  • Workspace-aware projects, conversations, and document libraries
  • Invitation delivery, role-change controls, removal, and audit evidence

Exit criteria

  • Cross-tenant access tests pass for every shared resource
  • Invitations and role changes are delivered and auditable end to end
  • Plan entitlements and seat limits are enforced server-side

Next — governed automatic promotion

Next

Automatic adapter promotion remains off until a real candidate completes the evaluation, canary, rollback, and evidence-archive exercise.

Exit criteria

  • A real candidate completes held-out evaluation and a bounded production canary
  • Rollback is deliberately exercised and the recovery evidence is archived
  • Promotion can be enabled without bypassing human, cost, or safety gates

Next — signed desktop and iOS distribution

Next

The shared workspace code already powers thin desktop and mobile shells; public distribution waits on platform signing and notarisation credentials.

Exit criteria

  • Apple Developer signing, notarisation, App Store, and iOS distribution credentials provisioned
  • Windows code-signing certificate and Tauri updater signing secrets provisioned
  • Install, update, rollback, and native-notification matrices pass on supported platforms

Roadmap caveats

Status follows evidence, not calendar promises. The internal source of truth is docs/product/roadmap.md in the main repo — this page is its customer-facing distillation and is updated when a proof gate changes.