A simpler way to deploy updates to many customer VMs
Software sold into customer-controlled environments can become hard to update once each customer has a separate or setup. The problem grows when updates must reach 10, 20, or 50 separate environments. Tools like Ansible, Salt, k3s, and ArgoCD can handle this, but small teams may not want to spend time learning and maintaining tooling instead of building product features.
The product idea is a simple dashboard where each customer environment is registered with an SSH key and overrides. A deploy button would show live success or failure for each customer, allow one-click rollback, and show which customer is on which version. The aim is to cover the common case without YAML files, playbooks, or a cluster to maintain.
The open question is whether $30 to $50 per month feels reasonable for teams with this pain.
Key points
- Separate customer make updates harder as customer count grows.
- Existing tools like Ansible, k3s, and ArgoCD solve the problem but can be heavy for small teams.
- The proposed tool uses an SSH key and instead of complex setup files.
- The main features are deploy status, rollback, and customer-by-customer version tracking.
- The price question is whether $30 to $50 per month matches the value of avoiding this work.