Home/Services
Six practices. One accountable team.
Take the whole managed service or start with a single engagement. Either way, the engineers who design it are the ones who run it at 3am.
Managed AWS Operations
A complete operations function for your AWS estate, delivered against a written SLA. Monitoring, patching, backup, incident response and change management.
- 24×7×365 from Australia
- 15-minute P1 response
- Monthly service review
Cloud Migration
Assess, mobilise, migrate, optimise. Data centre exits, VMware estates, Windows and SQL Server workloads, and database modernisation.
- Dependency-mapped wave plans
- Rehearsed cutovers
- AWS funding support
FinOps & Cost Optimisation
The reporting, the tag policy and the review rhythm — then the levers pulled month after month, for a fixed fee rather than a share of savings.
- Showback by team or product
- Commitment strategy
- Anomaly detection
Security & Compliance
Preventive guardrails, detective controls triaged by humans, and the evidence trail your auditor will ask for.
- Control Tower & SCPs
- Essential Eight mapping
- IRAP readiness
DevOps & Platform Engineering
Golden paths your developers will actually use: Terraform modules, CI/CD, EKS platform build and observability that answers questions.
- Policy-as-code in CI
- Progressive delivery
- Self-serve environments
Data, Analytics & AI
Lakehouse foundations, pipelines that fail loudly, governance that survives an audit, and Bedrock enablement with real spend controls.
- Glue & Lake Formation
- Cost per query
- GenAI guardrails
How the practices combine
Almost nobody buys one in isolation. This is the shape most engagements take.
| If your situation is… | Start with | Then usually | Typical first 90 days |
|---|---|---|---|
| Lease expiry / data centre exit | Cloud Migration | Managed AWS, FinOps | Inventory, wave plan, landing zone, pilot wave live |
| Bill has run away | FinOps | Managed AWS | Cost forensics, tag policy, commitments resized |
| On-call is breaking the team | Managed AWS | DevOps, Security | Alert hygiene, runbooks, pager transferred |
| Enterprise security review landed | Security & Compliance | Managed AWS | Gap assessment, guardrails, evidence automation |
| Deploys are slow and scary | DevOps & Platform | Managed AWS | Pipeline rebuild, IaC modules, environment self-serve |
| Analytics costs more than it returns | Data & AI | FinOps | Partitioning, format work, query cost attribution |
What we commit to in writing
Response targets are contractual on Managed and Enterprise plans, measured from alert receipt or ticket creation, and reported monthly with service credits where we miss.
Full service desk & SLA detail| Severity | Definition | Response | Updates |
|---|---|---|---|
| P1 | Production down or data at risk | 15 min, 24×7 | 30 min |
| P2 | Major degradation, workaround exists | 30 min, 24×7 | 2 hours |
| P3 | Minor fault, limited impact | 4 business hours | Daily |
| P4 | Request or query | 1 business day | On change |
Not sure which one you need?
Start with the free Well-Architected review. It usually answers the question for you — and you keep the report either way.