Cloud Infrastructure
Servers and cloud accounts set up so they can be rebuilt, not just restarted.
The problem
The server was configured by hand, by someone who has left, and nobody is willing to touch it.
What we do
We set up infrastructure that is documented and reproducible: what is running, why, and how to rebuild it. Backups are configured and then tested by restoring from them, because a backup nobody has restored is a hypothesis.
Everything ends up in your Technology Passport with its provider, environment and renewal date.
Who this is for
Organizations running their own applications, or planning to.
What you receive
- Configured infrastructure with documentation
- Backup configuration, with a restore actually performed and recorded
- Monitoring and alerting
- Access control and credential handover
How it works
Consultation
What runs, and what it needs.
Assessment
Current state and target state.
Proposal
Scope, cost and running cost.
Implementation
Build, migrate, test.
Delivery
Documentation and handover.
Support
Ongoing administration, if wanted.
What we need from you
- Administrative access to the hosting or cloud account, or authority to create one
- Agreement on who holds the root credentials afterwards
These become your onboarding checklist — generated from the services you choose, so you are not asked for anything this work does not need.
Questions
Do you test the backups?
Yes — we restore from them before handover and record the result. A backup that has never been restored is an assumption, not a control.