SlicingDice Documentation

SlicingDice - The All-in-One Solution Documentation

Welcome to the SlicingDice documentation. You'll find comprehensive guides and documentation to help you start working with SlicingDice as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Guides

Data Security

We take data security very seriously. Although a data breach would not cause a meaningful effect to our customers, as our data store is fully encoded, we clearly understand that security is the base of a Database as a Service offering.

Whenever you want, you are welcome to audit our security policies and procedures. Just let us know.

Check this video from SlicingDice's Founder & CEO detailing how we handle data security to make sure no one will ever get unauthorized access to your data.

Our proprietary data encoding

As we've developed our own database technology from the ground up, all data is stored in our own encoded format, making it harder for an attacker to get access to the original format of the stored data.

The only way for us to face a data breach would be by having full infrastructure hacking that would allow the attacker to get access to data and the source code of our processing engine, in order to reverse engineer the data encoding logic. Other than that, as we store data in a hashed and encoded binary format, no one would be able to really guess what is inside our files.

Infrastructure security

From an infrastructure perspective, we strictly follow recommended approaches in server hardening and sensible information management. One example of such recommended approach is that we don’t allow any SSH access to our servers. All servers are accessed exclusively using KVM over IP provided by our infrastructure partners. We know this is a radical approach, but we take security very seriously.

Security and privacy compliance

SlicingDice is compliant with the highest security standards and regulations.

What's Next

Data Durability

Data Security

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.