01 / Cloud Consulting

Good cloud decisions need a foundation.

We make cloud decisions technically and organisationally transparent. Together with architecture, development and operations, we assess applications, dependencies and costs. The result is a target state with reasoned decisions and a sequence your team can implement.

Request an architecture discussion

Record the existing environment and requirements

We start with applications and the workflows they enable. Which systems exchange data? Which component writes to which database? Where are identities, certificates and essential operational credentials held? This inventory connects technical topology with responsibilities and critical user journeys. Availability, recovery time and tolerable data loss are assessed for each application. Load patterns, latency limits, data classification and access requirements are also considered. Unknown dependencies or unconfirmed assumptions become visible as investigation tasks before they determine a target architecture.

Make target platforms comparable

We compare on-premises, public cloud and hybrid models against the same requirements. This includes compute and storage as well as data transfer, operational work, licensing and the capabilities a platform needs over time. A realistic cost model accounts for fluctuating load, reserved capacity and additional environments. Managed services can reduce operational tasks, but tie an application to specific features and interfaces. We document this trade-off for each building block. This distinguishes where deliberate platform dependence creates value and where portability or independent operation matters more.

Plan the operating model alongside the architecture

A target architecture needs an organisational counterpart. We define who provisions infrastructure, approves roles, assesses security updates and leads incident handling. The boundary between your team, the platform provider and other service providers is also described. This produces requirements for automation, access models, monitoring and documentation. If a solution requires knowledge not yet available within the team, capability building belongs in the roadmap. Future operational responsibility is thus considered at the architectural decision stage.

Results you can work with

Depending on the assignment, an assessment provides a system and dependency overview, evaluated architecture options and a prioritised action plan. Important decisions are documented with alternatives, reasons and consequences. Risks, cost assumptions and prerequisites still to be tested remain transparent. A proof of concept can be useful for particularly consequential assumptions, such as access to an existing system, a load test or restoring a dataset. The results inform the target state. The assessment therefore ends with a sound working foundation for implementation.

A typical decision: extend or relocate?

A new customer portal is to be built in the cloud while an authoritative existing system remains in the data centre. We first assess data volume, response times and behaviour when the connection is interrupted. Synchronous access for every user action may create different requirements from asynchronous ingestion of changes. A pilot makes these differences measurable. It tests the complete user journey, including login, data access and error handling. Only then can an informed decision be made on whether a hybrid design is viable, an interface needs changing or the migration sequence should be revised.

A shared decision baseline for technology and business

Architectural decisions often affect several objectives at once: shorter release paths, controllable costs, better recovery or replacing a system approaching end of life. We connect technical options to these objectives and explain their operational consequences. The target state shows system boundaries, data flows and responsibilities. A decision log records which questions are resolved and which depend on a test, contract or organisational approval. Technical and commercial stakeholders can then work from the same assumptions.

A roadmap with acceptance criteria

We divide implementation into steps whose outcomes can be tested. An initial platform foundation may mean reproducible provisioning with limited access rights. A migration pilot may require complete data reconciliation and a demonstrated return path. Each step receives prerequisites and criteria for the next decision. Dependent actions are distinguished from work that can proceed in parallel. The roadmap thus shows what an investment enables, which risks it reduces and which operational responsibility the next stage introduces.

Frequently asked questions

Do all applications have to move to the cloud?

No. We evaluate applications according to their dependencies, operational requirements and costs. Local operation may make sense because of tight coupling to existing systems, for example. A new application can be developed independently in the cloud if identities, data flows and connection failure behaviour are clarified.

What do you need for an assessment?

System overviews, existing architecture documents, cost information and development and operations contacts are helpful. We define in advance which applications and questions will be examined. Read-only access or measurement data is requested specifically; production changes are not an implicit part of an inventory.

When is a proof of concept useful?

When an architectural decision depends on an uncertain assumption. This may concern a latency limit, an authentication path or the recoverability of data storage. We define the specific question and success criteria before building. A successful prototype does not replace subsequent production and operational acceptance.

How concrete is the handover?

Within the agreed scope, you receive the documented starting point, assessed options, decisions and a prioritised roadmap. This includes assumptions used and open risks. A joint walkthrough clarifies which work your team will take on and where further technical tests or decisions are needed.

Take the task forward with purpose

Migration & Modernisation

Move applications and data in tested steps. Dependencies, cutover and recovery determine the plan.

Plan your migration path

On-Premises & Hybrid

Develop viable existing systems and build cloud connections selectively. Data flows and responsibilities remain transparent across both environments.

Explore On-Premises and Hybrid

Discuss your project

Describe your application, environment and desired result. From this, we define a technical investigation or an actionable first step.

Discuss your plans

Which cloud decision is next for you?

Bring a system sketch, your intended objective and the questions currently under discussion. From these, we define an assessment or technical pilot with a clear result.