ObjectDB pricing
Review the published ObjectDB price bands, included node and protected TB allowances, expansion packs, and edition capability boundaries before choosing the license shape for a cloud, on-premise, or hybrid deployment.
ObjectDB prices use committed license limits rather than automatic usage overages, so a team can choose the capacity it wants to license before deployment.
ObjectDB
$0
Free, non-expiring entitlement
Included
Expansion
ObjectDB
$12,000/year
$1,000/month equivalent, billed annually
Included
Expansion
ObjectDB
$36,000/year
$3,000/month equivalent, billed annually
Included
Expansion
Logical protected TB counts the payload bytes of distinct retained customer-visible objects and versions before ObjectDB compression. Replicas, erasure or parity data, indexes, journals, and temporary rebuild copies do not count again. Two independently uploaded objects count separately even when their content matches. One TB is one trillion bytes.
Licensed nodes are ObjectDB server processes that store, serve, or replicate ObjectDB traffic; client applications, SDKs, CLIs, and one-shot CI tools are not billable nodes. ObjectDB used only as an internal storage detail of another licensed Stornamics product does not require a second ObjectDB entitlement. An independently administered ObjectDB cluster remains separately licensed.
The capability matrix stays inside the current S3 Core profile: advanced S3 families and native ObjectDB runtime features are not implied by paid editions.
| Capability | Community | Pro | Enterprise |
|---|---|---|---|
| License shape | Free and non-expiring for personal, development, testing, learning, internal, and commercial use up to 5 nodes and 5 logical protected TB within documented maturity boundaries. | $12,000/year for 10 nodes and 50 logical protected TB. | $36,000/year for 50 nodes and 500 logical protected TB. |
| S3 Core bucket and object workflows | Included within the current private-beta s3-core-v1 compatibility and limit boundaries. | Included within the same documented s3-core-v1 compatibility and limit boundaries. | Included within the same documented s3-core-v1 compatibility and limit boundaries. |
| Object tags, metadata, CORS, and bucket policy | Included within documented local-adapter caps. | Included within documented local-adapter caps. | Included within documented local-adapter caps. |
| Data footprint | Up to 5 logical protected TB. | 50 logical protected TB included, with additional 100 TB commitments. | 500 logical protected TB included, with additional 100 TB or custom commitments. |
| Node footprint | Up to 5 ObjectDB nodes. | 10 licensed ObjectDB nodes included, with individual node expansion. | 50 licensed ObjectDB nodes included, with individual node expansion. |
| Allowance and scale boundary | The allowance is a license limit, not a durability, performance, topology, or verified-scale guarantee. | The allowance is a license limit; use current compatibility, limits, and evaluation evidence for deployment decisions. | The larger allowance does not widen the current private-beta compatibility, durability, performance, or scale boundary. |
| Advanced S3 families | Not included. | Not included in the active s3-core-v1 profile. | Not included until a future profile is approved. |
| Native ObjectDB model | Not included as a supported runtime feature. | Preview-contract review only. | Preview-contract review only with product approval. |
| Support path | Self-service documentation remains available; any paid support subscription is purchased separately. | Support is licensed separately from the product entitlement. | Support, professional services, and managed operations are purchased separately. |
Next step