PROFESSIONAL SERVICES

Cloud engineers for the work a bot can't do alone.

cm-bot runs the routine. For pipelines, security programs, migrations and new architecture, the Cloud Modules team works with you in your own accounts and repositories, and hands everything over when it's done.

Three practices

Pick one, or bring us in for all three

Each practice is run by engineers who work on AWS, Google Cloud and Azure every day. You get the work done and the knowledge to run it after we leave.

PRACTICE 01

DevOps

Ship faster with pipelines, infrastructure as code and platforms your team can run on its own.

What we do

  • CI/CD pipelines with GitHub Actions, GitLab CI or Jenkins: build, test, deploy and roll back.
  • Infrastructure as code with Terraform or CloudFormation, in reusable modules.
  • Containers and Kubernetes on EKS, GKE or AKS, with Helm and GitOps.
  • Observability: metrics, logs, traces and alerts that reach the right person.
  • Cost optimization: right-sizing, schedules and commitments.

What you get

  • Pipelines and code in your own repositories.
  • Runbooks for deploys, rollbacks and incidents.
  • A handover session with your team.
PRACTICE 02

SecOps

Find what's exposed, close it, and make sure you hear about the next problem before an attacker does.

What we do

  • Cloud security review across all your accounts and projects, with findings ranked by risk.
  • Identity and access: least-privilege roles, MFA, removing old keys and users.
  • Network exposure: security groups, public endpoints, WAF and TLS.
  • Logging and detection: CloudTrail, GuardDuty, Security Hub and alert routing.
  • Compliance readiness for SOC 2 and ISO 27001: controls, owners and evidence.

What you get

  • A findings report ordered by what to fix first.
  • Fixes applied with you, and incident playbooks.
  • Alerts that reach your team, tested end to end.
PRACTICE 03

Cloud architecture

Design for what you'll run next year: reliable, secure and priced for the load you actually have.

What we do

  • Architecture reviews against the AWS, Google Cloud and Azure well-architected frameworks.
  • Migrations from on-premises to the cloud, or from one cloud to another.
  • Landing zones: multi-account structure, networking and guardrails from day one.
  • High availability and disaster recovery, with restore tests that prove it works.
  • Cost-aware design: the right services and sizes before the bill arrives.

What you get

  • Architecture diagrams and written decisions.
  • A migration or build plan with milestones.
  • Recovery test results you can show an auditor.
How we work

Clear scope, your accounts, a real handover

1

Discover

A call with your team to understand the goal, the systems and the constraints.

2

Plan

A written scope, timeline and price before any work starts.

3

Build

We work in your accounts and repositories, with updates every week.

4

Hand over

Documentation, runbooks and training, so your team owns the result.

Assessment

A fixed-scope review of your cost, security or architecture, with a prioritized plan.

Project

A defined piece of work, such as a pipeline, a migration or a landing zone, delivered end to end.

Ongoing support

Engineers on call for your team each month, for changes, reviews and incidents.

With cm-bot

The team and the bot work together

If you use Cloud Modules, our engineers start from what cm-bot already knows about your accounts, and leave it running the routine when they're done.

  • Scheduler data shows which environments sit idle, so cost work starts with real numbers.
  • Attack surface map findings become the first items of a security review.
  • After the project, cm-bot keeps schedules and checks running every day.

Tell us what you're building.

An engineer will answer within one business day.

Draft service list. Edit it to match what Cloud Modules offers.