We work the platform layer and we do not pretend to work above it. What follows is what the firm has actually run in production, not a capability list assembled for a pitch.
Anansi is not a generalist shop. We build and run the cloud platform: the foundation workloads deploy into, the container runtime they execute on, and the pipelines that ship them there. Where a program needs specialist work above that line, we say so and bring in a partner rather than stretching to cover it.
Build it, then run itBuilt on a decade of production experience in regulated and high-availability environments, leading DevSecOps engineers, Linux administrators, and cloud engineers across AWS and Azure.
CI/CD engineering with security integrated through the development lifecycle. Pipeline design, policy enforcement, artefact integrity, and the automation that keeps a release honest.
Containerized workload design and operation, from image hygiene and registry strategy through orchestration, scaling, and resource governance.
Multi-account AWS and Azure architecture, network and identity design, and Terraform-declared environments inside strict compliance boundaries.
Monitoring and telemetry design for platforms rather than single services, including the dashboards and thresholds operations teams run against daily.
Hardening baselines, vulnerability management, and the control mapping and evidence work that carries a system through an audit without a scramble.
The platform side of machine learning rather than the modelling. Compute and accelerator provisioning, deployment paths, and the delivery automation around them. AWS Certified Machine Learning Engineer.
Most consultancies leave at go-live. The harder discipline is the environment that stays healthy afterwards, and the automation and evidence that make that possible without heroics.
Terraform module design, remote state and locking, and reusable patterns across many accounts and environments. Provisioning becomes a reviewed pull request rather than a ticket and a console session.
Dashboards, alert thresholds, and telemetry pipelines designed for platforms rather than single services, including the discipline of alerting on what an operator can act on rather than on everything that moves.
Backup, restore, and failover treated as procedures that are exercised and evidenced rather than assumed. Runbooks written while the reasoning is fresh, and validation that proves recovery actually works.
Right-sizing, instance consolidation, storage tiering, and commitment strategy, backed by the tagging and showback discipline that keeps the savings in place after the engagement ends.
Large multi-tenant estates moved across cloud platforms with assessment, target architecture, cutover sequencing, and validation gates at every step. Multi-cloud across AWS, Azure, Google Cloud, and Oracle Cloud.
Least-privilege access design, encryption posture, centralized logging, and the control mapping and evidence work that carries a platform through an audit or accreditation without a scramble.
Certifications held across the firm, AWS DevOps Engineer Professional · AWS Solutions Architect Associate · AWS Machine Learning Engineer · AWS Developer Associate · HashiCorp Terraform Associate · Azure Administrator · CompTIA Security+ · Linux+ · Oracle Linux
Tell us the scope and we will tell you honestly which parts we should be doing, and which parts belong with someone else.
Start a conversation