Cloud architecture & advisory
You're about to commit to a setup, or an existing one is slow, costly, or fragile and nobody can say why. That's the part of the work where you hire a senior pair of hands, not a finished feature. Klura designs and builds serverless cloud architecture, reviews what you already run and says plainly what holds and what doesn't, or takes a stalled decision off your team's plate.
When you need this
Most small products don't need a cloud architect. Ship a straightforward app or site and the right architecture is the boring managed one, set up correctly during the build with no separate advisory phase. You need this work when the stakes or complexity are real:
- You're about to commit to a setup or cloud provider and a wrong call is expensive to undo.
- An existing system is slow, fragile, or surprisingly costly to run and nobody can say why.
- You're outgrowing a no-code or template setup and need to plan the move to something you own.
- Your team is strong but missing one area (serverless, cloud and scaling) and needs a senior to design it or sanity-check the plan.
- Hosting or database bills are climbing faster than usage.
If none of those fit, we'll say so. We'd rather tell you the architecture you have is fine than invent a problem.
How we work
Three phases, each with a clear output. You can stop after any one, and many engagements are just the first.
- Review. We read what exists: the code, the cloud setup, the database, the bills. You get a written assessment of what's solid, what's a real risk, what's a false alarm, and a prioritised list of changes with rough effort and cost against each. It stands alone, and plenty of teams act on it themselves.
- Build or migrate. If you want it done rather than documented, we design the target architecture and build it: a new serverless setup, a migration off something you've outgrown, a faster layer in front of a slow app. We move in reviewable steps against the priority list, so the system keeps working while it changes.
- Handover. The work is finished when your team can run it without us: a documented, version-controlled setup, a deployment anyone can trigger, the reasoning behind each decision, and a walkthrough. Nothing is locked to us.
What you get
Scope depends on which phases you take. Usually some combination of:
- A written architecture assessment: strengths, real risks, and a prioritised, costed list of changes.
- A target design: hosting, database, scaling and deployment chosen for your needs and budget, not the trendiest option.
- Implementation built in reviewable steps, with the system staying live throughout.
- A version-controlled, reproducible setup, so deploys aren't a leap of faith.
- Cost and performance work: removing the lines on your bill or speed budget that don't earn their place.
- A senior second opinion on a tooling choice, a vendor, a scaling plan, or a design your team has drafted.
- Documentation and handover, so your team owns the result.
How we build
Our default is modern and serverless: it runs in the cloud, scales up under load and down to almost nothing when idle, sits on a managed database, and keeps running costs low at small scale. The whole setup is version-controlled and reproducible, so there are no undocumented dashboard clicks nobody can repeat, and the result is yours to own and run without us. It's a strong default for most products, not the answer to everything. A heavy data-processing job or a system tied to one provider's services may belong elsewhere, and we'll say so.
What it costs
Advisory is priced by scope, not by deliverable, because the value is senior judgement. Three shapes:
| Engagement | Shape | Indicative cost (kr, 2026) |
|---|---|---|
| Architecture review | A focused read of your system with a written, prioritised assessment | Scoped to the system size, agreed on a first call |
| Advisory | Senior time for reviews, tooling decisions, planning or pairing | Scoped per engagement, agreed up front |
| Build or migration | Hands-on implementation, scoped after the review | Fixed proposal once scope is clear |
No account manager, no sales layer, no junior billed as senior, no agency overhead, and you talk to the person who does the work. We don't publish a fixed price list because a real number depends on your system. For the numbers behind a full app build, see our cost guide. For cloud and advisory, we'll give you a range on a first call and a fixed proposal once scope is clear.
FAQ
Do I need a cloud architect?
Often no, and we'll tell you. Most small products are best served by a managed serverless setup configured correctly during the build, with no separate advisory phase. You need dedicated architecture or advisory work when the stakes or complexity are real: a setup you're about to commit to, a system that's slow or expensive for reasons nobody can pin down, a migration off something you've outgrown, or a gap in one area like serverless or scaling. If your current architecture is fine, we'd rather say so than invent a problem.
What does 'serverless' mean, and why does Klura use it?
Your code runs in the cloud and scales automatically with no servers to manage, paired with a managed database. For most modern products it's fast, cheap at small scale, and low-maintenance. We use it because it's a strong default for the kind of products we build. The tradeoff is a more constrained setup, and we'll tell you when a different approach fits better.
Can Klura just review our architecture without building anything?
Yes, the review stands on its own and it's a common engagement. We read your code, cloud setup, database and bills, then deliver a written, prioritised assessment of what's solid, what's a genuine risk, and what to change, with rough effort and cost against each item. Plenty of teams take that and act on it themselves. If you later want it implemented, we can do that too, with no obligation to continue.
Wondering whether your cloud setup is right, or which way to jump on a tooling decision? Tell us roughly what you're running or planning and we'll give you a straight read. Email hej@klura.app.