What we actually cover

What this covers

We take operational responsibility for your cloud environment — VMs, containers, databases, networking, storage. That means patching OS and runtime versions, configuring auto-scaling, managing backups, and responding to any infrastructure-level incident that arises.

We don't just monitor and alert: we monitor, respond, and resolve. The difference matters at 3am on a Sunday.

Typically included in an engagement

• Initial environment audit and hardening recommendations
• Ongoing OS and runtime patching (scheduled, tested)
• 24/7 infrastructure monitoring with human response
• Automated and verified backup configuration
• Auto-scaling rules configured to your traffic patterns
• Monthly status report with cost, uptime, and incident summary

What this covers

Migration projects start with a discovery phase — a detailed inventory of what you have, what it depends on, and what order things need to move. That sounds obvious, but most migration problems come from assumptions made at the start that nobody wrote down.

We handle the technical execution: architecture design on the target environment, data migration, cutover planning, and rollback procedures. We test before we switch. And we stay on after the move — the managed service engagement begins immediately so there's no gap between "moved" and "supported."

• Workload discovery and dependency mapping
• Target architecture design (reviewed with your team)
• Phased migration plan with defined rollback points
• Data migration with integrity verification
• DNS cutover and traffic validation
• Handover into ongoing managed service

What this covers

We design and implement the deployment pipeline from code commit to production. The exact tools depend on your stack and cloud provider — typically GitHub Actions or GitLab CI for pipelines, Terraform or Pulumi for infrastructure-as-code, and whatever container orchestration the workload actually needs.

The goal is a deployment process your developers run themselves, with confidence. Not a system that requires us to be present for every release.

• CI/CD pipeline design and implementation
• Infrastructure-as-code (Terraform, Pulumi, or CloudFormation)
• Environment parity: dev, staging, production
• Secrets management setup
• Container build and registry configuration
• Runbook documentation (human-readable, not just comments in code)

What this covers

We start with read-only access to your cloud billing and compute inventory. The audit typically takes five to seven working days. We look at idle and over-provisioned resources, unattached storage volumes, data transfer patterns, and commitment coverage — reserved instances and savings plans against actual usage.

The output is a prioritised list of changes with estimated monthly savings for each. We categorise them by effort and risk so you can decide what to implement yourself and what you'd like us to handle.

• Full inventory of billed resources vs active usage
• Right-sizing analysis for compute and database tiers
• Reserved instance and savings plan coverage review
• Data transfer and egress cost breakdown
• Storage lifecycle policy review
• Prioritised recommendation report with effort estimates

What this covers

We configure monitoring across the stack — infrastructure metrics, application health checks, error rates, and database performance. Alerting thresholds are set based on baseline analysis of your workload, not arbitrary numbers we pulled from documentation.

Alerts route to a human who can act on them, not a ticket queue with a 24-hour first response SLA. We distinguish between "something to look at on Monday" and "this needs attention now," and handle both accordingly.

• Baseline performance analysis for your workload
• Multi-layer monitoring: infrastructure, application, external
• Alert routing with severity classification
• On-call coverage with human response
• Monthly performance summary with trend analysis
• Anomaly detection configuration

What this covers

Security work is integrated into everything we do — we don't build environments and then audit them. IAM policies follow least-privilege principles from day one. Network security groups are reviewed before resources go live. Secrets are stored properly. Backups are encrypted and tested.

For clients working toward certifications (Cyber Essentials, ISO 27001), we can provide documentation of the controls in place and support the audit process. We don't certify anything ourselves, but we work with the certifying bodies and know what they look for.

• IAM and access control review (least-privilege)
• Network security group and firewall configuration
• Encryption at rest and in transit
• Secrets management (Vault, AWS Secrets Manager, Azure Key Vault)
• Backup encryption and restoration testing
• Access audit logs and retention policy