Known limits

Message Broker known limits.

Known Message Broker unsupported behavior, route-level runtime boundaries, and public claim boundaries.

Current availability

Private Beta. Public beta is scheduled for November 9, 2026.

Private BetaConfirm First

Audience

Use this page before designing broker integrations, writing migration guidance, or reviewing claims that mention Kafka, replication outcomes, auth posture, remote CLI behavior, or support boundaries.

Readiness Notes

Private Beta Routes

Private Beta

Stream, record, cursor, queue, audit, metrics, storage, and replication routes stay scoped to current private beta references.

Verification Gaps

Confirm First

Kafka network compatibility, strict cross-site outcomes, identity-provider validation, and support wording remain bounded.

Scope

Message Broker private beta route families, configured auth modes, remote CLI and SDK transport limits, replication row boundaries, and Kafka-shaped prototype exclusions.

Prerequisites

Read the Message Broker route and auth compatibility matrix.
Use the HTTP reference and CLI/SDK reference for exact route and tooling behavior.

Current Limits

Message Broker known limits. current limits
Limit	Applies to	Runtime behavior	Next best path
Kafka network listener	External Kafka clients and Kafka wire-protocol requests	There is no current Kafka network listener or external Kafka client smoke evidence. The Kafka-shaped adapter is a typed prototype, not a network endpoint.	Use the native HTTP routes, remote CLI management reads, or Rust SDK HTTP workflows documented for private beta evaluation.
Replication outcomes	Cross-site durability, failover, target-environment outcomes, and topology promises	Replication status, poll, pause, resume, and target apply routes exist, but route responses alone do not prove topology outcomes.	Keep wording to route behavior unless a public compatibility row documents a stronger outcome.
Direct identity-provider validation	mTLS trust-file and trusted-header external auth modes	Protected route behavior depends on configured auth mode. External modes rely on a trusted upstream and do not prove broker-side identity-provider validation.	Use documented API-key, mTLS trust-file, or trusted-header mode wording and keep external identity claims bounded.
Remote CLI data writes	Remote CLI over http:// targets	Remote CLI can call health, management inspection, and diagnostics routes over http:// targets; remote data writes and mTLS credentials are outside current CLI transport.	Use local CLI or documented HTTP routes for data workflows.

Unsupported Behavior

Message Broker known limits. unsupported behavior
Scenario	What happens	Recommended action
Connect an external Kafka client	No Kafka network listener is documented for the current broker.	Use native HTTP and SDK paths until a listener and client smoke path are documented.
Treat replication status as failover proof	Status and target-apply responses are route-level signals only.	Keep outcome wording tied to the documented route and topology scope.
Call protected routes without matching auth mode	Protected routes reject requests that do not satisfy the configured auth posture.	Use the HTTP reference for required permissions, headers, and mode-specific behavior.

Limits

This page summarizes current Message Broker route, auth, CLI, SDK, replication, and Kafka boundaries.
Do not use route existence alone as proof for cross-site or protocol outcomes.
Future protocol or replication claims need public compatibility support before promotion.

Safe Next Steps

Available
Compare route and auth scope
Use row status and notes before relying on routes, auth, replication, CLI, SDK, or Kafka-shaped behavior.
Available
Read HTTP reference
Check route permissions, errors, and limits for protected behavior.
Available
Review Message Broker limits
Confirm broker limits before planning broader protocol or topology claims.