This is the GitHub organisation for EscapeCloud, building open tooling and platforms for Cloud Exit Readiness — helping individuals, teams, and enterprises assess how prepared they are to move off a cloud provider, reduce vendor lock-in, and stay in control of their data, costs, and compliance.
Cloud Exit Readiness, from a single offline assessment to enterprise-wide governance:
| Edition | Best for | What it adds | |
|---|---|---|---|
| 🧩 | cloudexit — Community / Open Source | Developers, self-hosters | Offline-first assessment engine. Free and open source. |
| 💻 | exitcloud.io — Lightweight Platform | Individuals, SMEs, MSPs | Hosted reports, scoring, and tracking over time. |
| 🏢 | escapecloud.io — Enterprise Platform | Larger organisations | Advanced reporting, governance, and team workflows. |
cloudexit is the Community / Open Source edition of the EscapeCloud ecosystem — an offline-first assessment engine you can run yourself.
It can be used:
- Fully offline for a Basic assessment, with no account or connection required,
- Connected to a platform (exitcloud.io / escapecloud.io) for richer reports and scoring, or
- Automated in your CI/CD pipeline with cloudexit-actions, running exit-readiness assessments on every push or pull request.
Start in the open-source CLI, then connect to a platform when you need shareable reports, historical scoring, or governance.
Our public repositories include:
- cloudexit — the open-source, offline-first assessment engine
- cloudexit-actions — GitHub Actions for cloudexit
- cloudexit (open source): open an issue in the relevant repository for bugs, ideas, or usage questions.
- exitcloud.io / escapecloud.io accounts and resources: for anything specific to your account, subscription, or hosted assessments, please contact platform support rather than opening a public issue.
GitHub Action that wraps the cloudexit