---
title: "Cloud"
updated: "2026-11-16"
url: "https://www.etheon.com/services/cloud"
---

# Cloud engineering and DevOps

Cloud engineering, from architecture to SRE. We design, migrate and run your cloud, with security built in from the first commit.

## Cloud engineering, from architecture to SRE. We design, migrate and run your cloud, with security built in from the first commit.

### Architecture

Regions, services and data placed for your load.

Architecture. Regions, services and data placed for your load.

Users reach the apps in Region A through the edge; the apps use a queue and a database, with a standby app and a replica in Region B.

### Migration

Off your own servers, in stages.

Migration. Off your own servers, in stages.

- Waves, with a rollback point at each

An old app and an old database on premises, joined to the database in Region A.

### DevOps

Every change built, tested and released.

DevOps and CI/CD. Pipelines that build, test and release every change, and infrastructure kept as code.

- Build, test and release pipelines
- Infrastructure as code
- Staged rollouts

A pipeline from the repository through build and test to release, into the apps in Region A.

### SRE

Watched, alerted and recovered.

SRE. Watched, alerted and recovered.

Logs, metrics and alerts watching the apps, with the standby app and the replica in Region B.

### Security

Identity, keys and audit logs.

Security. Identity, keys and audit logs, set up from the first commit.

- Tenant isolation
- Residency
- Customer-managed keys

The edge, identity, the keys and the audit log.

### Architecture. Regions, services and data placed for your load.

#### What it is

Cloud architecture decides where your systems run and how they connect: regions, services, networks and data placed for your load, your budget and your rules. We design it for the traffic you expect and the failures you must survive, and write it down so your team can run it.

#### What we do

- Choose the cloud and its regions
- Place services and data for your load
- Design for the failures you must survive
- Write it down for your team

#### How we do it

1. Learn the load: Traffic, data and the rules your systems must follow.
2. Design: Regions, services and data placed, with the failures planned for.
3. Review: The design checked with your team before anything is built.
4. Document: Diagrams and decisions your team can run from.

#### Questions

**Which clouds do you work with?**

AWS, Microsoft Azure, Google Cloud and Nebius.

#### What you get

- An architecture design
- Diagrams of the regions, services and data
- A record of each decision and why it was made

#### Stack and tools

- AWS
- Microsoft Azure
- Google Cloud
- Nebius

#### Related

- [Migration](https://www.etheon.com/services/cloud?detail=migration#migration)
- [Security](https://www.etheon.com/services/cloud?detail=security#security)

### Migration. Off your own servers to the cloud you choose, in planned stages.

#### What it is

Migration moves your systems off your own servers to the cloud you choose, in planned waves. Each workload moves with a rollback point, so the business keeps running while it moves, and the old servers are switched off when nothing depends on them.

#### What we do

- Waves
- A rollback point at each

#### How we do it

1. Take stock: Every workload, its callers and its data.
2. Plan the waves: Which workload moves when, each with a rollback point.
3. Move: One wave at a time, the business running throughout.
4. Switch off: The old servers, once nothing depends on them.

#### What you get

- A migration plan in waves
- The new environment as code
- A rollback plan for each wave

#### Stack and tools

- AWS
- Microsoft Azure
- Google Cloud
- Nebius

#### Related

- [Modernization](https://www.etheon.com/services/software?detail=modernization#modernization)

### DevOps and CI/CD. Every change built, tested and released, and the infrastructure kept as code.

#### What it is

DevOps and CI/CD make every change safe to release. We build pipelines that build, test and release each change, keep your infrastructure as code so it can be reviewed and rebuilt, and roll changes out in stages.

#### What we do

- Pipelines
- Infrastructure as code
- Staged rollouts

#### How we do it

1. Map the path: From a commit to production, as it runs today.
2. Build the pipeline: Build, test and release for every change.
3. Code the infrastructure: Every environment written as code and reviewed.
4. Roll out in stages: A small share first, with a way back.

#### What you get

- Pipelines in your repository
- Your infrastructure as code
- A runbook for releases

#### Stack and tools

- Infrastructure as code
- Delivery pipelines
- Container orchestration
- Secrets management

#### Related

- [Data platforms](https://www.etheon.com/services/data?detail=platforms#platforms)

### SRE. Watched, alerted and recovered, with a written review after every incident.

#### What it is

Site reliability engineering keeps your systems up once they are live. We set up the logs, metrics and alerts that watch them, the runbooks that say what to do, and a written review after every incident so the same failure is less likely to happen again.

#### What we do

- Logs, metrics and alerts
- Runbooks for what can break
- On-call response during the engagement
- A written review after every incident

#### How we do it

1. Alert
2. Acknowledge
3. Contain
4. Restore
5. Review

#### What you get

- Dashboards and alerts
- Runbooks
- Incident reviews

#### Stack and tools

- Observability
- Alerting
- Incident management
- Status pages

### Security. Identity, keys and audit logs, set up from the first commit.

#### What it is

Cloud security covers who can reach your systems and your data, and how you show it. We set up identity and single sign-on, encryption keys, tenant isolation, data residency and audit logs from the first commit, so a security review starts from controls that already exist.

#### What we do

- Tenant isolation
- Residency
- Customer-managed keys
- Single sign-on

#### How we do it

1. Review: Your systems, your data and the controls you need.
2. Set up identity: Single sign-on and roles, from the first commit.
3. Protect the data: Encryption keys, tenant isolation and residency.
4. Gather the evidence: Audit logs and records an auditor can read.

#### Questions

**Can you help us pass an audit?**

Yes. We set up the controls and the logging an auditor looks for, and gather the evidence from your systems. The audit itself stays between you and your auditor.

#### What you get

- Identity and access set up
- Encryption keys under your control
- Audit logs and the evidence for your review

#### Related

- [Trust and compliance](https://www.etheon.com/company/trust#compliance)

## Migration in waves.

Workloads move in planned stages, with a rollback at each one.

| Workload | Wave |
| --- | --- |
| Website | Wave 1 |
| Customer API | Wave 1 |
| Reports | Wave 2 |
| Data warehouse | Wave 2 |
| Batch jobs | Wave 3 |

## Who secures what.

Your cloud provider, our engineers and your team, each with a clear part.

| Area | Your cloud provider | Etheon sets up | Your team owns |
| --- | --- | --- | --- |
| Data centres and hardware | Runs them (leads) | No part | No part |
| Network and firewall | The building blocks | Designed and set up (leads) | Approves changes |
| Identity and access | The identity service | Roles and single sign-on (leads) | Who gets access |
| Encryption and keys | The key service | Encryption on by default | Holds the keys, if you choose (leads) |
| Application code | No part | Built, tested and reviewed (leads) | Accepts each release |
| Data and backups | Storage | Backups, restores tested | What is kept, and how long (leads) |
| Compliance evidence | Its own reports | Evidence for your auditor (leads) | The audit itself |

We hold SOC 2 Type II, ISO 27001 and CSA STAR. Our own certifications; your audit stays yours.

[Trust](https://www.etheon.com/company/trust#compliance)

## When something breaks.

What happens between the alert and the review.

1. Alert: Monitoring raises an alert to the engineer on call.
2. Acknowledge: A person takes it and says so in your channel.
3. Contain: A circuit breaker, a fallback or a rollback limits the harm.
4. Restore: The service is back; we confirm with you.
5. Review: A written review: what happened, why, and what changes.

- [Data](https://www.etheon.com/services/data): Pipelines, platforms and BI
- [AI](https://www.etheon.com/services/ai): Agents, models and MLOps