Supported
Implemented and validated for the exact documented scope.
Compatibility
Start with the surface you plan to use, then open the product matrix for the detailed limits and next best path. Compatibility statuses separate supported, partial, unsupported, preview, and future behavior.
| Capability | Status | Maturity | Notes |
|---|---|---|---|
| ObjectDB: S3 Core clients | Supported | Live | S3-compatible clients can evaluate bucket lifecycle, object put/get, listing, and cleanup flows against the active local gateway. |
| ObjectDB: advanced S3 families | Unsupported | Future | Versioning, Object Lock, lifecycle automation, replication, SelectObjectContent, events, and website hosting are outside the active S3 Core profile. |
| Message Broker: HTTP stream and queue clients | Supported | Private Beta | HTTP clients can create streams, publish records, replay by cursor or time, claim queue work, acknowledge delivery, and inspect health or metrics. |
| Message Broker: Kafka wire protocol | Future | Future | Kafka-shaped migration fixtures exist for planning, but the current customer path is the Message Broker HTTP API. |
| LogDB: OTLP HTTP logs and traces | Supported | Live | OpenTelemetry-compatible senders can use OTLP HTTP/protobuf or JSON-compatible input, then query retained records through the documented query route. |
| LogDB: metrics and profiles | Unsupported | Future | Metrics and profile ingest are not part of the current customer runtime; keep logs and traces on the documented OTLP/query path. |
Implemented and validated for the exact documented scope.
Some behavior works, but documented gaps, limits, or exclusions apply.
Not implemented, intentionally unavailable, or rejected at runtime.
Early surface for planning or evaluation before complete customer-facing support.
Planned direction with no current runtime behavior to rely on. Check the documented status and release notes before using it.
Available
ObjectDB S3 Core compatibility matrixBucket, object, multipart, tag, CORS, policy, SSE, and presigned behavior for the active S3 Core profile.
Available
Message Broker route and auth matrixRoute families, auth modes, replication surfaces, queue behavior, and Kafka compatibility boundaries.
Available
LogDB OTLP and S3 query matrixOTLP HTTP, optional gRPC, JSON compatibility, query paths, S3 query reads, metrics/profile exclusions, and future publication work.
Available
ObjectDB known limitsUnsupported S3 families, local adapter constraints, preview native API boundaries, and current ObjectDB limits.
Available
Message Broker known limitsKafka listener exclusions, replication outcome boundaries, auth posture, remote CLI limits, and broker support boundaries.
Available
LogDB known limitsMetrics/profile exclusions, S3 query-read behavior, replay API boundaries, external sink boundaries, and BYOC limits.