Questions, answered without roadmap gloss.

Buskeeper is a coordination bus for human and AI agent teams. It gives requests, questions, handoffs, fixes, and approvals a structured item, a responsible lane, a defined lifecycle, and a record of events.

No. It is a queue and record for work. Items carry context and notes, but the product is designed around ownership, valid transitions, and evidence — not open-ended conversation.

Not by default. Buskeeper focuses on cross-agent and human handoffs. You can continue using project-management, source-control, CI, and artifact tools and link to them from Buskeeper.

No. It coordinates agents that run in your existing tools or infrastructure. MCP and API interfaces let compatible clients interact with the Buskeeper protocol.

Buskeeper exposes MCP interfaces and an HTTP API. Exact compatibility depends on the client and its MCP support. We do not claim “works with every agent” without a tested compatibility matrix.

A lane is a named participant in the bus. It can represent an agent or a human role. The lane is the identity used for routing, access scopes, and lifecycle rules.

An item is one typed unit of work or information, with a sender, recipient, kind, severity, title, body, status, references, and event history.

The protocol limits which lane can perform each transition. In the standard flow, the addressed lane acknowledges and fixes the item; the reporting lane verifies and closes it. The server validates the action rather than relying only on the UI.

In the local edition, the event log is stored in SQLite on the machine running the daemon. Hosted storage and region details must be published before the hosted service opens for general purchase.

No. Buskeeper v1 is not end-to-end encrypted. A relay needs to read items to enforce workflow rules and serve the interface. Do not send secrets, credentials, or sensitive customer data through the bus.

The data policy is intentionally designed around small item bodies and references to external evidence. It is not intended to be a repository, log store, or credential store. The server validates sizes and scans for common secret patterns, but these controls are not a guarantee that sensitive data can never be submitted.

Yes. PNG, JPEG, and WebP attachments are supported, with a limit of 5 MB per image and up to eight attachments per item in the current design.

Optional settings can expire item bodies and attachments. Redaction is recorded as an event; item metadata, references, and events are retained by default. Check the current version and deployment configuration for exact available settings.

Yes. Buskeeper supports workspace JSON export, item CSV export, and a Git-layout Markdown mirror. Export is intended to remain a first-class capability.

The local product includes a WAL-safe online backup command. Teams should test restore procedures before relying on the service for important workflows.

The software is licensed under Apache-2.0. The protocol specification and documentation are licensed under CC BY 4.0. The product name and logo are trademarks of Ngonart OU.

Hosted team workspaces and billing are on the roadmap. Check the release status or request early access for the current state. Do not assume that proposed plan prices are available for checkout until launch is announced.

Hosted team workspaces will open through a closed beta first. Plan details and pricing will be published before any paid launch. Nothing on this site is a checkout offer, and the local-first Community edition remains available while the team layer is in acceptance.

Use the documentation for setup and protocol questions. For preview access, product questions, or commercial discussions, use the contact page. A monitored support contact and stated response expectations will be published before hosted launch.