Stornamics system map.

Use this map to understand the active product roles, where they naturally sit near one another, and which boundaries prevent conceptual adjacency from becoming a runtime support claim.

Map Snapshot

Products: 3
Integration lanes: 3
Current claim level: Concept
Documentation status: Accepted

Architecture Diagram

Product roles are shown first, followed by conceptual lanes that require their own evidence before becoming runtime guidance.

ObjectDBLive s3-core-v1 gateway behavior Message BrokerPrivate beta HTTP route families LogDBLive ingest and query paths

Object references carried in messagesObjectDB + Message Broker
Telemetry from services into retained queryLogDB + any product service
S3-shaped storage vocabularyObjectDB + LogDB

Read every lane as planning input. Product hubs, compatibility matrices, limits, and public status, limits, and compatibility pages still own the support boundary.

Product Role Map

Object storage and object-data platform directionLive

ObjectDB

Start here for scoped S3 Core bucket and object workflows, plus explicit preview native object-platform boundaries.

Current surface: Live s3-core-v1 gateway behavior
Boundary: Does not imply broad S3 parity, distributed durability, hosted control plane, or native object-platform runtime support.

Message movement, replay, cursors, and shared queuesPrivate Beta

Message Broker

Start here for private beta stream create, publish, replay, cursor, shared queue, audit, metrics, and route inspection workflows.

Current surface: Private beta HTTP route families
Boundary: Does not imply strict cross-site outcomes, failover proof, direct identity-provider validation, or Kafka wire-protocol listener support.

Telemetry ingest, retained records, segment bundles, and queryLive

LogDB

Start here for OTLP logs/traces ingest, optional gRPC, local retained-record query, S3 query-read boundaries, and BYOC handoff boundaries.

Current surface: Live ingest and query paths
Boundary: Does not imply metrics/profile ingest, live S3 publication, public replay APIs, external sinks, or BYOC production readiness.

Validated Integration Planning Paths

Conceptual cross-product lanes
Path	Products	Use when	Current boundary	Source scope
Object references carried in messages	ObjectDB + Message Broker	An application wants messages to point at object keys, manifests, or storage events without copying large payloads through a stream.	Validated architecture planning path only. ObjectDB remains the object source of truth; Message Broker docs prove broker route behavior, not automatic object-event wiring.	documented source scope
Telemetry from services into retained query	LogDB + any product service	Operators need logs or traces from product services retained as records that can be queried by tenant, dataset, record ID, trace ID, and time filters.	LogDB proves ingest and query routes. This page does not claim automatic instrumentation or cross-product telemetry packaging.	documented source scope
S3-shaped storage vocabulary	ObjectDB + LogDB	Readers compare ObjectDB S3 Core object behavior with LogDB segment-bundle storage and S3 query-read settings.	ObjectDB S3 Core and LogDB S3 query-read are different surfaces. Do not merge them into one generic S3 compatibility claim.	documented source scope

How To Read The Map

Start With The WorkloadObject payload, event movement, or telemetry query should determine the first product page.
Check The Product BoundaryEach product hub, compatibility page, and known-limits page names what is live, private beta, alpha, preview, future, or still verification-required.
Treat Cross-Product Lanes As Design InputUse integration lanes to plan architecture conversations, not to publish runtime interoperability claims without evidence.

Do Not Infer

No Automatic Product Mesh

The map does not claim that ObjectDB, Message Broker, and LogDB automatically discover, secure, route, replicate, or observe one another.

No Shared Maturity Level

One product's live surface does not promote an adjacent product's alpha, preview, future, or verification-required surface.

No Hidden Support Promise

Support, security, durability, availability, performance, scale, compliance, and customer-commitment claims still need their own evidence and support teams.

Source scope

Source scope map
Map area	Source scope	Status
Product roles and maturity boundaries	Product hubs, status page, documented source scope, and source public status, limits, and compatibility pages	approved
Object storage and S3 Core boundary	documented source scope	approved
Message movement, replay, queue, and protocol boundary	documented source scope	approved
Telemetry ingest, query, S3 query-read, and BYOC boundary	documented source scope	approved

Internal public documentation boundaries track this system map and its product-boundary language.

Limits

This page is a conceptual map, not a runtime integration guide or deployment architecture.
Integration lanes are validated architecture planning patterns; product-specific source, tests, fixtures, release notes, and owner review still decide runtime support.
Future-facing surfaces such as broader S3 profiles, Kafka wire protocol, LogDB live S3 publication, and cross-product packaging stay labeled by their owning pages.

Safe Next Steps

Available
Choose a product path
Start with the product chooser when the immediate workflow is storage, messaging, cache, gateway, time-series, or telemetry.
Available
Review compatibility matrices
Use row-level status, maturity, evidence, and review freshness before strengthening any system-map claim.
Available
Read known limits
Check unsupported runtime behavior before turning a validated integration planning path into guidance.
Available
Check current readiness
Compare live, private beta, alpha, preview-contract, future, and verification-required surfaces by product.