Sovereign Multi-Cloud mit Codesphere
Reduce Cloud Dependencies and Build Portability into Application Architecture.
Cloud Portability Starts with Application Architecture
Modern cloud platforms combine compute resources with a wide range of prebuilt services, for example for databases, messaging, identity management, or monitoring. These services accelerate development and operations while also shaping an application's architecture: The more tightly provider-specific services are integrated, the more closely an application becomes technically tied to the interfaces and operating models of the respective cloud provider.
For companies and public-sector organizations that develop their own software, this creates an architectural challenge: Applications should take advantage of modern cloud platforms while being designed so that infrastructure decisions can be reevaluated when technical, economic, or regulatory requirements change. This requires transparency into which application components are already portable, which services are tied to a provider, and what alternatives are available for a migration.
Codesphere addresses this by providing a shared platform layer between applications and infrastructure. ISO-Gruppe connects this platform with the existing enterprise IT landscape: It develops the target architecture, introduces the platform, migrates existing applications, and supports ongoing operations.
A Shared Platform Layer Between Applications and Infrastructure
Codesphere combines the development environment, CI/CD automation, and infrastructure management in a shared platform layer between applications and the infrastructure in use. Development, test, and production environments are therefore based on a common technology foundation, regardless of the infrastructure on which they ultimately run.
A Shared Platform Layer Between Applications and Infrastructure
Codesphere combines the development environment, CI/CD automation, and infrastructure management in a shared platform layer between applications and the infrastructure in use. Development, test, and production environments are therefore based on a common technology foundation, regardless of the infrastructure on which they ultimately run.
The architecture lays the groundwork for a cloud exit strategy from the outset. By separating the application layer from the infrastructure, it becomes transparent which application components are already portable and where dependencies on cloud-specific services remain. These dependencies can then be assessed systematically and reduced step by step.
At the same time, Codesphere allows applications to be operated and orchestrated across different infrastructures. For example, one part of an application can run on German or European infrastructure, while another part remains with a hyperscaler by design.
How far an application can be moved depends on its architecture and the cloud services it uses. Sovereign Multi-Cloud creates transparency around dependencies and prepares migration paths accordingly.
What Sovereign Multi-Cloud Changes
Applications are designed to rely less heavily on the specific services of a single cloud provider.
Separating the application layer from the infrastructure shows which application components can already run on multiple infrastructures and which still require adaptation.
For key application components, the steps required to switch infrastructure and the cloud-specific services that would need to be replaced can be defined in advance.
Data location, regulatory requirements, and the ability to switch infrastructures are considered in the architecture from the outset.
Choose Infrastructure Based on Requirements
Sovereign Multi-Cloud primarily provides flexibility in infrastructure decisions: Infrastructure can be selected based on an application's actual requirements and adjusted over time.
Different infrastructure models can be considered, including international public cloud offerings, private cloud environments, German and European cloud providers, on-premises data centers, hybrid combinations, and isolated air-gapped environments for particularly sensitive applications.
Which model is suitable in each case depends on several factors:
- Data Location and Regulatory Requirements
- Security and Compliance Requirements
- Technical Performance Requirements and Scalability
- Available Platform and Cloud Services
- Cost and Operating Model
The Role of ISO-Gruppe
Codesphere provides the platform technology. ISO-Gruppe connects it with the existing enterprise IT landscape: It analyzes the current environment, develops the target architecture, implements and integrates the platform, migrates and connects existing applications, trains the teams involved, and, if required, takes over ongoing operations for the platform environments.
We analyze existing applications, cloud services in use, infrastructure models, and technical dependencies. This shows which applications are suitable for a cloud-agnostic platform approach and which cloud-specific services require particular attention during architecture design and migration.
Together with you, we develop the target architecture: which infrastructure models will be used in the future and how applications, the platform, CI/CD, and operations work together. Technical, regulatory, and economic requirements are incorporated into a common target state.
We implement and integrate the platform into existing development and infrastructure processes: Interfaces, access, environments, and existing tools are incorporated into the target architecture.
We migrate existing applications to the platform step by step and connect them to existing systems. The focus is on the application's actual dependencies, the portability of its components, and the adaptations required for provider-specific services.
We set up the required platform and cluster environments, integrate CI/CD and DevOps processes, and can take over ongoing technical operations on request. This includes continuous support and further development of the environments while they are in use.
We train development and operations teams to work with the platform; a certification offering is also in development.
When This Approach Is Relevant
Sovereign Multi-Cloud is particularly relevant for companies and public-sector organizations that develop or operate their own software and actively shape their infrastructure.
Applications are developed, further developed, or operated outside a standard SaaS model by the organization itself.
Multiple cloud and infrastructure models are already in use, from public cloud to an organization's own data center.
Data location and regulatory requirements influence architectural decisions.
Platforms and processes that have evolved over the years form a heterogeneous landscape.
Organizations have the greatest scope to shape applications they develop and operate themselves.
Codesphere as the Technology Foundation and Partner
Codesphere is a software company based in Karlsruhe, founded in 2020, and positions its platform as “The World’s First Virtual Cloud.” At its core is a shared platform layer for development, deployment, and operations. It includes development and CI/CD capabilities as well as functions for infrastructure, networking, storage, and monitoring. The platform can be used across different infrastructures, from public and private clouds to European cloud offerings, on-premises data centers, hybrid environments, and air-gapped environments. Development teams can work in a browser or continue using established development tools.
The collaboration is based on a strategic partnership between ISO Public Services, an ISO-Gruppe enterprise, and Codesphere. Codesphere contributes the platform technology, while ISO-Gruppe contributes its consulting, integration, and implementation expertise.
Frequently Asked Questions About Sovereign Multi-Cloud with Codesphere
A Sovereign Multi-Cloud combines different cloud and infrastructure models with requirements for control, portability, data location, and digital sovereignty. Applications can, for example, run on public clouds, European cloud offerings, private clouds, or an organization's own infrastructure. The key is to consider dependencies and migration options as part of the architecture and platform concept from the outset.
A traditional multi-cloud describes the use of multiple cloud providers. A Sovereign Multi-Cloud also considers how much control organizations have over the infrastructure in use, how readily that infrastructure can be changed, and what requirements apply to data location, compliance, and digital sovereignty.
Codesphere creates a shared platform layer between applications and infrastructure. This makes dependencies on individual cloud services more transparent and allows migration paths to be considered as part of the architecture. How far an application can actually be moved still depends on its architecture and the provider-specific services it uses.
Codesphere can be deployed across different infrastructure models, for example on public and private clouds, European cloud offerings, an organization's own on-premises infrastructure, and hybrid or air-gapped environments. The appropriate combination depends on the technical, regulatory, and operational requirements of the individual application.
The approach is particularly suitable for applications developed or operated by the organization itself, where companies or public-sector organizations can actively shape architecture, development, and infrastructure. With standard SaaS applications, this scope for control largely remains with the respective provider.
ISO-Gruppe analyzes the existing application and infrastructure landscape, develops the target architecture, integrates Codesphere into existing systems and processes, and supports the migration and connection of existing applications. It also sets up platform and cluster environments, integrates CI/CD and DevOps processes, provides ongoing technical operations, and trains the development and operations teams involved.
Johannes Reichel
90491 Nuremberg
Create More Flexibility in Your Cloud Strategy
The starting point is your existing application landscape: Which applications use provider-specific cloud services? Which infrastructure models should be available in the future? What requirements arise from data location, security, compliance, operations, and cloud exit? A consultation helps assess these questions based on your specific situation.