Managing Environments at Scale with Fleet Plans
Read Now
As organizations scale their cloud infrastructure, managing dozens or even hundreds of environments becomes increasingly complex. Whether you are rolling out security patches, updating configuration variables, or deploying new template versions, performing these operations manually on each environment is time-consuming, error-prone, and simply unsustainable.
Fleet Plans solve this challenge—a powerful feature that eliminates the need to manage environments individually by enabling bulk operations across multiple environments in parallel.

Note: Fleet Plans currently support day 2 operations only, focusing on managing and updating existing environments rather than initial provisioning.
Modern development teams often maintain numerous environments across different stages of the software lifecycle: development, staging, QA, production, and more. Each project might have its own set of environments, each potentially based on different templates and configurations.
Consider a common scenario: Your security team mandates an urgent update to a configuration variable across all production environments. Without fleet management capabilities, an operator would need to:
This approach doesn't scale. It's slow, inconsistent, and leaves room for human error.
Fleet Plans provide an automated approach to managing environment operations at scale. Instead of touching each environment individually, you define:
The system then orchestrates the entire process, executing operations in controlled batches while providing full visibility into progress and status.

The Fleet Plan configuration flow guides you through defining operations, selecting target environments, optionally scheduling execution, and monitoring the results. This visual workflow ensures a systematic approach to managing environments at scale.
Fleet Plans support multiple operation types that cover the most common environment management tasks:

Each operation can be configured with a "Continue on Failure" option, allowing the workflow to proceed even if individual environments encounter issues.
Not every operation should apply to every environment. Fleet Plans use a multi level filtering system:
env:production, team:platform)This filtering approach ensures you're targeting exactly the right environments—no more, no less.

Fleet Plans support both one-time and recurring schedules:
Scheduling is particularly valuable for operations that need to occur during low traffic periods or as part of regular maintenance routines.
Once a Fleet Plan runs, you get full visibility into execution status:
Visual dashboards with pie charts and counters make it easy to assess the overall health of a fleet job at a glance.

Your platform team has released a new version of the base infrastructure template that includes security patches and performance improvements. With Fleet Plans:
You have discovered that a critical configuration variable has inconsistent values across your production environments. With Fleet Plans:
End of quarter is approaching and finance wants to reduce cloud spend by eliminating unused development environments. With Fleet Plans:
Ready to simplify your environment management? Here's how to create your first Fleet Plan:

For comprehensive documentation, see the Fleet Plans documentation.
Fleet Plans transform environment management from a manual, error-prone process into an automated, scalable operation. By combining flexible targeting, powerful operations, and comprehensive monitoring, Fleet Plans give platform teams the tools they need to manage environments at any scale.
Whether you're updating ten environments or ten thousand, Fleet Plans ensure consistency, visibility, and control—freeing your team to focus on innovation rather than repetitive operational tasks.
.png)

Enterprises often require explicit approvals before critical actions can proceed especially when provisioning infrastructure or making configuration changes.
Read Now