Compare Products
Cloud
Cloud
Self-Managed
Self-Managed
Standard
Key features:
- Standard Support
- 99.9% SLA
- Workspaces
- Unlimited Storage
- MySQL compatibility
- SOC2 Type 2, ISO27001, GDPR/ CCPA, HIPAA
Premium
Everything in Standard, plus:
- Standard Support
- 99.99% SLA
- Point-in-time Recovery
- Multi-AZ failover
- Audit logging
Dedicated
Everything in Premium, plus:
- Silver Support
- Dedicated cloud account
- Customer-Managed Encryption Keys
Cloud
Pricing Plans | Cloud | Self-Managed | |||
|---|---|---|---|---|---|
Standard$600 Free Credits | PremiumContact us | DedicatedContact us | StandardGet Started Free | Premium30 Day Trial | |
| Service Levels and Pricing | |||||
| Service Levels and Pricing | |||||
Hosting | AWS, Azure, GCP | AWS, Azure, GCP | AWS, Azure, GCP | Self-hosted | Self-hosted |
SLAs Meet enterprise-grade requirements for availability. | 99.9% | 99.99% | 99.99% | ||
Meet enterprise-grade requirements for availability. | |||||
Support tier inclusion Higher Support Tiers may be purchased separately. | Standard | Standard | Silver | Standard | Standard |
Higher Support Tiers may be purchased separately. | |||||
Pricing More detailed usage pricing for cloud can be viewed here. Contact us for bulk pricing discounts and self-manged pricing. | Yearly Contract Contact for pricing | Yearly Contract Contact for pricing | |||
More detailed usage pricing for cloud can be viewed here. Contact us for bulk pricing discounts and self-manged pricing. | |||||
| Core Database Engine | |||||
| Core Database Engine | |||||
Universal Storage Unique to SingleStoreDB, Universal Storage unifies rowstores and columnstores in one table type. | |||||
Unique to SingleStoreDB, Universal Storage unifies rowstores and columnstores in one table type. | |||||
MySQL wire-compatible, ANSI SQL Data Model ANSI SQL with MySQL wire compatibility. Support for Stored Procedures, User Defined Functions. | |||||
ANSI SQL with MySQL wire compatibility. Support for Stored Procedures, User Defined Functions. | |||||
Multimodel Relational, JSON, Full Text Search, Geospatial, Time-series. | |||||
Relational, JSON, Full Text Search, Geospatial, Time-series. | |||||
Streaming Data Pipelines Easily build sophisticated data import operations, eliminating the cost and complexity of ETL tooling. | |||||
Easily build sophisticated data import operations, eliminating the cost and complexity of ETL tooling. | |||||
Advanced Query Execution Code Generation, Vectorization, SIMD, Flexible Parallelism. | |||||
Code Generation, Vectorization, SIMD, Flexible Parallelism. | |||||
AI vector matching functions DOT_PRODUCT and EUCLIDEAN_DISTANCE functions for matching images or other objects, based on deep neural network vector embeddings. | |||||
DOT_PRODUCT and EUCLIDEAN_DISTANCE functions for matching images or other objects, based on deep neural network vector embeddings. | |||||
| Developer tools & connectors | |||||
| Developer tools & connectors | |||||
ODBC, JDBC, HTTP drivers Native drivers for ODBC, JDBC and HTTP connections (Data API). | |||||
Native drivers for ODBC, JDBC and HTTP connections (Data API). | |||||
Code Engine Powered by Wasm Extend SQL with functions written in C/C++/Rust & more. Runs in-database in a safe sandbox. | |||||
Extend SQL with functions written in C/C++/Rust & more. Runs in-database in a safe sandbox. | |||||
Connectors for Analytics and BI tools Power BI, Cognos, Tableau, etc. Read more. | |||||
Power BI, Cognos, Tableau, etc. Read more. | |||||
Data integration ETL, CDC/ Replication tools like dbt, AWS Glue, Azure Data Factory, Arcion etc. Read more. | |||||
ETL, CDC/ Replication tools like dbt, AWS Glue, Azure Data Factory, Arcion etc. Read more. | |||||
| Availability and Disaster Recovery | |||||
| Availability and Disaster Recovery | |||||
High Availability Data is replicated accross nodes to ensure that it remains available in case a node is lost. | |||||
Data is replicated accross nodes to ensure that it remains available in case a node is lost. | |||||
Multi-AZ Failover Durability against the failure of an entire cloud availability zone. | |||||
Durability against the failure of an entire cloud availability zone. | |||||
Point-in-Time Recovery Allows users to pick an exact point in time to restore to, down to the microsecond, with fully adjustable retention periods. Requires Unlimited Storage. | |||||
Allows users to pick an exact point in time to restore to, down to the microsecond, with fully adjustable retention periods. Requires Unlimited Storage. | |||||
Disaster Recovery Self-Managed: Support for disaster recovery (DR) via replication from one cluster to another with REPLICATE DATABASE. Cloud: Multi-AZ Failover provides within-region DR, tolerating loss of full AZ. | |||||
Self-Managed: Support for disaster recovery (DR) via replication from one cluster to another with REPLICATE DATABASE. Cloud: Multi-AZ Failover provides within-region DR, tolerating loss of full AZ. | |||||
| Scalability | |||||
| Scalability | |||||
Workload Management Always-on intelligent throttling of queries to avoid system overload | |||||
Always-on intelligent throttling of queries to avoid system overload | |||||
Unlimited Storage Unlimited Storage (also known as Bottomless Storage) provides separation of Compute and Storage. Works with Amazon S3 (or 100% S3-compatible object store), Google Cloud Storage, Azure Blob storage. Note that Unlimited Storage on Self-Managed Standard edition is for cloud object stores only. | |||||
Unlimited Storage (also known as Bottomless Storage) provides separation of Compute and Storage. Works with Amazon S3 (or 100% S3-compatible object store), Google Cloud Storage, Azure Blob storage. Note that Unlimited Storage on Self-Managed Standard edition is for cloud object stores only. | |||||
Compute Workspaces Workspaces (1) allow elastic scaling, letting you to scale your read-only query workload on fully-up-to-date replicas on separate hardware, and (2) provide isolation for subsets of your analytical query workload. | |||||
Workspaces (1) allow elastic scaling, letting you to scale your read-only query workload on fully-up-to-date replicas on separate hardware, and (2) provide isolation for subsets of your analytical query workload. | |||||
| Security and Networking | |||||
| Security and Networking | |||||
Authenticate via JWT JSON Web Token | |||||
JSON Web Token | |||||
Engine RBAC Role-Based Access Control | |||||
Role-Based Access Control | |||||
Data encryption (AES_ENCRYPT) AES_ENCRYPT/DECRYPT functions supporting 256-bit keys and EBC, GCM, and CBC modes, with initialization vectors. | |||||
AES_ENCRYPT/DECRYPT functions supporting 256-bit keys and EBC, GCM, and CBC modes, with initialization vectors. | |||||
Encryption of data in transit (SSL/TLS) Support for SSL/TLS (1.2) for all connection to ensure security of data while in transit. | |||||
Support for SSL/TLS (1.2) for all connection to ensure security of data while in transit. | |||||
Encryption of data at rest (AES-256) Support for encryption of data on persistent storage | |||||
Support for encryption of data on persistent storage | |||||
Single Sign-On Okta, Ping, Azure AD | |||||
Okta, Ping, Azure AD | |||||
Federated Authentication- SAML Support for Security Assertion Markup Language (SAML), an open standard for federated authentication | |||||
Support for Security Assertion Markup Language (SAML), an open standard for federated authentication | |||||
Federated Authentication- OAuth Support for OAuth, an open standard for federated authentication | |||||
Support for OAuth, an open standard for federated authentication | |||||
Private network connections Ability to secure the connectivity between customer and database using the private communication channel | |||||
Ability to secure the connectivity between customer and database using the private communication channel | |||||
Audit Logging (native) Logging of all database activities to an external location. | |||||
Logging of all database activities to an external location. | |||||
Audit Logging (3rd party tools) Ability to use 3rd party tools of choice to write audit logs details. | |||||
Ability to use 3rd party tools of choice to write audit logs details. | |||||
Customer-Managed Encryption Keys (CMEKs) Support for customer to use their own key vault services and keys for encryption of data at rest, allowing customer to revoke access to all data by withdrawing keys. | |||||
Support for customer to use their own key vault services and keys for encryption of data at rest, allowing customer to revoke access to all data by withdrawing keys. | |||||
| Manageability and Observability | |||||
| Manageability and Observability | |||||
Resource Governance User-configurable control of memory, CPU, and other resources, enabling isolation of subsets of workload in different resource pools | |||||
User-configurable control of memory, CPU, and other resources, enabling isolation of subsets of workload in different resource pools | |||||
Management API (REST) Deploy and manage workspaces through our flexible REST API. | |||||
Deploy and manage workspaces through our flexible REST API. | |||||
Suspend & Resume Easily suspend & resume compute to minimize TCO. | |||||
Easily suspend & resume compute to minimize TCO. | |||||
Cloud Monitoring Realtime and historical monitoring of CPU, persistent cache, memory, queries per second and much more. | |||||
Realtime and historical monitoring of CPU, persistent cache, memory, queries per second and much more. | |||||
Automated Updates Updates are automatically applied to reduce operational costs. | |||||
Updates are automatically applied to reduce operational costs. | |||||
| Show more | |||||
| Get Started | Learn More | ||||
| Get Started | Learn More | ||||
FAQ
Cloud
Cloud
Self-Managed
Self-Managed
No. SingleStore utilizes both memory, flash, and spinning disk. SingleStore uniquely accelerates ingest and query performance with memory optimized tables to deliver persistence with full ACID compliance, high availability, and disaster recovery so your data is always accessible.
SingleStore is a next generation, distributed database built from the ground up for maximum performance for transactions and analytics. The SingleStore server includes its own storage engine and SQL-based execution engine built around scalable distributed execution and lock-free data structures. SingleStore and MySQL servers do not share any code, but SingleStore is compatible with MySQL client software. SingleStore uses the same wire protocol as MySQL and supports similar SQL syntax as MySQL for easier compatibility.
SingleStore is designed to support real-time applications and analytics with no unnecessary data movement or complexity. SQL is a proven, pervasively used language for writing and retrieving data. It provides rich descriptive capabilities that are interoperable with a large ecosystem of tools, is a straightforward skill to find and learn, and provides the easiest and fastest way to perform powerful analytics.
SingleStore offers 24x7 support across three support tiers: Standard, Silver and Platinum level support. For more detail, please refer to our support page
Get specific pricing details for different deployment sizes at https://www.singlestore.com/cloud-pricing/
SingleStore automatically provisions infrastructure, deploys and configures cluster software, maintains availability, provides scalability, performs backups, and handles software upgrades including SingleStore, operating system, and system software.
The easiest way to get data into SingleStoreDB Cloud is by uploading your dataset to Amazon S3 or Google Cloud Storage and using SingleStore Pipelines to ingest your data quickly. To get started we have a guide available here.
SingleStore is built on a cloud-native and highly resilient architecture that features high availability within the cluster. When cloud instances fail, SingleStoreDB transparently handles the failures, replaces instances, and maintains cluster availability to the application.
When you suspend a workspace, we stop billing for that workspaceas soon as the workspace is suspended. When your workspace is paused, you will be charged for the storage within the workspace group.
Workspace and storage are billed separately to make it easier for you to see the level of compute resources consumed. Workspace is metered granularly by the second. Storage charges are only incurred for storage used and are calculated based on the average total number of GB used per month. Object storage is allocated to SingleStore nodes and stores node-specific data as well as columnstore tables.
Backup and Point In time Recovery are charged at the standard storage rate that depends on the regional tier that you stored your data.
Correct, we charge after compression which is on average 80% (e.g. 100 GB of raw data will be compressed as 20 GB on average)
Purchasing commitments are a great way to save up on your workspace resources compared to on-demand pricing. Contact us to learn more about commitment.
We support direct payment methods such as credit cards and cloud marketplaces (Azure, GCP and AWS).
We do not charge for loading data into SingleStore (Ingress). However, such operations might incur costs from the service you load data from. Using features such as exporting or replicating data into different regions or cloud providers or other the internet, will incur costs in line with the starting price band that cloud providers commonly charge.
The cost of SingleStoreDB is determined by actual usage which varies based on the individual customer application. We recommend trying SingleStoreDB with on-demand pricing to develop and test so you can estimate the monthly cost. When your application workload moves to production, it will be a good time to take advantage of our commitment pricing model.
Example # 1- Learn, develop and test SingleStore
A customer is trying SingleStore 8 hours, 20 days a month on a S00 Standard in a Tier 1 Region. For 15 days in a month, 100 GB has been stored. The rest of the month (15 more days), 500 GB has been stored. During that month, 500 GB of data was ingested into SingleStore.
Here is how your bill for that month would look like:
Info | Usage | Billing |
|---|---|---|
Workspace | S00 - 8 hours x 20 days x 0.25 credits /hour = 40 credits | Cost: 40 credits x $3.2 /credit = $128 |
Average Storage | (24 hours x 15 days x 100 GB + 24 hours x 15 days x 500 GB) / (30 days x 24 hours) = 300 GB | Cost: 300 GB x $0.023 /GB = $6.9 |
Data Transfer | Ingress: 500 GB | Cost: 500 GB (Ingress) x $0 = $0 |
Example # 2 - Development and Production over SingleStore
You have a multi-tenant application serving various customer sizes in a SingleStore Tier 2 region. You have adopted the following architecture and usage pattern:
Info | Workspace | Usage |
|---|---|---|
Free tier tenants | S4 - fits 2,000 tenants | Workspace up throughout the month 1 GB of data ingested per day, no data deletion Started the month with 500 GB, finishing the month with 530 GB |
Paid tenants | S8 - fits 100 tenants | Workspace up throughout the month 100 GB of data ingested per day, no data deletion Started the month with 20 TB, finishing the month with 23 TB |
Dev/Test environment | S00 for dev S8 for test | S00 workspace: ON 8 hours a day 20 days a month. S8 workspace: ON 4 hours a day, 5 days a month. Across workspaces 500 GB of storage throughout the month. |
Here is how the bill for that month looks like:
Info | Usage | Billing |
|---|---|---|
Workspace | S4 (Prod) - 24 hours x 30 days x 4 credits /hour = 2,880 credits S8 (Prod) - 24 hours x 30 days x 8 credits /hour = 5,760 credits S00 (Dev) - 8 hours x 20 days x 0.25 credits /hour = 40 credits S8 (Test) - 4 hours x 5 days x 8 credits /hour = 160 credits | Cost: (2,880 + 5,760 + 40 + 160) credits x $3.2 /credit = $28,288 |
Average Storage | Free tenant prod storage: 515 GB Paid tenant prod storage: 21,980 GB Dev + Test storage: 500 GB | Cost: 22,995 GB x $0.025 /GB = $574.9 |
Data Transfer | Ingress: 500 GB | Cost: 500 GB (Ingress) x $0 = $0 |
