cloudtech.engineering
IT DE Book a call
Services How we work Work Insights
IT DE
Book a call
Platform and reliability

Cloud architecture and cost

Your cloud bill grows faster than your traffic, or you are about to build on a cloud and want it right the first time. We design and review GCP and AWS setups where networking, identity, data, secrets and observability fit together. You also get an honest view of what it all costs.

What we do

Design new setups as one system. For greenfield work we design networking, identity, the data layer, secrets and observability together. Bolting them on later is where most cloud pain comes from. We work GCP first and AWS too, multi-project or multi-account, with everything in code from day one. You get the design written down, including the options we rejected and why, so the next engineer doesn’t have to guess.

Review the estate you have. We read your accounts, projects and infrastructure code and look at three things. What it costs and why. How exposed it is, from public buckets to over-broad roles. And how far one failure or one leaked credential can spread. The output is a prioritized fix list. You won’t get a slide deck.

Plan migrations with honest economics. Moving to a cloud, between clouds or off a legacy platform. We compare lift-and-shift, replatform and refactor for each part of the system, with the real cost of running and changing it afterwards. Sometimes the right plan is to move less. We also plan the order of moves, the rollback for each step, and how data gets across without a long outage.

Bring the bill under control. We map every large line item to the service that causes it. Then we fix the waste, size things to real usage, use commitment discounts where load is steady, and set up labels and budgets so the next surprise shows up in days, not at the end of the quarter.

How it usually goes

Many engagements start with the two-week cloud cost review. We read your GCP or AWS bill line by line, map it to the services behind it and find what you pay for and don’t use. You get a ranked list of savings with effort and risk for each, and you keep it whether we continue or not.

From there, some teams do the fixes themselves. Others ask us to do the first round with them, usually a few weeks, or to move on to a wider architecture review or migration plan. Either way, the changes land in your repos and accounts, and your team can explain them afterwards.

A good fit if

  • Your bill is growing faster than your users, and nobody can say why.
  • You are picking a cloud, or consolidating accounts and projects.
  • You are planning a migration and need a second opinion before you commit.
  • One bad credential or one mistyped command could take down everything.

Questions we get

How much can a cloud cost review save?
It depends on how the estate grew, and we won’t promise a number before we’ve seen the bill. Common finds are idle or oversized resources, storage nobody reads, expensive data transfer paths and missing commitment discounts. The review gives you a ranked list with effort and risk for each item, so you can decide what is worth doing.
Should we use GCP or AWS?
Both are solid for most workloads. The better choice usually comes down to what your team already knows, which managed services you depend on, and your existing contracts. We work mostly on GCP and also on AWS, and we will tell you if the choice matters less than you think.
Lift-and-shift, replatform or refactor?
Lift-and-shift is fastest but carries your old costs and problems with you. Replatforming moves to managed services such as databases and queues with limited code changes, and is often the best balance. Refactoring gives the most benefit but costs the most time, so we save it for the parts of the system where it clearly pays back.
What is FinOps?
FinOps is the practice of making cloud spend visible, assigning it to the teams and services that cause it, and making cost a normal input to engineering decisions. In practice that means labels or tags, budgets, regular reviews and someone who owns the bill. We set up the minimum that works for your size.

Related services

Tell us what's broken.

A few sentences is enough. We reply within one working day and the first call is free.

Book a call info@cloudtech.engineer