Separate Role From Runtime Support
A product can have an obvious architectural role without every integration path being implemented or reviewed as supported.
Architecture concepts
LiveUse these pages when product names, storage words, replay words, or readiness labels overlap. Concepts explain how to reason about the system before moving into product hubs, references, compatibility matrices, or limits pages.
Available
See how ObjectDB, Message Broker, and LogDB relate without turning validated planning paths into current runtime guarantees.
Available
Object/version/manifest, stream/queue/replay, placement/gateway/storage, and envelope/segment/query concepts.
Available
Tenant, dataset, stream visibility, auth modes, bearer tokens, trusted headers, and review boundaries.
A product can have an obvious architectural role without every integration path being implemented or reviewed as supported.
Compatibility matrices, known-limits pages, references, and status entries decide whether a concept can be stated as live, alpha, preview, future, or verification-required behavior.