Frequently asked questions
These are the questions we’re asked most often — by technical teams, leadership, and risk owners alike.
Is RefugeX anti-cloud?
No.
The cloud remains useful for many workloads. RefugeX exists to prevent dependency without consent — not to reject the cloud outright.
Is self-hosting inherently riskier?
Poorly designed self-hosting is risky. Deliberate, well-understood infrastructure with clear ownership is not.
Risk doesn’t disappear in the cloud — it just becomes harder to see.
Will this disrupt our existing systems?
RefugeX does not perform “big bang” migrations.
Systems are assessed, planned, and moved incrementally, often running in parallel until confidence is established.
Do we need to leave the cloud entirely?
No.
Many organisations adopt a hybrid or selective approach. The goal is optionality, not purity.
Is this only for large organisations?
No.
Smaller organisations often feel cloud pressure earlier — particularly around cost predictability and dependency.
What about compliance and regulation?
RefugeX does not provide legal advice.
We design infrastructure that is easier to explain, audit, and control — which supports compliance rather than complicating it.
How long does an engagement last?
Long enough to leave you confident — and no longer.
RefugeX is intentionally structured to step away once systems are stable, documented, and understood.
What happens after the migration?
You own the outcome.
RefugeX provides documentation, runbooks, and handover support, so you are not dependent on us going forward.
Still have questions?
A short, neutral conversation is often the fastest way to get clarity.
Start a conversation