Services
Azure, AWS and platform work
Most clients come to us for one of these. Open any of them to see the deliverables you can expect.
Azure cloud engineering
Design, build and run Azure environments for teams that need an experienced cloud engineer but not a full-time hire.
- Landing zones, hub-and-spoke networking and Entra ID identity design
- Migrations to Azure, from lift-and-shift VMs to PaaS rebuilds
- Cost reviews: right-sizing, reservations and savings plans, tagging and policy cleanup
- Production operations, incident response and on-call cover
Typical deliverables
Examples. The actual list is agreed with you at kickoff.
- Landing zone or solution architecture, written up as decision records and diagrams
- Terraform in your repository, with remote state and CI set up
- A migration runbook with pre-flight checks, cutover, rollback and post-cutover checks, if you're migrating
- A cost assessment covering tagged usage, right-sizing and reservation options, if cost is in scope
- Runbooks for the incidents your team is most likely to hit
- Pairing and code review with your team during the build
- A handover session and an agreed window for follow-up questions
AWS, with 010 Consulting
The same kind of work on AWS, delivered with 010 Consulting. We run the engagement and stay your contact. Their engineers do the AWS-specific work.
- AWS architecture, migration and ongoing operations
- One engagement lead from Cloudwalker IT, with 010's AWS engineers on the build
- IaC, GitOps and observability set up the same way on Azure and AWS
- Sized for small and mid-sized companies
Typical deliverables
Examples. The actual list is agreed with you at kickoff.
- A joint engagement plan agreed by both firms at kickoff
- AWS architecture and implementation led by 010, with cross-cloud decisions made together
- Terraform or CDK, your choice, in your repository
- CI/CD, observability and IAM that match what you run on Azure
- One point of contact at Cloudwalker IT for the whole engagement
- Pairing between both firms' engineers and your team during the build
- A joint handover, so your team can run it without either firm
Platform engineering and Terraform
Pipelines, modules and clusters that let your developers ship without filing an infrastructure ticket every time.
- Managed Terraform: pipelines, modules, state, drift detection and remediation
- Kubernetes on AKS, EKS and on-prem clusters
- CI/CD in GitHub Actions and Azure DevOps Pipelines
- Policy as code with OPA or Sentinel, and self-service for developers
Typical deliverables
Examples. The actual list is agreed with you at kickoff.
- A Terraform module library for your environment: AKS or EKS, networking, IAM and shared patterns
- Plan and apply pipelines with policy checks and required approvals
- Remote state with locking, backups and a written recovery procedure
- Scheduled drift detection and a procedure for fixing drift
- OPA or Sentinel policies covering your compliance scope
- Walkthroughs and pairing while your team adopts the platform
- Documentation developers can use without asking us
In every engagement
Whichever service you use, you get these.
- Documentation written for your team to use
- Infrastructure code and configuration in your repositories from day one
- Knowledge transfer while the work happens
- A handover that leaves your team able to run it without us
- A written summary of what we decided, what we deferred and what we'd do next
- An agreed window for follow-up questions afterwards
Not sure which one you need?
Describe the problem on a call and we'll work out which of these it is.
Book a 30-minute intro callPrefer to write first? Use the contact form