Architecture concept
LiveUse this page to read tenant, dataset, stream visibility, auth mode, bearer token, trusted-header, and product-boundary language without turning local or private beta evidence into a broader identity, privacy, support, or compliance claim.
A product-scoped identity or partition boundary used by docs examples, route checks, limits, records, or access policy.
Use now: Use when a product reference names the tenant field, header, route permission, quota, or local policy that applies to a request.
Boundary: Does not imply product-wide isolation, customer identity integration, privacy posture, regulatory posture, or shared tenancy semantics across products.
A named grouping or filter boundary whose exact behavior is owned by the product page that defines the field.
Use now: Use for LogDB query authorization and filters, and cautious ObjectDB native-model discussion.
Boundary: Does not imply a global Stornamics namespace, cross-product policy boundary, or customer data governance claim.
The Message Broker route behavior that returns only tenant-visible stream descriptions or not-found errors for streams outside the caller's route context.
Use now: Use with broker stream list, stream describe, storage catalog, stream inspect, and permission language from the HTTP reference.
Boundary: Does not imply cross-tenant discovery, external identity-provider validation, or every stream-sharing pattern a deployment might need.
A configured product posture for checking credentials or admitting local requests, such as insecure-local, api-key, mTLS, external, or local bearer-token modes.
Use now: Use only with the exact product mode, route family, credential source, transport, and local or private beta status named by the reference.
Boundary: Does not imply direct identity-provider validation, customer credential parity, hosted control-plane integration, or a uniform auth model across products.
A credential value passed in an Authorization header or metadata field where a product reference names that behavior.
Use now: Use for Message Broker API-key examples and LogDB local tenant admission checks.
Boundary: Local tokens are example or development admission boundaries unless a product page names stronger credential validation and product confirmation.
An external Message Broker identity mode where a configured upstream component supplies identity through headers the broker trusts.
Use now: Use when documenting broker external auth mode and route checks that depend on configured upstream identity headers.
Boundary: Does not imply direct identity-provider validation, header trust outside the configured boundary, or automatic support in ObjectDB or LogDB.
A named area where stronger identity, security, privacy, support, or policy wording requires product-specific evidence and review.
Use now: Use near auth, tenant, dataset, encryption, trusted-header, local-token, support, or customer-commitment language that needs exact scope.
Boundary: A product boundary is not a defect claim or roadmap promise; it scopes the exact wording in front of the reader.
| Product | Current surface | Source scope | Boundary |
|---|---|---|---|
| ObjectDB | S3 Core gateway examples use local development principals and ObjectDB-specific permission headers; bucket policy, SSE header mapping, and customer credential composition stay product-bound. | documented source scope | Do not claim IAM parity, customer credential parity, encryption-at-rest backend composition, tenant isolation, or policy outcomes beyond the named local gateway behavior. |
| Message Broker | The private beta HTTP surface supports insecure-local, api-key, mTLS, and external auth modes, with tenant and stream permissions for protected route families. | documented source scope | Do not claim direct identity-provider validation, unrestricted remote CLI credentials, Kafka listener identity semantics, or production support coverage. |
| LogDB | OTLP and query routes use x-logdb-tenant plus Authorization bearer credentials in local development; query requires a dataset and checks dataset read authorization. | documented source scope | Do not treat custom endpoint JSON helper routes as tenant-admitted OTLP behavior or claim broader identity, privacy, retention, or BYOC readiness. |
Product-specific tenant, dataset, stream, and token behavior does not create one cross-product identity model.
API keys, local bearer tokens, mTLS trust files, and trusted headers only mean what the owning reference says they mean.
Access checks, tenant headers, and local admission examples do not establish certification, regulatory, privacy, support, or legal commitments.
| Concept area | Source scope | Status |
|---|---|---|
| Cross-product tenancy and security vocabulary | documented source scope | approved |
| ObjectDB local principal, policy, SSE, and credential boundaries | documented source scope | approved |
| Message Broker auth modes, tenant permissions, and stream visibility | documented source scope | approved |
| LogDB tenant admission, dataset authorization, and helper-route boundaries | documented source scope | approved |
Internal public documentation boundaries track this concept page and its claim boundaries.
Available
Use the claim boundary checklistRoute security, privacy, support, credential, identity, tenant, and customer-commitment wording through the required support teams.
Available
Read product mental modelsUse product nouns correctly before writing tenant, dataset, stream, auth, or trusted-header copy.
Available
Review known limitsCheck unsupported auth, identity, token, trusted-header, and customer credential behavior before publishing guidance.
Available
Compare compatibility rowsUse compatibility status and evidence before strengthening identity or access-control wording.
