SlicingDice is a petabyte-scale analytical database. There is no infrastructure to manage and you don't need a database administrator, so you can focus on analyzing data to find insights for your business. SlicingDice provides a multi-purpose analytical database for all sizes of companies, from startups to Fortune 500.
Important features for an Analytical Database
SlicingDice features and capabilities
Queries under 10 seconds. Always.
Yeah, you read right: we have a public commitment of making your queries under 10 seconds, doesn't matter how much data you have or how complex is it. If your query is slower we believe it’s our responsibility, not yours.
Read more about our Speed & Infrastructure
Zero Maintenance Necessities
On SlicingDice you simply need to insert your data and query it using SQL or our REST API. There is no maintenance for you to worry about, no tuning, no tweaking databases. Nothing. We do all the work for you.
Totally serverless - No server to manage.
Forget about infrastructure provisioning. We are a serverless solution, which means you don’t need to worry about infrastructure at all. SlicingDice was built for you to spend your valuable time generating insights and value for your business, not managing infrastructure.
Learn more about the reasons for selecting a serverless solution
Unlimited and Free Data Storage
By selecting our pay-per-column pricing model, you can store as much data (rows) as you need without increasing costs, as you are only charged by the number of columns you have, not by the volume of data you insert.
Read more about our proprietary technology
You can batch load or stream your data to SlicingDice the same way, there is no special configuration or additional costs. All data inserted on SlicingDice is available for querying within 5 seconds after arriving on our servers.
Immediate data availability for querying
Any data you insert on SlicingDice, doesn't matter if it was batch loaded or inserted via streaming using our API, will be available for querying within 5 seconds after the API request was received.
Check the docs about Insertion Speed