Product
ObjectDB, Message Broker, and LogDB are priced independently so teams can license the system they actually need.
Pricing
Transparent licensing for data infrastructure you run anywhere
Compare the edition model and the path for each product. ObjectDB, Message Broker, and LogDB each have published price bands and product-specific capability boundaries.
How pricing works
Start with the product, choose Community, Pro, or Enterprise, then size the license around the operating profile that matters for the deployment.
TB of data
Data footprint is tracked by product. For ObjectDB, logical protected TB counts distinct retained customer-visible objects and versions without charging again for replicas or internal storage overhead.
Node count
Each product is sized around the nodes that run that product. Community stays free with a published allowance for each product.
Operating profile
Throughput, retention, replication topology, governance, and administration needs help determine the software edition. Support is scoped separately.
Compare editions
The same three editions apply across the products shown here. Community is free and limited. Pro and Enterprise are paid licenses sized around product, data, node, and topology needs. Support is licensed separately.
Edition
Community
Free
For self-managed deployments that fit within each product's published allowance.
- Non-expiring product entitlement.
- Product-specific node and capacity allowances.
- Verified product workflows within documented limits.
- Support is licensed separately from the product edition.
Edition
Pro
Transparent paid license
For deployments that need more committed capacity and licensed nodes.
- Sized by product, TB of data, and licensed node count.
- Uses a 365-day paid entitlement unless a published product offer says otherwise.
- Keeps product licensing and support licensing separate.
Edition
Enterprise
Transparent enterprise license
For larger footprints, high redundancy, higher throughput, and formal operational requirements.
- Sized by the same transparent inputs with larger committed allowances.
- Stays inside each product's verified capability and compatibility boundaries.
- Support, rollout help, and custom commercial terms are available separately.
Choose a product path
We are keeping pricing focused on the three products customers can evaluate independently as infrastructure building blocks. Each one uses the same edition model. Detailed price bands are published one product at a time as terms are approved.
ObjectDB
Published pricingObject storage licensed by data footprint, ObjectDB node count, deployment topology, and redundancy goals.
- Protected TB
- ObjectDB nodes
- Cloud, on-premise, or hybrid topology
- Throughput and redundancy targets
Published price bands and edition boundaries are ready to review.
View ObjectDB pricing detailsMessage Broker
Published pricingStreams and queues licensed by the broker nodes in one cluster, without activity-based billing.
- Broker nodes
- One Message Broker cluster per entitlement
- Annual Pro or Enterprise term
- Optional additional paid nodes
Published price bands and edition boundaries are ready to review.
View Message Broker pricing detailsLogDB
Published pricingTelemetry ingest and retained-record query licensed by LogDB nodes in one cluster, without activity-based billing.
- LogDB nodes
- One LogDB cluster per entitlement
- Annual Pro or Enterprise term
- Optional additional paid nodes
Published price bands and edition boundaries are ready to review.
View LogDB pricing detailsLicensing path
Self-service first, sales help when useful
- Start with product and edition, then size the product license by data footprint, node count, and topology.
- Review published product-specific price bands for a self-service commercial starting point.
- Use Contact Sales when procurement, security review, or deployment planning needs extra coordination, when support needs a separate license, or when standard allowances do not fit.