Some of the most common questions we, Satorians, encounter are about the many Satori deployment options, whether or not this is a fully SaaS solution, and whether or not you can host your own Satori Data Access Controller (DAC). In this article, I’d like to answer these questions and explain some of the specific reasons behind the design. When we first created Satori, we came with experience building both large-scale, multi-tenant SaaS services and on-premises products. We came prepared and we're not biased towards a specific approach. We knew that there would be some organizations that prefer the advantages of a multi-tenant SaaS solution and others that prefer to host their own private Satori DACs. The main advantages of a multi-tenant solution are:
- Satori takes care of all of the DevOps and Infrastructure involved.
- Satori frequently updates our SaaS multi-tenant DACs, so customers do not need to do the upgrades themselves.
- This deployment option has a better Total Cost of Ownership (TCO), as Satori is in charge of the computation, storage, and other infrastructure expenses and also provides upgrades and administration.
Satori’s Three Deployment OptionsWe thus designed Satori with three different deployment options in mind:
- SaaS: where the entire infrastructure is maintained by Satori and shared across customers. These DACs are receive updates as soon as they are available, and the customers don’t need to do anything to maintain the product itself.
- Private SaaS: where the DAC is deployed by Satori on dedicated resources for that customer. This option fits customers who require separation from other customers due to compliance or security requirements but prefer not to maintain the infrastructure.
- Customer Hosted: where the customer installs Satori on a Kubernetes cluster in their VPC and is responsible for the network and infrastructure of the deployment.