Consistency you do not have to enforce by hand
A new cluster arrives fully equipped
You need a new production cluster. Give it the right labels and it receives every application it needs, the same way every other cluster in the fleet did.
Drift recovers on its own
On day 2, someone changes a resource by hand or deletes one by mistake. Sveltos detects the drift and restores the declared state, so a quick fix does not turn into a permanent difference between clusters.
One change reaches every cluster
One management cluster is the single place where you define what runs. Change something there once and Sveltos propagates it to every cluster that needs it.
What changes for your team
| Situation | Without Sveltos | With Sveltos |
|---|---|---|
| Adding a cluster | Follow a checklist or run scripts, and hope nothing was missed. | Apply the right labels. The cluster gets what it needs. |
| Changing a shared component | Repeat the change on each cluster, one at a time. | Change it once. Sveltos rolls it out to every matching cluster. |
| Someone edits a cluster by hand | The cluster quietly diverges until something breaks. | The drift is detected and the declared state is restored. |
| Rolling out a risky change | Push to everything and watch. | Promote through QA, staging, and production with health checks between stages. |
Free to start, priced by fleet size
The core of Sveltos is open source and free forever. Enterprise adds priority support, priority security patches, and the advanced features, and is licensed per year by the number of managed clusters. The management cluster is not counted.
See the full plan comparisonQuestions your team will ask
Does it replace Argo CD or Flux?
No. Sveltos extends GitOps tools. Argo CD and Flux are strong at managing a single cluster, and Sveltos distributes that configuration across the whole fleet.
What if we stop paying?
The Enterprise features stop working. Every open-source feature keeps running, so your fleet stays managed and the core is never locked away.
Can we try it first?
Yes. The core is open source, Pull Mode and Progressive Rollouts can be tried within the free limits, and you can ask us for an Enterprise trial.
How do we find out when something needs attention?
Define your own rules for what matters to you, and Sveltos notifies you in Slack, Teams, or wherever you already watch alerts if it ever happens in any of your clusters. This applies to whatever you tell it to watch, not just drift.
Can we isolate teams or customers on the same fleet?
Yes. ClusterProfile applies global policy across the fleet, and Profile scopes configuration to a single namespace, so separate teams or customers can share the same clusters without seeing each other’s configuration.
Can this reach clusters we can’t open a firewall for?
Yes, with Pull Mode. Instead of the management cluster pushing to a target, a lightweight agent on the managed cluster polls the management cluster over an outbound connection, which works behind firewalls, at the edge, or in air-gapped environments.
Who else uses it?
Renault, Comcast, RTL, Mistral AI, and others. See the adopters page for how each of them uses Sveltos.
View adoptersHow do you handle security issues?
There is a published disclosure process, and Enterprise customers receive patched images ahead of the next release.
Read the security policyA low-risk way to evaluate
Install the open-source version
Register a few clusters and deploy one add-on to them by label.
Try it on a real workload
Add drift detection, ordering, or a progressive rollout and see how it behaves.
Talk to us when you are ready
We will size a license for your fleet or set up an Enterprise trial.