mist-ce
Mist CE is an open-source multicloud management platform that provides a unified interface for provisioning, monitoring, and orchestrating resources across 20+ cloud providers, hypervisors, and container platforms. Originally backed by a commercial vendor, the Community Edition is no longer actively maintained post-acquisition by Dell in December 2023, though it remains functional and receives occasional security contributions.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | mistio/mist-ce |
| Owner | mistio |
| Primary language | Python |
| License | Apache-2.0 — OSI-approved |
| Stars | 1.9k |
| Forks | 327 |
| Open issues | 54 |
| Latest release | v4.7.2 (2025-05-18) |
| Last updated | 2025-05-18 |
| Source | https://github.com/mistio/mist-ce |
What mist-ce is
A containerized microservices application built in Python, deployed via Kubernetes/Helm or Docker Compose, with REST/WebSocket APIs, Dramatiq workers, MongoDB/Elasticsearch/InfluxDB backends, and support for orchestration across AWS, Azure, GCP, OpenStack, vSphere, KVM, Docker, and Kubernetes. No longer receives feature development or regular maintenance.
Get the mist-ce source
Clone the repository and explore it locally.
git clone https://github.com/mistio/mist-ce.gitcd mist-ce# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Kubernetes installation requires a functional K8s cluster; Docker Compose single-host option simpler but less scalable. Both require pre-configuration of domain/TLS and MongoDB/Elasticsearch/time-series DB instances.
- Cloud credential management and SSH key centralization needed for shell and script execution; assess credential storage and rotation policies before deployment.
- Monitoring via Telegraf agents and Gocky relay; evaluate firewall/network requirements for metrics collection from remote or air-gapped infrastructure.
- Audit logging stored in Elasticsearch; plan retention and query capacity based on expected action volume and compliance requirements.
- Helm chart and Docker Compose files provided, but post-acquisition maintenance status unclear—review pinned dependency versions and test against current toolchain.
When to avoid it — and what to weigh
- Need active vendor support or feature development — Project is not actively maintained. Enterprise Edition and Hosted Service offerings ended December 2023. Only community-contributed security fixes are expected.
- Require fine-grained RBAC or governance constraints — Role-based access control, cost quotas, and governance policies were exclusive to the discontinued Enterprise Edition and are not available in CE.
- Deploying into a tightly constrained environment — Mist is microservices-heavy requiring 8 CPUs and 16GB RAM minimum on Kubernetes, plus MongoDB, RabbitMQ, Elasticsearch, and InfluxDB/VictoriaMetrics instances. Not suitable for resource-limited deployments.
- Expecting regular security patches or stable API — With minimal maintenance post-acquisition, there is no clear SLA for security vulnerability response or API stability guarantees.
License & commercial use
Mist CE is licensed under Apache License 2.0 (OSI-approved permissive license). Permits commercial use, modification, and distribution under the same terms. No patent grants or indemnification beyond standard Apache 2.0 terms.
Apache 2.0 permits commercial use without requesting permission. However, project is not actively maintained post-acquisition; no vendor support contract available. Users must accept responsibility for security patches, bug fixes, and operational support. Forking and self-maintenance may be necessary for production deployments.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Stale |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | High |
| DEV.co fit | Possible |
| Assessment confidence | Medium |
Project uses centralized SSH key management and audit logging (stored in Elasticsearch) for shell and script execution, which is a positive control for teams enforcing compliance. However, with minimal active maintenance, there is no clear security vulnerability disclosure process or patch timeline. Deployment involves multiple stateful components (MongoDB, RabbitMQ, Elasticsearch, InfluxDB) requiring individual hardening, backup, and monitoring. Assess credential storage mechanism (MongoDB encryption at rest?), network isolation, and RBAC implementation before production use. No third-party security audit or penetration test results provided.
Alternatives to consider
Terraform / OpenTofu
Infrastructure-as-code approach for provisioning and managing resources across clouds; requires scripting/coding but offers version control, testability, and strong ecosystem. Does not provide runtime monitoring or unified dashboard like Mist.
vRealize Cloud Universal (VMware/Broadcom)
Commercial multicloud management platform with active vendor support, RBAC, cost governance, and broader integration ecosystem. Higher cost and potential vendor lock-in; does not have permissive open-source option.
CloudHealth / VMware Aria Cost (Broadcom)
Focused on cloud cost optimization and governance; does not provide resource provisioning/orchestration like Mist but covers monitoring, chargeback, and RI management at enterprise scale.
Build on mist-ce with DEV.co software developers
Review the deployment architecture, test against your cloud portfolio in a non-production environment, and assess long-term maintenance strategy. Consider forking or contributing security patches if production use is planned.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
mist-ce FAQ
Is Mist CE still actively developed?
Can I use Mist CE for production workloads?
What is the minimum infrastructure footprint to run Mist CE?
Does Mist CE support Terraform or Helm templates?
Work with a software development agency
DEV.co helps companies turn open-source tools like mist-ce into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source devops stack.
Ready to evaluate Mist CE?
Review the deployment architecture, test against your cloud portfolio in a non-production environment, and assess long-term maintenance strategy. Consider forking or contributing security patches if production use is planned.