Cloud Advisory: Which cloud fits each workload

Before you build or commit, a certified cloud solution architect weighs each workload on AWS, Microsoft Azure and Google Cloud and writes down which fits.

Ask for an assessment See what you receive

What we weigh in every workload

FitDoes it run well there?

CostOver three years, not one bill

RiskOutages, lock-in, the way out

RulesWhere its data may live

PeopleWhat your team already knows

Your workloadWhat it does and holds

One recommendationIn writing, for each workload

The recommendation, on one page

Cloud recommendation

Illustration

1A fit for each workload

Workload	AWS	Azure	Google Cloud
Customer web app	Fits best
Business apps		Fits best
Analytics			Fits best

Which cloud suits it, and why.

2A cost model

Year 1

Year 2

Year 3

Three years, with the assumptions written down.

3The risks

HighOne region only
MediumKeys held by one person
LowAn old runtime version

Ranked, with an owner for each.

4An exit plan

TodayAnother cloud

How you would leave, so the choice is never a trap.

5A landing zone outline

Accounts
Network
Identity
Guardrails

Accounts, network and identity, in outline.

6A first step

Build
Move
Not yet

A build, a move or nothing at all.

Ask for this on your workloads

From first call to decision

A manager standing to explain a plan to colleagues at a meeting table

Step 1: Learn what you runWe read your workloads, data and rules in one working session.You and Cloud 23
Step 2: Weigh the cloudsEach workload on AWS, Microsoft Azure and Google Cloud, and any plan you bring, against best practice.A certified cloud solution architect
Step 3: Write it downOne report: a recommendation for each workload.Cloud 23
Step 4: Decide with usWe walk through it with your team. You choose.You

When to ask

Before a first moveChoose the cloud before you commit to it.
A plan needs a second opinionA design or a quote, checked against best practice.
Before a commitmentCheck a renewal or a spend commitment against what you run.
Clouds need one planAfter a merger, or when teams chose their own.
Data has to stay putKnow where it may live, and what that means.

How the advice stays independent

The report is yours to check, and to take to anyone.

No cloud is the defaultEach workload is weighed on fit, cost and risk.
You keep the reportWith its assumptions, for your team or another partner.
Nothing is built until you decideAn assessment is scoped and priced in writing first.
It stops at the recommendationThe detailed design and the build are separate work, quoted separately.

Questions

Can you check a plan or a quote we already have?

Yes. We read it against the best practice for that cloud, such as the AWS Well-Architected Framework, and say what to change before you spend.

How is this different from a review?

A review reads a cloud that already runs and ranks what to fix. Advisory is for what you have not built yet: the choice, the shape and the cost.

How long does it take, and what does it cost?

That depends on how many workloads there are. The scope, the time and the price are agreed in writing before we start.