Development teams expect cloud-like speed when they need a database, a message broker, or a streaming cluster. For many organisations, moving sensitive data to public cloud services is not an option, whether for regulatory reasons, sovereignty requirements, or cost predictability.

evoila delivers Database as a Service on your own infrastructure: a turnkey DBaaS for PostgreSQL, MySQL, Kafka, and RabbitMQ on VMware Cloud Foundation, or the same services on Kubernetes through production-grade Operators.

Key benefits at a glance:

• Self-service provisioning of databases and data services in minutes, not days
• Full digital sovereignty, your data never leaves your infrastructure
• Two deployment paths, VMware DSM for VCF environments, Kubernetes Operators for K8s-native setups
• Production-grade configurations from the first deployment

The gap between what developers need and what infrastructure teams can deliver is widening. Application teams want to spin up a PostgreSQL instance, a Kafka topic, or a RabbitMQ queue in minutes. Instead, they submit a ticket and wait days or weeks – with inconsistent configurations, unclear security policies, and no standardised lifecycle management.

At the same time, many organisations cannot simply move these workloads to the public cloud. Financial regulations, data residency requirements, or cost unpredictability make on-premises operation a necessity, not a preference. The result: teams are stuck between slow internal provisioning and inaccessible cloud services. Innovation stalls, shadow IT grows.

Path 1: VMware Data Service Manager (recommended for VCF environments)

For organisations running VMware Cloud Foundation, DSM is the fastest path to on-premises DBaaS. It provides a fully integrated self-service portal where development teams provision PostgreSQL, MySQL, and other data services on demand – with standardised configurations, automated backups, built-in monitoring, and policy-based governance. No Kubernetes expertise required.

DSM handles the full database lifecycle: provisioning, high-availability configuration, point-in-time recovery, scaling, patching, and decommissioning. Platform teams define service tiers with resource limits and security policies; application teams consume them through a portal or API. Your data stays on your infrastructure, under your governance, with enterprise-grade auditability.

This is our recommended starting point for most enterprise environments.

Operations & Managed Services

Every deployment path – DSM or Kubernetes – can be operated by evoila as a managed service. Our operations team provides proactive monitoring, incident management, performance tuning, security patching, and 24/7 on-call support. You choose the level that fits your needs.

Path 2: Kubernetes Operators

For organisations with existing Kubernetes infrastructure or requirements for maximum portability and open-source sovereignty, we deploy data services using production-grade Operators.

PostgreSQL – We deploy either on VMware Tanzu for Postgres, the same enterprise-supported PostgreSQL version that is used in DSM, or CloudNativePG, a mature CNCF-recognized operator that manages high-availability replica sets.

MongoDB – For workloads requiring schema flexibility and horizontal scalability, we deploy MongoDB on Kubernetes with the Percona or Community Operator. Automated replica sets, sharding, failover, backup scheduling, and security hardening are managed declaratively.

Apache Kafka – Using the Stackable Kafka Operator, we deploy multi-broker clusters with rack-aware replication, topic management, Kafka Connect integration, and Prometheus/Grafana monitoring. Kafka serves as the backbone for real-time data pipelines and event-driven architectures.

RabbitMQ – The RabbitMQ Cluster Operator handles clustered deployments with quorum queues, federation for multi-site messaging, and flexible routing (topic, fanout, header-based). Ideal for application integration and asynchronous microservice communication.

On top of these individual services, we build a unified self-service layer. Platform teams define service offerings with standardised configurations, resource limits, and security policies. Application teams provision what they need through APIs – no tickets, no waiting, no configuration drift.

VMware Data Service Manager DSM is an infrastructure management layer built into VMware Cloud Foundation that brings cloud-like self-service capabilities to on-premises environments. Platform teams define database service offerings with standardised configurations, resource limits, and security policies. Application teams provision these services on demand through a portal or API – with automatic backup, monitoring, and lifecycle management built in. DSM supports single-server and cluster deployments for PostgreSQL, including high-availability with automated failover and point-in-time recovery to S3-compatible storage. The key advantage: your data stays on your infrastructure while your teams get the speed and convenience they expect from cloud-native services – without needing Kubernetes expertise.

Kubernetes Operators: How they work An Operator is a software extension to Kubernetes that encodes operational knowledge – the kind of expertise a skilled database administrator brings – into automated, declarative workflows. Instead of manually creating a PostgreSQL replica set, configuring replication, setting up backups, and scripting failover, you define the desired state in a YAML manifest, and the Operator continuously ensures that state is maintained. If a node fails, the Operator handles failover. When you change the configuration, it performs a rolling update. When you need to scale, it adds replicas automatically.

PostgreSQL and MongoDB on Kubernetes For PostgreSQL, CloudNativePG manages replica sets, automated failover, backup and recovery (including point-in-time restore to S3-compatible storage), TLS certificate management, and RBAC configuration. For MongoDB, the Percona/Community Operator handles replica sets, sharding, encryption, and automated failover. All resources are defined as Custom Resource Definitions (CRDs), integrating natively with Helm, ArgoCD, and Terraform.

RabbitMQ on Kubernetes The RabbitMQ Cluster Operator handles clustered instances with quorum queues, persistent storage, automatic peer discovery, federation plugins for multi-site messaging, and Prometheus-based monitoring.

Infrastructure-as-Code throughout Every deployment follows infrastructure-as-code principles. Service definitions, configurations, and policies are version-controlled in Git and applied through GitOps workflows (typically ArgoCD or Flux). This ensures every environment is reproducible, auditable, and consistent.

Underlying infrastructure VMware DSM runs on VMware Cloud Foundation. Kubernetes Operators run on bare metal, VMware vSphere (using vSphere Kubernetes Service), or any CNCF-conformant distribution. We design the underlying compute and storage layer to meet the performance requirements of stateful data workloads – including dedicated storage classes for high-IOPS database volumes and node affinity rules for data locality.

evoila brings together deep VMware and Kubernetes infrastructure expertise with deep data service knowledge. The engineers do not just deploy DSM or install Operators. They understand database internals, replication topologies, performance tuning, and the failure modes of every service we manage. evoila is the leading Broadcom partner in Europe, with extensive VMware Cloud Foundation and Kubernetes experience, and holds ISO 27001, BSI C5, and TISAX certifications.

The managed operations team runs Kafka and RabbitMQ environments for large European enterprises in production, with on-call response, incident management, and proactive monitoring. With 600+ specialists across 15+ countries, evoila is large enough for enterprise-grade support and structured enough to stay close to the work.