We’re excited to launch the public beta of MultiTool, a progressive delivery tool that helps teams catch production bugs before they impact users.
Every team knows the pressure of a crucial production release. The code is merged, tests pass, staging checks out. But live traffic is the real test. Engineers scan metrics, wait for alerts, and hope nothing slipped through. We built MultiTool to give teams a proactive way to safeguard their user experience. It detects regressions as they emerge and automatically rolls back unstable changes.
Most teams today face a familiar tradeoff: ship fast and monitor later, or slow down and manually babysit releases. MultiTool gives you a third option: agentic deployments, canary rollouts that are automatically monitored, evaluated, and promoted in real time.
Instead of waiting for alerts to fire or dashboards to show spikes, MultiTool watches each deployment as it happens. It promotes stable rollouts and rolls back risky ones — automatically.
Say you push a change to your billing API. MultiTool shifts 10% of traffic to the new version. Within minutes, 500 errors spike. The deployment is automatically rolled back. No paging, no guesswork, no impact to the other 90% of users.
MultiTool consists of two parts:
You define your application once in the MultiTool app. Then, with a single CLI command, multi run, it deploys a new version. MultiTool automatically analyzes service behavior, tracks metrics over time, and decides whether to promote, pause, or revert.
We started building MultiTool with a simple conviction: that engineering teams shouldn't have to choose between moving fast and staying safe. Progressive delivery, when done well, makes it possible to release confidently without compromising user experience or developer velocity. This approach has been widely adopted by industry leaders. For instance, Google employs progressive delivery strategies to gradually roll out new features and ensure reliability before a full release . This practice underscores the growing importance of progressive delivery in modern development workflows.
After several months of focused development and internal testing, we’re sharing MultiTool with a wider audience. We’re excited to see real teams use the platform. Your feedback at this stage will play a critical role in shaping what comes next!
The MultiTool beta supports:
Anyone can sign up for free. See Pricing for more plan details.
We’re still early with an ever expanding list of features we want to build for the future. Here's what’s on the horizon:
If there’s something you need, let us know! We want MultiTool to work for real teams solving real deployment problems.
If you’re giving MultiTool a try, you're among the first to use it in the wild. Your feedback is invaluable to us, and we want to know what’s working, what’s confusing, and what’s missing for you. You can submit bug reports and feature requests on GitHub. And if you need to get in touch with us directly, we’re always available at support@multitool.run.
We’re building MultiTool to make safe deployments feel easy. Thanks for being here at the start! Check out our other blog posts for information on agentic deployment, canary deployment, canary releases and blue-green deployment.
— The MultiTool team
