Buskeeper release status

We publish implementation milestones and acceptance status so teams can tell the difference between shipped capabilities and roadmap work.

Local foundation complete; evidence and migration work implemented locally and progressing through acceptance. The hosted team layer is in closed beta. Pricing is not published and no checkout is open.

Last updated 21 October 2026 · this page describes the repository state, not an SLA or an uptime measurement.

Timeline

What is done, in progress, and planned.

  • P0 · local foundation

    The daemon, state machine, lane authentication, REST endpoints, MCP interfaces, CLI, minimal UI, tests, packaging, and the local two-lane workflow.

    Complete
  • P1 · evidence and migration

    Attachments, retention, export formats, the XIOM relay importer, docs scaffold, and install scripts. Implemented locally; the CI and operations acceptance gate is still being closed.

    Implemented
  • P2 · team mode

    Schema v3, human accounts with Argon2id, roles, persistent sessions, login/logout, account administration, and the light/dark responsive UI. Approvals, audit export, notifications, staging deployment, backup drills, and load tests remain.

    In acceptance
  • Hosted beta and billing

    Single-tenant hosted workspaces, billing, customer portal, trial flows, and further PWA polish. Planned after the team-mode acceptance gate.

    Planned
  • Productization

    Protocol packs, A2A adapter, webhooks, GitHub integration, SSO/SAML, Postgres adapter, conformance badges, and registry listings.

    Planned

What you can use today

Local workspace

  • One binary with the daemon, web UI/PWA, CLI, and MCP server.
  • SQLite event log, append-only history, online backup.
  • Lane identity, scoped tokens, role-bound transitions.
  • Typed references, image attachments, retention.
  • JSON, CSV, and Git-layout Markdown export.
  • Human accounts and persistent sessions on the P2 branch.
Do not assume hosted availability. Proposed prices are not a checkout offer. No uptime percentage is published because there is no hosted service with a measured history yet.

Acceptance detail

What “in acceptance” means here.

A capability is only marked available after implementation, tests, documentation, and the relevant acceptance gate. CI green alone is not the gate.

AreaCurrent stateEvidence or next gate
Local two-lane workflowCompleteAutomated tests and the smoke binary.
Import / exportImplemented locallyRound-trip tests; operations acceptance pending.
Human accounts and sessionsP2 branch; in acceptanceSchema v3, Argon2id, token-hash sessions, RBAC tests.
Approvals and gatesP2 plannedRole-bound approval transitions and tests.
Audit exportP2 plannedGoverned event export for review.
NotificationsP2 plannedEmail, Slack, Telegram delivery after acceptance.
Staging deployP2 plannedDeployment hardening and smoke checks.
Backup / restore drillP2 plannedDocumented restore verification.
10k-item / 100-lane load testP2 plannedMeasured results before hosted claims.
Hosted billingPlannedProvisioning, billing, cancellation, deletion flows.

Follow the build, not the hype.

Request the local preview, read the specification, or ask a direct question about the current state.