Menu

Product hub

Controlled BetaLivePreview ContractVerification Required

ObjectDB

ObjectDB documentation starts with the scoped S3 Core gateway, keeps native object-platform contracts visibly bounded, and routes broader durability, availability, performance, support, security, and scale claims through evidence-backed review.

Current availability

Private Beta. Public beta is scheduled for .

First Path

  1. S3 clientsBegin with local bucket and object workflows.
  2. s3-core-v1Use the named profile and its explicit exclusions.
  3. ObjectDBKeep native API, placement, and durability work tied to review status.

Surface Status

S3 Core gateway

Live

Lead readers to the named s3-core-v1 profile for bucket discovery, object CRUD, listing, range reads, multipart upload, tags, metadata, delegated URLs, browser POST uploads, and explicit unsupported-feature errors.

Evidence: ODB-EVID-002

Native object model

Preview Contract

Treat object versions, manifests, policies, placement, and event-oriented behavior as product direction until public references and reviewer-approved evidence land.

Evidence: ODB-EVID-001

Local adapter and service limits

Verification Required

Keep local workflows tied to named data-directory, platform capability, and failure-mode limits before making durability, recovery, availability, or scale statements.

Evidence: ODB-EVID-004

Customer-facing claims

Verification Required

Reuse fact-sheet wording only with the evidence index nearby; stronger support, security, performance, or competitive wording needs sensitive review.

Evidence: ODB-EVID-005

Boundaries to Keep Visible

Scoped S3 Core

ObjectDB should be framed as an object data platform with a named S3 compatibility gateway, not as a blanket clone of every S3 or AWS IAM behavior.

Preview Native API

Native API, object version, manifest, policy, placement, and event language stays in preview-contract territory until references and evidence records are ready.

Local Adapter Limits

Local workflows are useful for first success and smoke checks, but pages must name local adapter, storage path, and failure-mode limits near the claim.

Safe Next Steps

  • Available now

    Review the evidence index

    Check source-backed claim records before reusing ObjectDB product, S3 Core, or review-boundary wording.

  • Available now

    Run the S3 Core quickstart

    Create a bucket, put and get an object, list results, and see unsupported-surface guidance in a local workflow.

  • Available: DOCS-058

    Use S3 SDK examples

    Adapt illustrative Python boto3 and AWS SDK for JavaScript v3 examples while keeping SDK status, auth, and unsupported behavior boundaries visible.

  • Available: DOCS-038

    Compare S3 Core behavior

    Use the compatibility matrix to separate supported, partial, unsupported, preview, future, and review-bound S3 surfaces.

  • Available: DOCS-042

    Read known limits

    See what happens for unsupported S3 families, local adapter boundaries, and review-bound native API claims.

  • Available: DOCS-029 and DOCS-030

    Read HTTP and configuration references

    Find health routes, S3 gateway route shape, startup environment variables, fixed request limits, and platform capability requirements.

  • Available: DOCS-050

    Run operator smoke tests

    Gather health, platform capability, S3 gateway, data-directory, and support-evidence checks for operators.