Cloud and Serverless

Moving workloads to cloud infrastructure, and reducing a cloud bill that has grown faster than the business using it.

Cloud decisions are usually made once and then inherited. The environment grows, the bill grows with it, and the reasoning behind the original setup is no longer available to anyone. The useful first step is rarely a migration — it is finding out what you are currently paying for.

Who it is for

Companies whose cloud bill has grown faster than their usage.
Teams running servers they would rather not keep patching themselves.
Founders who inherited an environment nobody fully understands.
Businesses whose hosting was set up once, years ago, and never revisited.

Typical situations

The bill went up and nobody can say exactly why

Cloud spend rises steadily without a matching rise in customers or traffic. The invoice is itemised but not explicable, and the people who created the resources have moved on.

Hardware is due for replacement

Servers reach the end of their warranty and the choice is to buy more hardware or stop owning hardware. That decision is easier with real numbers on both sides.

Resources exist that nobody owns

Test environments, old snapshots, detached volumes and oversized instances accumulate. Each one looked small when it was created.

One machine does everything

A single server runs the application, the database and the backups. It has worked for years, which is precisely the problem when it stops.

What we deliver

A breakdown of current spend by resource, with the things nothing is using identified.
A sizing review comparing what is provisioned against what is actually consumed.
A written migration plan, including what should not be moved and why.
Infrastructure defined as code, so the environment can be rebuilt rather than remembered.
Backup and restore configured, with a restore actually tested rather than assumed.
Handover documentation and a cost baseline to measure against later.

Typical timeline

A fixed-price assessment usually takes one to two weeks once read-only access is granted. Implementation duration is set out in the assessment report and depends on scope and change windows.

Starts with a fixed-price assessment

Read-only access first, so nothing changes while we look. You get a written finding, a recommendation and a price before any work is agreed. If the finding is that you should do nothing yet, that is what it will say.

Book a fixed-price assessment

Common questions

Will moving to the cloud reduce our costs?

Sometimes, and sometimes not. A workload that runs constantly at a steady size can be cheaper on your own hardware. The assessment produces a comparison with your real usage, and the answer is occasionally to stay where you are.

Do we have to commit to one cloud provider?

No, and it is worth deciding deliberately rather than by default. Avoiding provider-specific services keeps a move possible later, but costs some convenience. Whichever way you choose, the trade-off is written down.

What does serverless actually change for us?

It removes the servers you patch and the capacity you size in advance, and replaces them with per-request billing. It suits uneven or spiky workloads. For something running steadily all day it is usually the more expensive option.

Can you reduce the bill without migrating anything?

Often, yes. Unused resources, oversized instances and forgotten environments are common, and removing them changes nothing about how the system works. That is usually the first thing examined.

Who holds the cloud account?

You do. The account, the billing relationship and the credentials stay yours. Access is granted to us and can be revoked at any point, including after the engagement ends.

Nothing published on Cloud and Serverless yet. Advisories and articles tagged for this service will appear here as they are written.