|
| 1 | +# Frequently Asked Questions |
| 2 | + |
| 3 | +This section answers common questions about exitcloud.io, cloud exit readiness assessments, and how the platform works. |
| 4 | + |
| 5 | +--- |
| 6 | + |
| 7 | +## What is cloud exit readiness? |
| 8 | + |
| 9 | +Cloud exit readiness describes how prepared an organization is to **reduce, change, or fully exit** a cloud service provider. |
| 10 | + |
| 11 | +It covers: |
| 12 | +- technical dependencies |
| 13 | +- service lock-in risks |
| 14 | +- cost and operational considerations |
| 15 | +- availability of alternative technologies |
| 16 | + |
| 17 | +exitcloud.io helps assess and quantify this readiness in a structured way. |
| 18 | + |
| 19 | +--- |
| 20 | + |
| 21 | +## Who is exitcloud.io for? |
| 22 | + |
| 23 | +exitcloud.io is designed for: |
| 24 | +- small and medium-sized enterprises (SMEs) |
| 25 | +- managed service providers (MSPs) |
| 26 | +- consultants supporting cloud strategy and risk assessments |
| 27 | +- technical leaders who need visibility into exit risks |
| 28 | + |
| 29 | +--- |
| 30 | + |
| 31 | +## Which cloud providers are supported? |
| 32 | + |
| 33 | +Currently supported: |
| 34 | +- **AWS** |
| 35 | +- **Microsoft Azure** |
| 36 | + |
| 37 | +Planned / coming soon: |
| 38 | +- Google Cloud Platform (GCP) |
| 39 | +- Alibaba Cloud |
| 40 | + |
| 41 | +Support for additional providers will be added over time. |
| 42 | + |
| 43 | +--- |
| 44 | + |
| 45 | +## Does exitcloud.io require admin access to my cloud account? |
| 46 | + |
| 47 | +No. |
| 48 | + |
| 49 | +exitcloud.io requires **read-only permissions** only. |
| 50 | +These permissions are used exclusively to collect metadata such as: |
| 51 | +- resource types |
| 52 | +- counts |
| 53 | +- cost summaries |
| 54 | + |
| 55 | +No changes are made to your cloud environment. |
| 56 | + |
| 57 | +--- |
| 58 | + |
| 59 | +## How are credentials handled? |
| 60 | + |
| 61 | +- Credentials are used only during assessment execution |
| 62 | +- They are **not stored in the platform database** |
| 63 | +- They are securely handled via an **isolated secrets manager** |
| 64 | +- Full auditing and strict access controls are applied |
| 65 | + |
| 66 | +exitcloud.io never stores long-term credentials in plaintext. |
| 67 | + |
| 68 | +--- |
| 69 | + |
| 70 | +## What is the difference between Basic and Standard assessments? |
| 71 | + |
| 72 | +**Basic** includes: |
| 73 | +- Resource Inventory |
| 74 | +- Cost Overview |
| 75 | +- Risk Inventory |
| 76 | +- Executive Summary |
| 77 | + |
| 78 | +**Standard** includes everything in Basic, plus: |
| 79 | +- Exit Readiness Scoring |
| 80 | +- Detailed Exit Readiness Report |
| 81 | +- Benchmarking and trend analysis (for continuous assessments) |
| 82 | + |
| 83 | +--- |
| 84 | + |
| 85 | +## What is a continuous assessment? |
| 86 | + |
| 87 | +A continuous assessment automatically re-runs on a schedule: |
| 88 | +- daily |
| 89 | +- weekly |
| 90 | +- monthly |
| 91 | + |
| 92 | +This allows you to: |
| 93 | +- track changes over time |
| 94 | +- monitor risk evolution |
| 95 | +- measure improvement or regression in readiness |
| 96 | + |
| 97 | +--- |
| 98 | + |
| 99 | +## Can I export or download reports? |
| 100 | + |
| 101 | +Yes. |
| 102 | + |
| 103 | +Depending on the assessment package, you can download: |
| 104 | +- **Executive Summary** (Basic & Standard) |
| 105 | +- **Exit Readiness Report** (Standard only) |
| 106 | + |
| 107 | +Reports are available as PDF files via the **Download** button on the Assessment Details page. |
| 108 | + |
| 109 | +--- |
| 110 | + |
| 111 | +## Can I change my data region later? |
| 112 | + |
| 113 | +No. |
| 114 | + |
| 115 | +EU and US regions are **fully isolated**, and accounts or assessments cannot be migrated between regions. |
| 116 | + |
| 117 | +Choose your data region carefully based on legal, regulatory, and contractual requirements. |
| 118 | + |
| 119 | +--- |
| 120 | + |
| 121 | +## Is exitcloud.io vendor-neutral? |
| 122 | + |
| 123 | +Yes. |
| 124 | + |
| 125 | +exitcloud.io is: |
| 126 | +- cloud-provider agnostic |
| 127 | +- vendor-neutral |
| 128 | +- focused on outcomes, not tooling promotion |
| 129 | + |
| 130 | +Alternative technologies are presented for analysis, not endorsement. |
0 commit comments