Run Microsoft SQL Server
on Kubernetes
Solanica Platform deploys and operates SQL Server on any Kubernetes cluster, in the cloud or in your own data center. Failover, backups and upgrades are automated. Built on the open-source OpenEverest project.
What it costs
A typical production setup: 16 vCPU, 64 GB RAM, 1 TB of storage and a high-availability replica. Here is the same workload on Azure SQL Managed Instance and on Kubernetes with Solanica.
Azure SQL Managed Instance
General Purpose tier, pay-as-you-go
SQL Server on Kubernetes with Solanica
Your cluster, your SQL Server licenses
No cloud lock-in
Azure SQL, Amazon RDS and Cloud SQL each tie SQL Server to one provider. With Solanica, the same deployment runs on any Kubernetes cluster.
Any Kubernetes cluster
AKS, EKS, GKE, OpenShift, Rancher or upstream Kubernetes on-premises. The manifests are the same everywhere, so moving between environments doesn't mean rewriting your tooling.
Standard formats and tools
Backups go to S3-compatible storage you control and metrics go to Prometheus. Your DBAs keep using the SQL Server tools they already know.
Your licensing choice
Bring existing licenses through Software Assurance, use Developer Edition for dev and test, or Express for small workloads.
Open source underneath
The platform is built on OpenEverest, an open-source set of Kubernetes operators for databases. You can read the code and run it yourself.
How it works
You describe the database you want as a single Instance in OpenEverest. The mssql provider creates the SQL Server resources in your cluster and keeps them in the state you declared. Read more in the MSSQL Provider and MSSQL Operator docs.
What's included
The operations you would expect from a managed SQL Server service, running in your own cluster.
High availability
Always On availability groups managed by the operator, with automatic failover and synchronous or asynchronous replicas.
Read the docs →Backup and restore
Scheduled full and differential backups to S3-compatible storage, with point-in-time restore.
Read the docs →Monitoring
SQL Server metrics exported to Prometheus, with Grafana dashboards and alerts for replication lag and resource usage.
Read the docs →Security
TLS for client connections, Kubernetes RBAC and network policies, and credentials kept in Kubernetes Secrets or an external vault.
Read the docs →From pilot to production
Our engineers work with your team from the first cost estimate to running in production.
Assessment
We look at your current SQL Server estate and licensing, and estimate what it would cost to run on Kubernetes.
Pilot
You deploy on your own cluster, move a real workload over, and test failover, backups and monitoring against your requirements.
Production
We help you roll out with a repeatable setup that fits your GitOps workflow, and our team stays on hand for support.
Talk to us about your SQL Server workloads
Tell us about your setup and we will connect you with the engineers who build and support the platform.