Version 3.0.0

October 13, 2026

SleakOps Team

major release · October 13, 2026

🚀 New Features

Import Existing AWS (beta)
SleakOps can now adopt your existing infrastructure — AWS accounts, networks, EKS clusters, domains, databases and other dependencies, projects and their variable groups — instead of provisioning everything from scratch. Nothing gets recreated: imported resources are flagged as such, databases can be onboarded by pasting their connection string, and Valkey is supported alongside the other managed dependencies.
Static Sites
A new static project type builds your frontend from Git and serves it on your own domain through S3 and CloudFront, with no container or web server to maintain.
Manifests (beta)
The manifests SleakOps generates for your workloads are now visible and editable, and you can add your own (for example, an extra Ingress) for full transparency over what gets deployed. NodePools also gain an extended form with YAML editing, so advanced Karpenter settings no longer have to be changed directly in the cluster.
Environment Presets (beta)
Preset details now show every project at once and can create all of them, with their resources, in a few clicks instead of one project at a time. Presets exported locally also work with private repositories.
MCP Server (beta)
Connect the SleakOps MCP server to Claude Code or any MCP client and operate the platform in natural language.
Contextual support chat
Every resource now has a support button that opens the support chat directly from where you are working.

Essential addons managed from the Addons section
Essential cluster addons are now listed and managed together with the rest of the addons. Their configuration is protected from edits that could break the cluster, and it is completed automatically when they are adopted.
Clearer Build and Deployment status
Builds and Deployments now show why they are waiting (for example, queued behind another build or waiting for a resource to be ready), and pending changes are reviewed directly from the deployment detail.
Console and access improvements
Advanced settings open automatically when they differ from the defaults, addon links are available from the Dashboard and Workloads, Settings has its own sidebar, and services show all of their variable groups. In addition, the Viewer role can no longer read the secret values of variable groups.

Safer database dependency edits
Saving a database dependency no longer disables its deletion protection in AWS, Aurora clusters restored from a snapshot or point-in-time can be edited again, and the DocumentDB edit form shows the configured instance class. Restores now validate the engine version against the snapshot before creating any resources.
Reliable environment domain changes
Changing an environment's domain now provisions the new domain, re-points addons and S3 aliases, and redeploys affected projects (including static sites and workers) only after the domain is ready. Orphaned domains can be deleted without errors.
Cluster creation and deletion
New clusters install their essential addons in the correct order, and deleting a cluster no longer fails when some addons were already being removed or leaves project namespaces behind.
Workloads and activity log
Re-running a CronJob now opens the job form prefilled with its definition, service updates keep their backup replica settings, removing a file-type variable group no longer leaves pods trying to mount it, and the Dashboard activity log shows only the selected provider's activity.