04.01
Cloud setup and migration
New environments, or moving what you have onto something you can reason about.
Index What we do S/04
Infrastructure that stops being a topic of conversation.
S/04 / Scope
What this covers.
04.02
CI/CD pipelines
Tested, reviewed, and deployed on a push — not on an evening when everyone is available.
04.03
Infrastructure as code
Environments defined in a repository, so they can be rebuilt, reviewed, and rolled back.
04.04
Monitoring and alerting
Alerts tuned to mean something, so nobody learns to ignore them.
04.05
Backups and recovery
Backups that have actually been restored at least once, because an untested backup isn't one.
04.06
Cost and security baseline
What you're spending and why, plus access, secrets, and the basics done properly.
Signals
Where this usually starts.
01
Deploys are manual, and only one person is comfortable doing them.
02
Nobody is quite sure what's running, where, or what it costs each month.
03
You found out about downtime from a customer rather than a system.
04
Access and credentials live in one person's head or one person's laptop.
05
Your cloud bill grew steadily and nobody can point to why.
Deliverables
What you get.
Documented environments
What exists, what it does, and how to rebuild it.
Automated deployment
A pipeline your team can run without ceremony, with a way back if something's wrong.
Alerts worth reacting to
Tuned to real failure conditions rather than noise.
A tested restore
We restore from backup once, in front of you, so you know it works.
A cost baseline and a runbook
What you spend now, and what to do at three in the morning.
Every engagement follows the same four stages — understand, design, build, improve. Scope and price are agreed before anything is built.
How we workQuestions
Asked often enough to answer here.
Which cloud provider?
Whichever you're already on, in most cases — migrating providers is rarely worth it on its own. For new environments we recommend based on what you're running, where your data has to live, and what your team can maintain.
Can you work with our existing setup?
Yes. Most of this work is improving something already running rather than starting clean. We begin with a review of what's there, and prioritise by risk — what would hurt most if it failed tomorrow.
Do you provide on-call support?
We can, under a retainer with an agreed response window. We'd rather first reduce the number of things that can page anyone, and be clear about what we can realistically commit to as a two-person studio.
How do you handle access and secrets?
Secrets go into a managed secret store, never into a repository or a shared document. Access is granted per person and per environment, and removed when an engagement ends. We work to your policy where you have one, and set up a workable baseline where you don't.
Have a project in mind?
Tell us what you're working on and what you need help with. We answer every message ourselves, usually within two business days.