Infrastructure as code
Servers, networks and storage described in files, so they can be rebuilt.
infra/Service / Cloud and storage
We set up servers, cloud accounts and storage, then monitor, patch and back them up under written terms.
01 / What you get
Servers, networks and storage described in files, so they can be rebuilt.
infra/Cloud, domain and storage accounts your company owns, with our access granted.
owner: youUptime, disk, certificates and errors watched; alerts reach us and you.
alertsEncrypted copies off-site, and a restore test you can watch.
restore-test.logSecurity updates on a schedule, the previous state kept for rollback.
CHANGELOG.mdHow the system starts, stops, recovers and passes to another team.
RUNBOOK.md02 / How it runs
Review
what runs today
Plan
sizing, region, cost
Build
as code, on staging
Move
with a rollback
Operate
monitor, patch, report
03 / Example
Illustrative. Changes and times are invented.
Example · invented data
04 / What to send us
06 / FAQ
The one that fits the system and your rules: a large public cloud, a European host or your own servers. The choice and the reasons are written into the plan.
Your company. Accounts and billing are in your name, and we work through access you grant and can revoke.
We agree in writing what is monitored and how fast we respond. Availability also depends on the provider, so we do not promise a figure we do not control.
Yes. The region for the data and for its backups is agreed in the plan and recorded.
Your systems, where they run, and what worries you.