Public cloud consulting · Multi-cloud

When your infrastructure spans several clouds

Running several clouds in parallel is complex because they differ. We help you work out concepts that keep you flexible and keep the effort low.

Active in two clouds

Kubernetes as the shared layer

One login for both clouds

01

Abstraction

Kubernetes is the same in every cloud

01

Abstraction

Kubernetes is the same in every cloud

Managed services differ from cloud to cloud. Kubernetes is the same. That allows very similar deployments of your applications on every environment where Kubernetes is available.

Applications built once, rolled out everywhere

Switching clouds stays possible

Your team learns one system

02

Operations

The repository defines the target state

02

Operations

The repository defines the target state

Argo CD distributes the target state from Git into both clouds. Drift is detected and corrected.

Every change is a pull request

Argo CD reverts drift

One on-call service for both clouds

03

Identity

One login for all clouds

03

Identity

One login for all clouds

One identity provider, federated into every cloud for targeted and maintainable synchronization.

Short-lived access instead of permanent keys

Every access is logged

04

Case study

One hub for all

04

Case study

One hub for all

One clearly defined entry point with identity-based access. Low maintenance, flexible, and it passes every audit.

Only same tier to same tier

Only registered applications

Every connection is logged

HubVPN Eingang, hochverfügbarStandort AStandort BEin Eingang, DNS, Protokolle aller VerbindungenUnternehmensnetz nur über den HubSpokeAWSEKS im Segment ProduktionProduktionTestVerwaltungSpokeAzureAKS im Segment ProduktionProduktionTestVerwaltungSpokeGoogle CloudGKE im Segment ProduktionProduktionTestVerwaltungerlaubt: gleiche Stufeverweigert: Test zu Produktion

05

entry point

The next steps

05

entry point

The next steps

1

Assessment

We work out your needs and goals with you and write a qualified offer with effort and duration.

2

Target picture

We create an architecture target picture: how data flows and where it is stored and encrypted. We also create a business continuity and disaster recovery concept. Everything must be accepted and confirmed by you.

3

Build

We build the infrastructure according to the plan, integrate applications into monitoring and enforce regular backups.

4

Failover drill and handover

We test the disaster recovery concept in practice and document the time it takes. Then briefing and handover.

06

Entry point

A conversation first

06

Entry point

A conversation first

Intro call

30 minutes, free of charge

You describe your clouds and the service that must not fail. We tell you what comes first and the range the effort falls in.

As you wish

Architecture consulting

Billed by effort, the result as a document.

Build

At a fixed price after a short assessment.

Support on call

Questions, reviews, the next version.

We are done only when everything has been accepted and the failover test has been completed successfully.

07

Questions

Frequent questions about multi-cloud

07

Questions

Frequent questions about multi-cloud

Isn't multi-cloud more expensive than one cloud?

What about the data?

Do we have to move everything to Kubernetes?

Does multi-cloud help with DORA?

Next step

30 minutes that belong before your next audit

An intro call with the founders. We listen to where you stand and recommend the best next step.

30 minutes

Free of charge

With the founders

Request an intro call

One email is enough. We reply with a proposed time.

Write an email

Next step

30 minutes that belong before your next audit

An intro call with the founders. We listen to where you stand and recommend the best next step.

30 minutes

Free of charge

With the founders

Request an intro call

One email is enough. We reply with a proposed time.

Write an email