Summary
DuoCircle is winding down the hosted Commando.io service and releasing the platform as open source. You will be able to run the full application yourself, on your own infrastructure, with the same Recipe engine, audit trail, API, CLI, and iOS app you use today.
This article is the practical guide for current hosted users: what is changing, when, and the steps to move your data. For the reasoning behind the decision, read our announcement post: We Are Open-Sourcing Commando.io: Server Automation Meets the LLM Era.
Timeline
| Milestone | When | What happens |
|---|---|---|
| Wind-down notice period | Now through July 31, 2026 | Your hosted account stays fully functional. Export your Recipes, files, and server configuration during this window. |
| Hosted service end date | July 31, 2026 | The hosted Commando.io service stops accepting new executions and is retired. |
| Open-source release | Mid-August 2026 | The Commando.io code is published to a public repository under an open-source license, and self-hosting becomes the path forward. |
Please note the gap between the two dates. The hosted service is retired on July 31, 2026, and the open-source code lands in mid-August 2026. Export your data before July 31 so you have everything you need on hand. If you rely on Commando.io for time-sensitive automations and need continuity across that window, contact our team and we will help you plan for it.
What you should do before July 31, 2026
- Export your Recipes. Your Recipes are versioned command containers. Copy each Recipe's current source out of the web editor and into your own version control. If you have a large library, the API can pull them programmatically.
- Export your files. Anything stored in centralized file storage for SCP distribution should be downloaded and kept with the Recipes that use it.
- Record your server inventory. Export or note your server groups, tags, and connection details so you can recreate them in your self-hosted instance. Do not export private keys into anything insecure.
- Note your integrations. Write down any GitHub triggers, webhook sources (for example a monitoring service that fires a webhook into a Recipe), API clients, and CLI usage so you can re-point them at your own instance.
- Save your audit history if you need it for compliance. Pull the execution history you are required to retain before the hosted service is retired.
How to self-host
Once the code is published in mid-August 2026, you will be able to stand up your own Commando.io instance and import the Recipes, files, and server configuration you exported above.
A few things to know going in:
- The stack uses an older version of PHP that benefits from an upgrade. Modernizing it is a great first contribution, and we expect the community to move quickly here.
- You control the keys. Self-hosting means your SSH credentials and audit trail stay entirely on infrastructure you own.
- The webhook-to-Recipe pattern travels with you. If you wired a monitoring alert into a runbook Recipe on the hosted service, you can recreate it on your own instance and point the webhook at your domain.
The repository link will be added here as soon as the code is public.
Frequently asked questions
Is Commando.io being shut down?
The hosted service is being wound down on July 31, 2026. The product is not going away. It is being released as open source in mid-August 2026 so you can run it yourself.
Why is DuoCircle doing this?
DuoCircle acquired Commando.io for its automation and server-management engine, and we still use it internally as a tier-one triage tool. We believe the webhook-driven Recipe engine is more valuable in the open, especially paired with an LLM to turn static runbooks into adaptive ones.
Will I lose my Recipes and data?
Not if you export before July 31, 2026. Follow the steps above.
Does the iOS app still work after the wind-down?
The app talks to a Commando.io instance. Once you self-host, you point it at your own instance.
Can I pay DuoCircle to keep running it for me?
The hosted service is being retired. If you need help migrating or operating a self-hosted instance, contact our team and we will point you in the right direction.
Need a hand
If you have questions about exporting your data or standing up a self-hosted instance, reach out through our contact page and we will help you plan the move.