EU customers: entirely on STACKIT in the EU
For EU customers, production operation runs entirely on STACKIT in the EU. Website delivery also uses the configured EU region of the STACKIT CDN distribution. Additional data paths and subprocessors are disclosed in contractual and privacy documentation.
USA and APAC follow regionally
The rollout for the USA and APAC is approaching. Customers are intended to receive production operation from their respective region. Concrete availability and scope are confirmed before contract conclusion.
Self-hosting is a qualified option
During onboarding, region, integrations, data paths and operating responsibility are defined together. Each tenant therefore receives a documented operating model that connects delivery, support and continued development throughout the lifecycle.
Qualification evaluates target infrastructure, update path, monitoring, backup, support and integrations together. The result clearly assigns which components run in the customer region, who operates them, how updates are delivered and which service paths apply during an incident. This assignment becomes part of onboarding and operating documentation.
What should be clear before onboarding
- Region and tenant scope
- Required Zscaler, ITSM and notification integrations
- Isolation, roles and operating responsibility
- Update, monitoring and support path
- Contractually documented data paths
Why regional delivery is more than a data-centre location
A region describes more than where compute runs. Databases, object storage, backups, monitoring, support access, CDN delivery and connections to external systems all belong to the operating picture. Contractual documentation must describe these paths for the selected model.
CentaurNexus assigns a customer to a regional operating environment. Tenant isolation, roles and audit apply independently of region. Region does not change the functional protection of customer contexts. It determines where the corresponding platform components operate.
Describe the EU model precisely
For EU customers, CentaurNexus operates entirely on STACKIT in the EU. The regional operating model includes the connected Zscaler, ITSM and notification paths agreed for the customer tenant.
The website is delivered through the EU region of the active STACKIT CDN distribution. Regional operation, integrations and responsibilities are documented together.
USA and APAC as separate regional environments
The USA and APAC rollout is approaching. The objective is to provide production operation from the customer's region rather than route every tenant through one global region. Exact availability is confirmed for the region and contract date.
Before regional go-live, infrastructure, data storage, backups, monitoring, support processes and external integrations must be accepted together. A marketing status is not sufficient. The customer receives the binding scope in the offer and corresponding operating documentation.
What qualified self-hosting means
Self-hosting starts with a joint assessment of the target environment. It is not merely a question of starting a container. Network zones, identity, secrets, databases, storage, backup, monitoring, updates and support access must form a complete operating path.
Qualification determines which components run in the customer environment, which external services remain necessary and who owns each part. The result is a concrete scope that can be described contractually. Only then can the model be offered reliably.
Responsibility between customer and CentaurNexus
In the regional SaaS model, CentaurNexus is responsible for the agreed platform delivery. The customer provides the required access, scopes and approvals for connected systems. Self-hosting requires a more detailed split: infrastructure, platform operation, updates, monitoring, incident handling and backup must each have an owner.
A clear RACI assignment prevents gaps. Every operating task needs an executor, decision owner, notification path and defined evidence for incidents.
Updates and support in the self-hosting model
A qualified model needs a tested release path. New versions must not alter tenant isolation, data migrations, integrations or read-back contracts without control. Staging, compatibility review, rollback path and maintenance-window ownership therefore belong to the qualification.
Support access must also be limited and traceable. Whether and how CentaurNexus can access the customer environment is defined technically and contractually. Self-hosting does not automatically place every operating task entirely with the customer or entirely with CentaurNexus.
Integrations and feed sources in regional planning
OneAPI, NSS, LSS, ITSM and notification channels connect the CentaurNexus environment with external systems. Onboarding therefore establishes from which region those systems are reached, which data leaves the operating environment and which contractual prerequisites apply.
Historical NSS and LSS analysis also brings feed path, retention and data class into the plan. Regional platform operation does not automatically answer every question about a customer-configured third-party integration. The documented end-to-end path remains authoritative.
Plan for portability and termination
A complete operating model also describes how configuration, exports and agreed customer data are handled during a regional move or contract termination. Responsibility, format, deadline and deletion path are established in advance.
For self-hosting, the parties additionally define which components and keys remain in the customer environment and how support access ends. This exit perspective prevents operating responsibility from being discussed only at the end of service.
Qualification as a joint decision workshop
Technology, security, privacy, procurement and operations bring different requirements. Qualification combines them in one matrix. Open items receive a concrete verification step instead of being replaced by a broad promise.
The result is a traceable decision for regional SaaS, self-hosting or a later review point. The workshop becomes part of solution architecture rather than a sales disclaimer.
Keep evidence current
Region, subprocessors, integrations and operating responsibility can change during the service life cycle. Contract documents, privacy information and technical operating records are therefore updated when a reviewable change occurs. An earlier acceptance cannot remain the sole basis for a materially changed service forever. Named owners review the records and evidence on an agreed recurring cycle.
Criteria for choosing the right model
- Define the required region and contracting customer entity.
- Document data classes and external integration paths.
- Compare SaaS and self-hosting responsibilities.
- Qualify target infrastructure, updates, monitoring, backup and support.
- Define acceptance, incident paths and recurring evidence.
- Confirm availability and concrete contract scope before ordering.
The best model is the one whose technology and responsibilities are fully described. Regional SaaS delivery and qualified self-hosting provide different but clearly bounded paths.
Frequently asked questions
Where does CentaurNexus run for EU customers?
Production operation for EU customers runs entirely on STACKIT in the EU.
Are the USA and APAC available?
The regional rollout is approaching. Concrete availability is confirmed before contract conclusion.
Is self-hosting universally available?
No. Self-hosting is qualified for the concrete infrastructure and the required operating and integration scope.
Sources and further information
See the workflow in context
Choose the relevant role in the demo launcher. The demo uses prepared sample data.
Open demo launcher