ScyllaDB review

ScyllaDB is a distributed NoSQL database aimed at workloads that need low latency and high throughput. The homepage positions it for real-time AI systems, including feature stores and vector search, and says it can scale to petabytes of storage. It also markets ScyllaDB as a replacement for DynamoDB and Cassandra.

There are two deployment paths in the published product information: ScyllaDB Cloud, a managed database service, and ScyllaDB Enterprise, which teams run on their own infrastructure. Cloud plans are organized around resource-based pricing rather than per-request charges, according to the pricing information. That distinction matters when comparing it with a database billed by request volume, but it does not make ScyllaDB automatically cheap: monthly and annual prices are not published.

The product is most relevant when a team has a specific scale or latency problem to solve. If your application does not need those characteristics, its operational and licensing trade-offs may be hard to justify.

ScyllaDB’s stated fit is workloads where response time and throughput matter at the same time. The homepage says it supports inference with predictable single-digit millisecond latency, feature stores with millions of operations or features, and contextual vector search across billions of embeddings. It also claims high throughput for large AI workloads and storage scaling to petabytes. These are vendor claims, not independent benchmarks in the published material, so treat them as requirements to validate against your own workload.

The managed service gives teams an alternative to running the database themselves. Its Standard plan lists one daily backup, resource-based pricing with no per-request charges, and an uptime SLA shown as 99.99% in the plan details; the FAQ lists 99.9%, so confirm which applies to your contract. Professional adds multi-region active-active high availability and disaster recovery, while Premium adds a dedicated Technical Account Manager and bring-your-own encryption key.

For teams evaluating a Cassandra or DynamoDB replacement, the value proposition is straightforward: keep a distributed NoSQL model while targeting demanding latency and scale. The practical case depends on workload fit, migration effort, and what the eventual quote costs.

The biggest buying drawback is price opacity. ScyllaDB does not publish monthly or annual plan prices, and self-managed Enterprise requires a custom quote based on provisioned vCPUs and cluster sizing. The pricing information says one- and three-year contracts can save up to 70% or more against on-demand rates, but without public rates, that discount is difficult to assess. A 30-day Developer Free Trial and 48-hour Production Evaluation are listed; neither reveals the long-term bill.

Also budget for possible extras: hourly on-demand rates or Flex Credits, cloud-provider charges for cross-zone or cross-region data transfer, and backup storage beyond the included daily backup. Standard lists 8x5 P1 support with a two-hour response; Professional lists 24x7 with a one-hour response, and Premium lists 24x7 with a 15-minute response.

Licensing is another point to verify before self-hosting. In one Reddit thread, a commenter said the license change requires a commercial license above 50 vCPUs or 10 TB of available storage. That is a user report, not a substitute for checking ScyllaDB’s current license terms. Reddit users also describe pricing as difficult for smaller companies.

ScyllaDB does not publish monthly or annual prices for its Cloud tiers, so there’s no public dollar figure to compare. The pricing information we have lists three plans: Standard, Professional and Premium. Each step adds capabilities, but the price jump between tiers is not published.

Standard includes resource-based pricing with no per-request charges, one daily backup and an uptime SLA listed as 99.99%; the FAQ lists 99.9%, so confirm the commitment in your contract. Professional adds multi-region active-active deployment and a 24x7 P1 response within one hour. Premium adds a 15-minute P1 response, bring-your-own encryption key and a dedicated technical account manager.

Budget for possible extras: backup storage beyond the included daily backup, cross-AZ or cross-region data transfer, and on-demand hourly rates or Flex Credits. Annual and multi-year contracts may save up to 70% or more versus on-demand rates, according to the pricing information, but get a quote to verify your actual total. Self-managed Enterprise also requires a custom quote, with licensing based on provisioned vCPUs and cluster sizing.

Treat a move to ScyllaDB as a database migration, not a simple plan change. The published product information positions it as a Cassandra or DynamoDB replacement, but it does not document migration tooling, compatibility limits, data-export formats or a migration timeline. Ask ScyllaDB how your schema, application queries and operational processes would transfer before committing.

Cloud pricing lists a 30-day Developer Free Trial and a 48-hour Production Evaluation. Those offer a way to evaluate the service, but the published details do not say whether they include migration assistance or how to export data afterward. Confirm the exit process, transfer costs and any contract obligations in writing. ScyllaDB’s Reddit discussion and user reports were not included in the published material we were given, so we can’t substantiate claims about why customers leave. For a switch in either direction, make data portability and a tested rollback plan part of the evaluation—not assumptions.