Cloud, DevOps & support
Software is not finished when it launches; that is when it starts costing money. We set up the infrastructure, automate the releases, watch the system and keep a support line open with a response time written into the contract.
B-05.1 — What we deliver
Deployment, monitoring and a line that answers
- 01Cloud setup on AWS, Google Cloud, Azure or a plain VPS
- 02CI/CD pipelines that deploy without hand-holding
- 03Monitoring, alerting and on-call that we answer
- 04Backups restored on a schedule, not just taken
- 05Security hardening, patching and access reviews
- 06Support with an agreed response time
B-05.2 — How we work
Four steps, no surprises
- 01Take stockWhat is running, where, who can reach it, and what happens if it stops.
- 02Automate the releaseOne command from merge to production, with a rollback that has been practised.
- 03Instrument everythingLogs, metrics and alerts tuned so that an alert means something is actually wrong.
- 04Run itPatching, restores, capacity and a report you can take to your board each month.
B-05.4 — Questions
What people ask first
Yes, after an audit. We need to know what we are agreeing to keep alive before we promise a response time.
A monthly retainer sized to the response time you need. Office hours is cheaper than round the clock, and most businesses only need one of them.
No. Everything runs in your own cloud accounts, under your billing. If you leave, nothing has to move.