Skip to main content

Network & cloud infrastructure

Architecture, cloud migration and hybridisation, DevOps pipelines for demanding production systems.

AWS Azure Hybrid Cloud DevOps
Server racks in a data room

Key features

Standards covered

AWS Well-Architected Azure CAF ISO 27001

The cloud as seen from Yaoundé, not from a brochure

The reference architectures of the big cloud providers are written for companies with redundant fibre and no data-residency constraints. That is not the context of most of our clients. In the CEMAC region, the right architecture works with real-world connectivity, the sovereignty requirements of public institutions and a foreign-currency budget that must be defended — which often means a hybrid: an on-premise footprint in Cameroon, interconnected with AWS or Azure through VPN or a dedicated link, with genuinely elastic workloads on the cloud side.

We refuse two shortcuts. Wholesale lift-and-shift, which relocates your problems and adds a monthly invoice. And dogmatic cloud-first, which ignores that a production application can have excellent reasons to stay on site. Every application gets a cloud-readiness score, every choice is documented, and the architecture is reviewed against the Well-Architected Framework before anything moves. It is the same rigour we apply to the ERP rollouts that later run on these infrastructures.

Technical stack

Method

How we work

  1. 01

    Audit of the existing estate

    2 to 4 weeks

    Application inventory, dependencies, a cloud-readiness score per application, sovereignty and connectivity constraints. We do not migrate what we do not understand.

  2. 02

    Target architecture & trajectory

    3 to 6 weeks

    Target and transition diagrams, reasoned choices — public cloud, hybrid or multi-cloud —, reviewed against the Well-Architected Framework or the Cloud Adoption Framework, with costs projected per environment.

  3. 03

    Migration in waves

    4 to 8 weeks per wave

    We favour replatforming — moderate modernisation during the move — over pure lift-and-shift, which captures none of the cloud's value. Infrastructure as Code and CI/CD pipelines from the first wave.

  4. 04

    Run & observability

    Ongoing

    Monitoring, operations runbooks, contractual SLOs, periodic cost reviews. Managed operations are optional; observability is not.

Deliverables

What you receive

Architecture dossier

Target and transition diagrams, reasoned choices, Well-Architected or CAF compliance matrix.

Infrastructure as Code

Versioned Terraform or Bicep repositories, operational deployment pipelines.

Operations runbooks

Monitoring, incident and recovery procedures, tested with your teams.

SLO & cost table

Quantified service commitments and cloud cost projections per environment.

Commitment

The cloud is not a destination. It is a trade-off — sovereignty, latency, costs — that we document with numbers.
Every architecture we deliver is reviewed against the AWS Well-Architected Framework or the Microsoft Cloud Adoption Framework, with documented gaps. SLOs and operating costs are quantified at framing — not discovered on the first invoice.

Getting started

How to get started

  1. 1

    Scoping call

    45 minutes on your estate: applications, sovereignty constraints, team in place.

  2. 2

    First written trajectory

    Envisioned architecture and budget range.

  3. 3

    Within 48 business hours

    No commitment on your side.

FAQ

Frequently asked questions

Should everything move to the cloud?

No. We start from your constraints (sovereignty, latency, costs) — the right answer is often a hybrid architecture with an on-premise footprint in Cameroon.

Do you work with AWS or Azure?

Both, depending on your estate and in-house skills. Every architecture is reviewed against the Well-Architected Framework or the Cloud Adoption Framework.

Do you provide managed operations after migration?

Yes: monitoring, operations runbooks, contracted SLOs and cloud cost projections per environment.

Let's talk about your project

A demo, an audit, an ERP to roll out? One message is enough to start the conversation.