Known limits

ObjectDB known limits.

Known ObjectDB unsupported behavior, runtime responses, local adapter limits, and public claim boundaries.

Current availability

Private Beta. Public beta is scheduled for October 12, 2026.

LiveConfirm First

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.

Readiness Notes

S3 Core Profile

Live

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

Public Boundaries

Confirm First

Credential posture, broader S3 families, durability, operations, and support wording stay scoped to the public compatibility and reference pages.

Scope

ObjectDB s3-core-v1 gateway behavior, local adapter constraints, explicit unsupported S3 families, preview native API boundaries, and public claim boundaries.

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
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.
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.
Native object platform contracts	Object versions, manifests, policy, placement, and events	Native API posture remains preview-contract direction until public references document supported behavior.	Use the scoped S3 Core gateway for current workflows and keep native API claims bounded.

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 documents support.
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.

Limits

This page summarizes ObjectDB limits already backed by the S3 Core matrix and references.
Do not use this page to infer new S3 compatibility outside the documented matrix.
Future ObjectDB profiles need their own public compatibility rows before unsupported rows move.

Safe Next Steps

Available
Compare S3 Core behavior
Use row status and notes before relying on any S3-shaped behavior.
Available
Read S3 and HTTP reference
Check route shapes, error behavior, and local adapter constraints.
Available
Review ObjectDB limits
Confirm ObjectDB limits before planning broader S3 workflows.