ObjectDB known limits.

Known ObjectDB unsupported behavior, runtime responses, local adapter limits, and review-bound claim areas.

Current availability

Private Beta. Public beta is scheduled for September 7, 2026.

Audience

Use this page before choosing S3 operations, writing ObjectDB examples, or reviewing claims that mention unsupported S3 families, local adapter behavior, or native object-platform direction.

Maturity Status

S3 Core Profile

Live

Bucket and object workflows stay tied to the named s3-core-v1 profile and its explicit exclusions.

Review-Bound Edges

Verification Required

Credential posture, broader S3 families, durability, operations, and support wording need accepted evidence before promotion.

Scope

ObjectDB s3-core-v1 gateway behavior, local adapter constraints, explicit unsupported S3 families, preview native API boundaries, and claim areas that still require review.

Prerequisites

Read the ObjectDB S3 Core compatibility matrix.
Use the ObjectDB S3 and HTTP reference for exact route and error wording.

Current Limits

ObjectDB known limits. current limits
Limit	Applies to	Runtime behavior	Next best path	Evidence
Advanced S3 families	Versioning, Object Lock, lifecycle, replication, inventory, notifications, SelectObjectContent, ACLs, and website hosting	These surfaces sit outside s3-core-v1. Routed requests should return S3-shaped NotImplemented responses when the gateway recognizes them.	Build against bucket and object operations in the ObjectDB S3 Core compatibility matrix.	ODB-EVID-002, ODB-EVID-009
Local adapter state	CORS, policy, tags, metadata, and local data-directory state	Local adapter behavior is bounded by documented payload caps, local storage paths, and temporary local state.	Use the S3 and HTTP reference before depending on local adapter behavior outside first-success workflows.	ODB-EVID-007, ODB-EVID-008, ODB-EVID-009
Native object platform contracts	Object versions, manifests, policy, placement, and events	Native API posture remains preview-contract direction until public references and reviewer-accepted evidence exist.	Use the scoped S3 Core gateway for current workflows and keep native API claims in review.	ODB-EVID-001, ODB-EVID-005

Unsupported Behavior

ObjectDB known limits. unsupported behavior
Scenario	What happens	Recommended action
Enable bucket versioning or Object Lock	The operation is outside the active profile and should not be treated as available ObjectDB behavior.	Keep the workflow on unversioned bucket and object operations until a future profile adds evidence.
Use lifecycle, replication, inventory, or notifications	Those S3 families are explicitly excluded from s3-core-v1.	Document the dependency as unsupported and track it through a future compatibility row.
Use ACLs, website hosting, or SelectObjectContent	These requests are outside the documented route surface for the active profile.	Use bucket policy, object metadata, and object reads that are listed in the compatibility matrix.

Claims Requiring Review

ObjectDB known limits. review-bound claims
Claim area	Required reviewer	Publication status
Durability, recovery, or operations outcomes	objectdb-product-sme and operations-reviewer	Verification Required
Security, support, performance, or scale wording	security-reviewer, support-reviewer, and docs lead	Verification Required
Broad S3 parity or customer credential commitments	objectdb-product-sme and legal-reviewer	Verification Required

Evidence

ObjectDB known limits. evidence
Limit or unsupported behavior	Evidence	Status
Unsupported S3 families	DOCS-038 and ODB-EVID-009	pending
HTTP route behavior and local adapter caps	DOCS-029, DOCS-030, ODB-EVID-007, and ODB-EVID-008	pending
ObjectDB limits page artifact	DOCS-042	pending

The evidence table summarizes the reviewed basis for each known limit without exposing internal source locations.

Limits

This page summarizes ObjectDB limits already backed by the S3 Core matrix and references.
Do not use this page to add new S3 compatibility claims without product SME review.
Future ObjectDB profiles need their own evidence before unsupported rows move.

Safe Next Steps

Available: DOCS-038
Compare S3 Core behavior
Use row status and evidence before relying on any S3-shaped behavior.
Available: DOCS-029
Read S3 and HTTP reference
Check route shapes, error behavior, and local adapter constraints.
Available
Review ObjectDB evidence
Confirm source records before strengthening ObjectDB limits wording.