Cloud Lab.Infrastructure designed to stay up when nobody is watching.
We migrate, automate and operate cloud infrastructure, with service level objectives, error budgets and rehearsed recovery. Releases become routine, and when something fails the alert reaches a person who knows the system.
Build · Run · 24/7
01What we build
What the Cloud Lab builds.
Archetypes, named by what they do. Every engagement also carries the standards we apply in every lab.
- 01
Cloud migrations
Moves off ageing servers and single boxes onto containers and managed services, with a rehearsed cutover and a warm rollback.
- 02
Infrastructure as code
Every environment defined in Terraform or an equivalent and reviewed like application code.
- 03
CI/CD pipelines
Build, test and deploy on every change, with preview environments and one-step rollback.
- 04
Container platforms
Kubernetes or simpler container hosting sized to the workload, with policies enforced as code.
- 05
Observability stacks
Logs, metrics, traces and error tracking wired to alerts that mean something.
- 06
Managed hosting and 24/7 operation
Patching, backups, monitoring and incident response under a service level agreement.
02Services
Services and deliverables.
Concrete scopes with named outputs, so you know what you will hold at the end of each stage.
Migration
Assessment, plan and cutover for applications and data, with the old environment kept warm until sign-off.
- Migration assessment
- Cutover runbook
- Rollback plan
Platform engineering
Infrastructure as code, pipelines and environments your developers can use without raising a ticket.
- Terraform modules
- CI/CD pipelines
- Developer documentation
Site reliability
Service level objectives, error budgets, alert routing and postmortems.
- SLO definitions
- Alert routing
- Postmortem process
Managed operations
Hosting, patching, backups, monitoring and on-call as a retained service.
- Service level agreement
- Monthly reliability report
- DR drill schedule
03Live tool: Cloud cost estimator
Estimate the bill.
Describe the workload and compare indicative monthly costs. Prices are list-price assumptions shown in full, not a quote from any provider.
04Lab standard
The A* standard for this lab.
On top of fixed-price discovery, a named lead, code you own, test gates, observability, written decisions and an SLA-backed run retainer, this lab adds:
- 01
SLOs and error budgets
Reliability targets are agreed per service, and the error budget decides when to ship features and when to fix.
- 02
Disaster recovery drills
Backups are restored and failovers rehearsed on a schedule, so recovery time is measured rather than hoped for.
- 03
Cost dashboards
Spend is visible by service and environment, with alerts and a monthly review of waste.
- 04
Policy as code
Security and configuration rules are enforced automatically on every infrastructure change.
- 05
Blameless postmortems
Every significant incident gets a written review and tracked actions.
05Human sign-off
Where people sign off.
Agents can plan infrastructure changes but cannot apply them on their own: Terraform apply is disabled by default for automated tooling, and hooks block destructive commands.
- Production change approvalEvery production infrastructure change is approved by a named engineer after the plan has been reviewed.
- On-callA person carries the pager. Automation triages and gathers context so that person can decide quickly.
- Incident commandDuring an incident one named person leads, communicates and makes the calls.
06FAQ
Questions, answered.
Which cloud providers do you work with?
AWS, Google Cloud, Azure, Cloudflare, Vercel and Supabase, plus VPS hosting where it is the sensible choice. We recommend by workload and team, not by partner incentives.
Do you provide 24/7 support?
Yes, through the run retainer. Response times are written into the SLA, and alerts route to engineers who know your system.
Can you reduce our cloud bill?
Often, yes. We start with a cost breakdown by service and environment, then rightsize, schedule and re-architect where the savings justify the work.
Will we be locked in to you?
No. Infrastructure is defined in code, in your own accounts, documented and runnable by any competent team.
08Contact
Tell us what must stay up.
Your first call is with an engineer from the Cloud Lab, not a sales script. Bring the system, the deadline and the constraints.
hello@aurionlabs.io