Use Case
Healthcare Tech Company
Delivering secure, compliant services at scale across Cloud Foundry and Kubernetes
Challenge
As the telehealth provider scaled its engineering teams and expanded internationally, its platform grew increasingly complex–now spanning hundreds of microservices, databases, and other data-related services deployed across both Cloud Foundry and Kubernetes. Cloud Foundry was favored for its speed and developer self-service, while Kubernetes was used for custom workloads requiring fine-grained control. However, managing data services consistently across these platforms became a growing pain point. Core systems supporting patient data, scheduling, and compliance relied on databases that lacked unified provisioning, governance, and observability, creating operational overhead and risk.
Solution
As the company scaled past 200 applications and expanded across teams and regions, managing app delivery, compliance enforcement, and developer velocity became increasingly complex. To bring structure and governance to a fast-growing platform ecosystem, they adopted a9s Cloud Foundry as their centralized application platform. It provided built-in automation, self-service for developers, and consistent governance policies, making it easier to roll out secure, compliant services across internal teams and global markets.
To address database challenges, the platform team deployed the a9s Data Service Bundle, switching from unmanaged open-source PostgreSQL and Redis to a9s PostgreSQL and a9s KeyValue (a production-grade Redis-compatible service based on Valkey). These VM-based data services delivered high availability, automated backups, observability, and hardened security out of the box.
As workloads expanded into Kubernetes, the company faced a new challenge: exposing their robust VM-based data services to container-native environments without duplicating or reengineering their infrastructure. To solve this, they implemented Klutch, the open-source abstraction layer that bridges Kubernetes and VM-based data services. This allowed developers to consume a9s services through a Kubernetes-native interface, while platform teams retained full control over lifecycle, security, and compliance across both environments.
Impact
The move to a9s Cloud Foundry and Klutch-enabled data services gave the organization a platform that satisfied internal compliance requirements while enabling teams to move fast without reinventing infrastructure. Developers could focus on shipping features, while platform teams gained centralized control over service configuration, access, and updates. Time-to-provision dropped dramatically, and platform consistency across CF and Kubernetes ensured fewer misconfigurations, tighter access controls, and a significant reduction in compliance drift.
By the Numbers
Let's talk
Have any questions?
Reach out to learn more about our easy migration process and the benefits of a9s Cloud Foundry, our data services, and even Klutch for your business.
We’ll get back to you quickly!
