Over the past few weeks, I've been leading an initiative to integrate the Serverless Framework with our Omnistrate platform. Today, I'm excited to share the technical details of this integration and how it can help developers maintain their serverless applications while gaining enterprise SaaS capabilities.

Many B2B startups start their cloud journey with AWS ECS or GCP Cloud Run. It's understandable—they're familiar, quick to set up, and tightly integrated with the hyperscalers' ecosystems. Throw in some Terraform, and you have a hello-world deployment workflow that seems "good enough" to get your SaaS up and running.

But "good enough" quickly breaks down as you scale.

A while ago I wrote, why Terraform tool is not enough for SaaS here. Today, I am extending the same series for Helm -- covering the purpose they serve and why they are NOT enough to build your cloud offering or control plane.

Helm charts are widely used for Kubernetes application deployment, offering a templated approach to package and manage applications. However, when it comes to building a full-fledged SaaS control plane, relying solely on Helm is not enough.

We think that Terraform is an excellent IaC tool if you want to setup your cloud infrastructure once. However, when it comes to SaaS, we feel that it falls short on many grounds. Here are the basic set of things that are missing in Terraform to even accomplish proper infrastructure management for building SaaS.

I was among the authors at AWS who pioneered the first SaaS control plane back in 2009, laying the groundwork for many SaaS offerings both within and beyond AWS. Crafting the SaaS control plane, we delved deep into fundamental questions: