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
Choose the right Stornamics product path.
Match your goal to ObjectDB, Message Broker, or LogDB, then use each hub's current availability, limits, and compatibility links 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 private beta workflows.
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 S3 query-read boundaries.
Compare readiness before picking
Start with the status dashboard when the choice depends on private beta timing, live routes, preview contracts, future work, or product-bound claims.
Use product availability and hub limits before planning a pilot.
Choose By Team
Operators
Plan health, diagnostics, limits, and incident workflows.
Use product hubs to identify current route surfaces, diagnostic context, and runbook areas that remain product-scoped.
App Developers
Build against object, event, 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 availability, readiness, and boundaries before comparing storage, messaging, 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, and S3 scope.
Compare ObjectDB S3 Core behavior with LogDB segment-bundle storage without merging their claim boundaries.
Product hubs
- ObjectDB
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, compatibility, and planned next steps.
- Message 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, compatibility, and planned next steps.
- LogDB
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, compatibility, and planned next steps.
Decision Checks
Start With The Narrowest Current Path
Prefer the product hub that matches the immediate workflow, then expand only when the linked readiness labels and limits 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 reference point.