Private beta candidate
Private BetaFrame the broker as a single-cluster private beta engineering candidate, with named-pilot readiness still tied to packet completion, accepted gaps, and product signoff.
Product hub
Message Broker documentation is scoped to the private beta temporal broker candidate: local durable ingest, replay, shared queue processing, diagnostics, configured auth modes, and policy-shaped replication with product-bound claim limits.
Current availability
Private Beta. Public beta is scheduled for .
Frame the broker as a single-cluster private beta engineering candidate, with named-pilot readiness still tied to packet completion, accepted gaps, and product signoff.
Use the native API contract for stream creation, publish, fetch, replay, cursor commit, cursor rewind, and consumer-group inspection wording.
Describe claim, ack, nack, renew, retry, and dead-letter operations as shared-queue workflows over the current broker surface.
Point operators toward health, metrics, audit inspection/export, diagnostics bundle, and release-packet evidence without making support promises.
Keep replication status, worker polling, and target-apply route wording separate from cross-site durability or availability outcomes until selected packet evidence is attached.
Health, metrics, audit inspection, audit export, and diagnostics bundle surfaces for pilot evaluation and operations review.
Stream management, publish, fetch, replay, and record inspection through the native broker contract.
Cursor commit, cursor rewind, and consumer-group inspection for replay and reader coordination.
Claim, mutation, lease renewal, ack, nack, retry, and dead-letter flows over durable queue state.
Replication status, worker poll, and target-apply routes with strict claim boundaries for topology-specific outcomes.
Configured API-key, mTLS trust-file, or trusted-header external identity modes for non-health routes.
Present current workflows as evaluated private beta behavior, not as general release support or an unrestricted broker replacement.
Route-family documentation can name replication status and worker flows, but cross-site outcomes need selected packet evidence and operations review.
Keep Kafka language tied to typed prototype scope until a real listener, client smoke evidence, and accepted matrix row exist.
Name API-key, mTLS trust-file, or trusted-header modes exactly, and require approved support coverage before publishing commitments.
Available now
Run stream and queue quickstartCreate a stream, publish records, replay data, claim queue work, ack results, and inspect private beta limits.
Available now
Review Message Broker limitsUse the limits and compatibility guidance before strengthening stream, queue, auth, replication, or pilot-readiness claims.
Available
Use Rust SDK examplesReview tested Rust examples for stream publish, replay, cursor commit, shared queue processing, retry, and dead-letter handling.
Available
Read HTTP referenceFind versioned stream, record, cursor, queue, audit, metrics, storage, and replication routes.
Available
Read CLI and SDK referenceGroup lifecycle flags, diagnostics, local and remote CLI examples, and Rust SDK entry points.
Available
Compare route and auth scopeSeparate private beta routes from auth, replication, queue, CLI, SDK, and Kafka protocol boundaries.
Available
Read known limitsSee what happens for Kafka listener, replication outcome, identity, and remote CLI boundaries.
Available
Use operator runbooksCheck health, metrics, audit, diagnostics, storage inspection, quota rejection, replication status boundaries, and support details.