Store and serve object data
Start with ObjectDB when the immediate task is bucket and object workflows through the scoped S3 Core gateway.
Review ObjectDB hub and S3 Core boundaries.
Product chooser
Verification RequiredChoose the right Stornamics product path.
Match your goal to ObjectDB, Message Broker, Concordia, or LogDB, then use each hub's maturity labels and boundaries to understand what is ready to evaluate now.
Choose By Goal
Publish, replay, or queue events
Start with Message Broker when the task is stream creation, record publish/fetch, replay, cursor movement, or shared queue work.
Review Message Broker controlled-beta workflows.
Evaluate cache, gateway, or TSDB surfaces
Start with Concordia when the evaluation centers on local Cache behavior, Gateway alpha routes, Time Series primitives, or storage validation.
Review Concordia local and alpha boundaries.
Ingest and query logs or traces
Start with LogDB when the task is OTLP logs/traces ingestion, WAL-backed segment publication, retained segment query, or S3 query-read review.
Review LogDB ingest, query, and gated S3 boundaries.
Compare readiness before picking
Start with the maturity labels when the choice depends on what is live, controlled beta, alpha, preview, future-facing, or verification-required.
Use the labels and hub boundaries before planning a pilot.
Choose By Team
Operators
Plan health, diagnostics, limits, and incident workflows.
Use product hubs to identify current route surfaces, diagnostics evidence, and runbook areas that still need operations review.
App Developers
Build against object, event, cache, and telemetry APIs.
Pick the hub that matches the API surface first, then follow the planned quickstart or reference path for examples.
Platform Teams
Evaluate shared foundations and deployment boundaries.
Start with maturity labels and boundaries before comparing storage, messaging, gateway, telemetry, and deployment direction.
Observability Teams
Mirror logs and traces, query retained records, and evaluate replay direction.
Use LogDB for OTLP ingest and query, then keep Message Broker replay terminology separate unless a workflow needs both.
Storage Teams
Review object storage, segment bundles, S3 scope, and validation gates.
Compare ObjectDB S3 Core behavior with LogDB segment-bundle storage and Concordia validation work without merging their claim boundaries.
Product hubs
- Controlled BetaObjectDB
Private beta object storage documentation led by scoped S3 Core behavior and explicit preview boundaries.
Current availability: Private Beta. Public beta: .
Open the hub for current surfaces, limits, evidence, and planned next steps.
- Controlled BetaMessage Broker
Private beta temporal stream, replay, queue, cursor, audit, metrics, auth, and replication documentation.
Current availability: Private Beta. Public beta: .
Open the hub for current surfaces, limits, evidence, and planned next steps.
- Controlled BetaConcordia
Private beta product-family documentation for Cache, Gateway, Storage, Time Series, and future workflow surfaces.
Current availability: Private Beta. Public beta: .
Open the hub for current surfaces, limits, evidence, and planned next steps.
- Controlled BetaLogDB
Private beta OTLP ingest, WAL, segment bundle, query, BYOC, replay, and audit documentation.
Current availability: Private Beta. Public beta: .
Open the hub for current surfaces, limits, evidence, and planned next steps.
Readiness Guardrails
Start With The Narrowest Live Path
Prefer the product hub that matches the immediate workflow, then expand only when the linked maturity labels and evidence support the next claim.
Keep Similar Words Separate
Object storage, segment storage, replay, gateway, and compatibility terms can mean different things across products; use the owning hub as the source of truth.