Cloud Foundations
Infrastructure you can rebuild, watch and afford.
- How long3 to 8 weeks
- How we workFixed package
What you receive
Infrastructure you can rebuild, watch and afford, instead of a server someone set up by hand and nobody dares touch.
What should our setup look like?
You receiveAn architecture design
Decisions are made once, deliberately, not by accident over years.
What it is. A design for your hosting: the services, how they connect and how they grow.
Why it matters. Decisions are made once, deliberately, not by accident over years.
Could we rebuild it if we had to?
You receiveInfrastructure as code
No more "only one person knows how the server works".
What it is. Your whole setup written as code, so it can be recreated exactly in minutes.
Why it matters. No more "only one person knows how the server works".
How do changes go live?
You receiveAutomated build and release
Releases become routine, not risky late-night events.
What it is. Every change tested and released the same way, at the press of a button.
Why it matters. Releases become routine, not risky late-night events.
Will it run the same everywhere?
You receiveContainers, where they fit
Fewer "it worked on my laptop" problems, and easier scaling.
What it is. Applications packaged in containers where that suits them, so they run the same on every machine.
Why it matters. Fewer "it worked on my laptop" problems, and easier scaling.
Will we know if something breaks?
You receiveMonitoring and alerts
Problems are fixed before customers notice.
What it is. Dashboards and alerts that tell the right person when something goes wrong.
Why it matters. Problems are fixed before customers notice.
What are we paying for?
You receiveA cost report
Your bill matches what you really need.
What it is. A clear breakdown of your hosting costs and where to save.
Why it matters. Your bill matches what you really need.
Can our team run it?
You receiveA handover
You own and understand your infrastructure.
What it is. A walkthrough and written guide for your team.
Why it matters. You own and understand your infrastructure.
From brief to done
- 1
Week 1
Design
The architecture agreed.
- 2
Weeks 2 to 6
Build
Infrastructure as code, releases and monitoring.
- 3
Final week
Hand over
The cost report and handover.
What can a stranger see about our systems?
Outside-in security look. What anyone on the internet can see about your systems, and the five fixes that matter most.
- You give us written permission and the addresses to check
- We check certificates, email settings and anything exposed, from the outside only
- A short report with the fixes in order
- It is free. There is nothing to pay and nothing to sign.
- The report is yours to keep and share, whatever you decide.
- No sales call unless you ask for one.
Questions people ask
How much does it cost?
We send a written quote after your request: what it covers and what it does not. The tier, scope and timing set the price.
Could I just use AI for this?
AI drafts code and prototypes quickly, and we use it every day. It cannot decide what to build, prove that it is secure, or answer for it when real people rely on it. That is the part you are hiring us for.
Who owns the work?
You do. Code, designs, files and documents are yours, and the quote says so in writing.
Can we change the scope?
Yes. If something needs adding or removing, we agree it in writing before we do it.
What happens after?
Most people go on to Operate and Improve Plan, but there is no obligation. You keep everything we made.