If your team already manages infrastructure through Terraform, you shouldn't have to leave that workflow behind just to bring your resources into Sedai. Starting today, you don't have to.
We're excited to announce the Sedai Terraform provider, a new way to onboard AWS accounts, Kubernetes clusters, Azure and GCP resources into Sedai — no UI, no separate tooling, no new process to learn. If you already know Terraform, you already know how to use it.
Why we built this
Sedai's onboarding has always evolved alongside how our customers actually work. It started as a point-and-click, UI-driven experience. Over time, we added SDKs and APIs so teams could onboard resources programmatically as part of their own automation. The Terraform provider is the next step in that same journey: giving teams the flexibility to onboard resources in whatever way fits best within their existing tooling and processes.
This particular capability was shaped directly by customer need. A large, highly federated organization using Sedai asked for exactly this: a way to standardize onboarding across dozens of internal teams without asking every engineer to learn a new tool or process. Their central platform team already maintains shared infrastructure-as-code patterns for provisioning cloud accounts and clusters; they just wanted Sedai onboarding folded into that same workflow.
How it works
Terraform providers are the standard way infrastructure-as-code tools read your configuration and provision resources, whether that's an AWS account, a set of VMs, or a Kubernetes cluster. The Sedai Terraform provider works the same way: it reads your existing Terraform configuration and onboards the corresponding resources into Sedai automatically, right alongside the infrastructure being provisioned.
In practice, that means:
- Provision and onboard in one step. Spin up an AWS account, Kubernetes cluster, Azure resource, or GCP resource, and onboard it into Sedai as part of the same Terraform apply. No separate manual step required.
- Built on our existing SDK and APIs. The provider is powered by the same SDK and APIs that already back Sedai's programmatic onboarding, so it's a natural extension of infrastructure you can already trust.
- Works for short-lived and long-lived resources alike. Whether it's a cluster spun up for a few weeks of feature testing or a permanent production account, the provider makes sure Sedai optimization is available for the full lifecycle of the resource, not just the resources that happen to get onboarded manually.
- Fits your existing playbooks. Platform and architecture teams can add the Sedai provider to the shared IaC patterns they already hand down to other teams, so onboarding becomes an inherited default rather than an extra checklist item.
The provider is open source and published on Terraform's public registry, so it's easy to find, inspect, and adopt using the same conventions you already use for any other provider.
Who this is for
This is especially relevant if you're on a platform engineering, architecture review, or governance team responsible for defining how infrastructure gets provisioned across an organization. It lets you build Sedai onboarding directly into the standards you already maintain, rather than layering on a separate process for individual teams to follow. The engineers and DevOps teams actually building and owning that infrastructure benefit too — they get Sedai coverage automatically, without having to learn Sedai's UI or talk to a separate team to get set up.
Part of a bigger picture
This launch is one piece of a broader goal: making Sedai easy to work with wherever your team already operates — through APIs, SDKs, and now infrastructure-as-code tooling — rather than requiring everyone to come to a single interface. Meeting teams in their existing tools, instead of asking them to adopt new ones, is a theme you'll continue to see from us.
Get Started
The Sedai Terraform provider is generally available today. Documentation, setup instructions, and provider details are available through the public Terraform registry.
