Open Telekom Cloud vs Unomed Cloud PACS

Compare Open Telekom Cloud and Unomed Cloud PACS on capabilities, jurisdiction, assurance, and fit for European buyers.

Both listed as alternatives to: Amazon Web Services (AWS), Microsoft Azure

Logo: Open Telekom Cloud

Open Telekom Cloud

Germany· Cloud Computing

Needs review

Shortlist when you need a German Telekom/T-Systems OpenStack public cloud with DE/NL/CH regions and a strong BSI C5/ISO/TISAX package for regulated or public-sector workloads. Skip when you need hyperscaler global PaaS breadth or pure self-hosted OpenStack—consider OVHcloud, Scaleway, or AWS/Azure for those cases.

EU-operated (T-Systems)OpenStack public IaaSBSI C5 Type II (claimed)DE / NL / CH regionsGPU + ModelArts AIPay-as-you-go
Logo: Unomed Cloud PACS

Unomed Cloud PACS

Switzerland· Cloud Computing

Needs review

Shortlist for Swiss practices that want a cloud DICOM archive, browser viewing and referrer sharing without replacing their PIS, and that accept a Zurich SaaS vendor with claimed Swiss image hosting. Skip when you need a default CE-marked diagnostic viewer, a fully public subprocessor and audit pack, or a self-hosted PACS you operate yourself. Consider PostDICOM or a classic on-prem PACS plus sharing tool when those constraints dominate.

Swiss-operatedCloud PACS / VNADICOM archiveBrowser viewerPIS overlay
Open Telekom Cloud vs Unomed Cloud PACS: Snapshot
FeatureLogo: Open Telekom CloudOpen Telekom CloudLogo: Unomed Cloud PACSUnomed Cloud PACS
Country of originGermanySwitzerland
CategoryCloud ComputingCloud Computing
Open sourceNoNo
Self-hostedNoNo
HeadquartersGermanySwitzerland
Legal entityT-Systems International GmbH (Deutsche Telekom group); product marketed as T Cloud Public / Open Telekom CloudUnomed AG
Governing lawGerman / EU law for the cloud service (confirm contract)Not listed
US parent / controlNo known US parentNo known US parent
CLOUD Act exposure (indicative)LowMedium
EU-hosted statusNot listedPartial
Hosting / residencyPrimary: Telekom/T-Systems twin-core data centers in Germany (Biere/Magdeburg), Netherlands (Amsterdam region), and Switzerland (Bern/Zollikofen). No public indication that AWS, Azure, or GCP is the primary IaaS host. Backups/DR via platform multi-AZ services. Full public subprocessor table not found—request DPA annex. Historical Huawei technology partnership is supply-chain diligence, not US-cloud hosting.Vendor claims primary hosting, databases and DICOM storage in Switzerland. Privacy policy lists identity/liveness processing in EU (Ireland) and speech recognition in EU (Denmark). API CSP references AWS S3 eu-central-2 (Zurich) and AWS Rekognition/Cognito eu-west-1; push via Firebase; website may use Cloudflare WAF cookies and Google Analytics. Named subprocessor list on request only.
Summary

Deutsche Telekom / T-Systems sovereign European public cloud (now marketed as T Cloud Public): OpenStack-based IaaS and platform services in Germany, Netherlands, and Swiss regions with BSI C5, ISO, and SOC attestations.

Swiss cloud PACS and vendor-neutral archive for storing, viewing and sharing DICOM medical images in the browser, integrated with existing medical practice workflows.

Tags
At a glance: Open Telekom Cloud vs Unomed Cloud PACS
At a glanceLogo: Open Telekom CloudOpen Telekom CloudLogo: Unomed Cloud PACSUnomed Cloud PACS
HQ / operatorGermany — T-Systems / Deutsche TelekomNot listed
Current brandT Cloud Public (formerly Open Telekom Cloud)Not listed
PlatformOpenStack-based public cloudNot listed
RegionsGermany (Biere/Magdeburg), Netherlands, SwitzerlandNot listed
Commercial modelPay-as-you-go (+ optional discounts/reservations)Not listed
Self-hostNo — managed public cloudNot listed
HQNot listedZurich, Switzerland
Legal entityNot listedUnomed AG (CHE-374.858.885)
Product typeNot listedCloud PACS / VNA SaaS
Self-hostedNot listedNo (local connector only)
Default viewerNot listedOHIF (not for diagnosis per GTCs)
Data residency regionsNot listedSwitzerland claimed for DICOM/hosting; some auxiliary processing in EU (IE/DK) per privacy policy
Key capabilities: Open Telekom Cloud vs Unomed Cloud PACS
Key capabilitiesLogo: Open Telekom CloudOpen Telekom CloudLogo: Unomed Cloud PACSUnomed Cloud PACS
EU-operated (T-Systems)YesYes
OpenStack public IaaSYesNot listed
BSI C5 Type II (claimed)YesNot listed
DE / NL / CH regionsYesNot listed
GPU + ModelArts AIYesNot listed
Pay-as-you-goYesNot listed
Cloud PACS / VNANot listedYes
DICOM archiveNot listedYes
Browser viewerNot listedYes
PIS overlayNot listedYes

Open Telekom Cloud

  • OpenStack public cloud with Elastic Cloud Server and GPUs

    Self-service IaaS on OpenStack: Elastic Cloud Server flavors from general-purpose to GPU shapes for AI/ML and graphics, plus Dedicated Host and Bare Metal where the region supports them. Provision via console, API, or automation; Auto Scaling for metric-driven capacity. Suited to production VMs and hybrid patterns that need European operator control rather than a thin VPS plan.

  • Multi-AZ object, block, and file storage in EU regions

    Object Storage Service provides S3-compatible multi-AZ object storage; Elastic Volume Service attaches block disks with snapshots; Scalable File Service offers NFS shared filesystems. Cloud Backup and Recovery and related services back up VMs and volumes into platform object storage. Pin workloads to DE, NL, or Swiss regions according to residency policy.

  • VPC networking, Direct Connect, and security services

    Virtual Private Cloud isolation, Elastic Load Balancer, VPN, NAT, Enterprise Router, and Direct Connect for high-bandwidth hybrid links. Security stack includes Anti-DDoS, WAF, Cloud Firewall, Host Security Service, and Key Management Service with bring-your-own-key options—useful for regulated network architectures without leaving Telekom-operated regions.

  • Cloud Container Engine and managed data services

    Cloud Container Engine runs Kubernetes-managed clusters and images; companion services cover container instances and registries. Relational Database Service supports MySQL, PostgreSQL, and Microsoft SQL with HA and backup patterns; document, cache (Redis-class), MapReduce, and search services extend the data plane. Service availability differs between DE and NL—check the regional matrix before design freezes.

  • ModelArts and sovereign AI positioning

    ModelArts provides an end-to-end AI development path (data prep, training, deployment) on European infrastructure, with GPU-backed instances for training and inference. Aimed at teams that want model and training-data residency under the same European operator as their IaaS—confirm which AI services exist in your chosen region (several AI offerings are DE-focused).

  • Twin-core European data centers (DE, NL, CH)

    Published regions: twin-core Germany (Biere/Magdeburg), Netherlands (Amsterdam area), and Switzerland (Bern/Zollikofen) for Swiss data residency. Vendor claims geo-redundant twin-core design, high availability targets, and renewable-powered German facilities. Not a global multi-continent footprint—by design for European sovereignty shortlists.

Unomed Cloud PACS

  • Cloud DICOM archive (VNA-style)

    Central archive for studies from in-house modalities and external institutes, with DICOM export so you can take the archive with you. Storage is billed as you grow; long-term statutory retention remains the customer's duty under Unomed's terms.

  • Zero-footprint browser viewer (OHIF default)

    Open studies in the browser with nothing installed on the workstation. OHIF is the default; other viewers can be connected on request. Unomed's GTCs state the standard viewer is not authorised for diagnostic reporting.

  • PACS inbox with assisted patient matching

    Inbound studies land in an inbox; Unomed suggests the matching patient (including fuzzy name matches) and a human confirms. Useful when institutes send studies that do not already carry a clean order from your record.

  • Share via messenger and guest links

    Send studies to colleagues, referrers and patients through Unomed messenger. Recipients without an account get a time-limited guest link; registered users keep the thread in case chat instead of CDs or ad-hoc portals.

  • Cloud Connector, Radiology Bridge and Medical API

    Connect DICOM modalities like a second destination printer, autoroute from an existing institute PACS via Radiology Bridge, or integrate via DICOMweb/Medical API. Keeps on-site PACS investments when you only need outbound routing to Unomed practices.

  • Overlay on existing practice software

    Opens studies from the patient record in supported web-based Swiss practice systems without replacing the PIS. Vendor lists 16+ systems with several official partners; desktop-only software needs a feasibility discussion.

Assurance & compliance: Open Telekom Cloud vs Unomed Cloud PACS
Assurance & complianceLogo: Open Telekom CloudOpen Telekom CloudLogo: Unomed Cloud PACSUnomed Cloud PACS
Independent security / no-logs audit
Not applicable

IaaS platform—not a no-logs consumer VPN. Independent assurance is via ISO/SOC/C5-style audits rather than a no-logs report.

Not found

No public independent security audit report located on unomed.ch.

ISO 27001
Vendor claimed

Vendor certifications page links ISO/IEC 27001 umbrella certificate PDF for download; re-verify serial/date in procurement.

Not found

No ISO 27001 certificate or registry entry found on the official site.

ISO/IEC 27017 (cloud security)
Vendor claimed

Claimed with downloadable attestation PDF on certifications page.

Not listed
ISO/IEC 27018 (cloud PII)
Vendor claimed

Claimed with downloadable attestation PDF on certifications page.

Not listed
SOC 2 / SOC 3
Vendor claimed

SOC 2 Type II (request report); SOC 3 public PDF linked on certifications page. SOC 1 Type II also claimed.

Not found

No SOC 2/3 report referenced on public pages reviewed.

BSI C5 Type II
Vendor claimed

Vendor claims BSI C5:2020 Type II (ISAE 3000); detailed report typically on request via audit-reports download flow.

Not listed
TISAX Level 3
Vendor claimed

Vendor states TISAX Level 3 for Germany and Netherlands regions.

Not listed
GDPR / EU data protection
Vendor claimed

EU operator, EU/CH regions, ISO 27018/27701 claims, DPA language on marketing pages—confirm signed DPA for your entity.

Vendor claimed

Swiss FADP (DSG) primary; privacy policy also cites GDPR bases. Confirm DPA/ABV for your use case.

US CLOUD Act exposure (indicative)
Partial

German Telekom/T-Systems operator, no known US parent of the cloud business, primary hosting on Telekom EU/CH data centers (not AWS/GCP/Azure). Not a legal clearance of zero extraterritorial risk. Historical Huawei tech partnership is separate supply-chain diligence. Not legal advice.

Partial

Swiss entity / no known US parent, but AWS (S3 Zurich region, Rekognition Ireland) and Firebase appear in public technical/privacy materials. Not legal advice.

Data processing agreement (B2B)
Vendor claimed

Vendor GDPR pages state DPA, TOMs, and audit reports available for B2B; obtain current signed pack—not fully self-serve public template verified here.

Vendor claimed

GTCs require an Auftragsbearbeitungsvertrag (ABV) when patient data is processed on behalf of the healthcare provider.

EU AI Act
Partial

Platform offers AI services (ModelArts) that may fall under customer AI Act obligations; OTC itself is infrastructure—not an automated high-risk AI system assessment by EuropeanStack.

Not applicable

PACS archive/viewer product; AI is used for assisted patient matching and other suite features, but this entry evaluates the imaging archive, not an AI-centric system.

Diagnostic viewer certificationNot listed
Partial

Default OHIF viewer explicitly not for diagnosis per GTCs; certified third-party viewers optional.

Considerations & known limitations: Open Telekom Cloud vs Unomed Cloud PACS
Considerations & known limitationsLogo: Open Telekom CloudOpen Telekom CloudLogo: Unomed Cloud PACSUnomed Cloud PACS
Historical Huawei technology partnership
Medium

Platform launched with Huawei hardware/software partnership; residual stack components may still matter for sensitive public-sector RFPs. T-Systems states independent operation. Review supply-chain docs under NDA.

Not listed
Service catalog differs by region
Medium

Several services (e.g. ModelArts, bare metal, some database/analytics SKUs) are unavailable in NL or limited to DE. Design against the live regional matrix, not the full marketing list.

Not listed
Limited public subprocessor table
Low

Unlike some SaaS vendors, a complete public subprocessor inventory was not found on marketing pages. Request DPA annex and subcontractor list before high-assurance processing.

Not listed
Smaller global ecosystem than AWS/Azure/GCP
Low

Expect fewer regions, fewer proprietary PaaS services, and a smaller marketplace than US hyperscalers. Migration tools and partner ecosystem exist but differ in depth.

Not listed
Brand transition OTC → T Cloud Public
Low

Documentation, console URLs, and community still mix Open Telekom Cloud and T Cloud Public names. Factor rebrand into runbooks and vendor risk registers.

Not listed
US-group cloud components in the data pathNot listed
Medium

Even with Swiss HQ and claimed Swiss image hosting, AWS and Firebase endpoints appear in public privacy/CSP materials. Procurement should obtain the named subprocessor annex and assess CLOUD Act residual risk.

Default viewer not for diagnosisNot listed
High

If radiologists must report from the included viewer, Unomed alone is the wrong shortlist item unless a certified diagnostic viewer is contracted.

No public ISO/SOC or independent auditNot listed
Medium

Assurance currently rests on vendor policies, Swiss entity status and contractual ABV rather than published certificates.

Subprocessor list not publishedNot listed
Medium

Privacy policy says processors can be requested at any time but does not name hosting vendors on the page. Blockers for security questionnaires until the annex is shared.

Fit

Open Telekom Cloud

Best fit when

  • German public sector and regulated buyers needing Telekom-group operator plus BSI C5 / ISO package
  • Enterprises pinning workloads to DE, NL, or Swiss twin-core regions under GDPR (and Swiss DSG where relevant)
  • Teams wanting OpenStack-based IaaS with ECS, object/block storage, VPC, and Kubernetes (CCE) without US hyperscaler residency defaults
  • AI/ML projects that require GPU capacity and ModelArts-class tooling with European data residency messaging
  • Hybrid architectures using Direct Connect / VPN into Telekom data centers with 24/7 European support expectations

Poor fit when

  • Workloads that require dozens of global regions or deep proprietary hyperscaler PaaS catalogs
  • Buyers seeking a free self-hosted OpenStack distribution rather than a commercial public cloud
  • Teams that need every service in every region—several AI, bare-metal, and data services are DE-only or limited
  • Organisations that reject any non-European technology supply chain without further review (historical Huawei partnership)

Consider instead when

  • When: You need extensive bare-metal catalogs and a very large multi-country EU footprint

    Consider: OVHcloud

    Different operator (France) and product packaging; compare bare-metal and region maps.

  • When: You prefer developer-centric European cloud packaging outside the Telekom stack

    Consider: Scaleway or Exoscale

    Scaleway for FR/NL-oriented developer UX; Exoscale for Swiss multi-zone IaaS + managed K8s.

  • When: You need global regions, marketplace depth, or proprietary PaaS only hyperscalers provide

    Consider: AWS, Microsoft Azure, or Google Cloud Platform

    Accept US-parent CLOUD Act exposure and multi-region complexity in exchange for breadth.

  • When: You want German-market hosting adjacency with a different commercial/product mix

    Consider: IONOS

    Often compared for German buyers; validate IaaS depth vs OTC enterprise cloud features.

Unomed Cloud PACS

Best fit when

  • Swiss medical or dental practices that want cloud DICOM archive and sharing without an on-site PACS project
  • Teams that must open imaging from an existing web-based practice system rather than a second patient search
  • Institutes that need to autoroute studies to referring practices while keeping an existing PACS (Radiology Bridge)
  • Buyers who prioritise a Swiss contracting entity and vendor-claimed Swiss image residency under the FADP
  • Workflows that share studies with referrers or patients via links instead of CDs or one-off portals

Poor fit when

  • Organisations that require the included viewer to be a certified diagnostic/reporting workstation out of the box
  • Buyers that need a published named subprocessor list and independent ISO/SOC evidence before first sales call
  • Teams seeking a fully self-hosted open-source PACS they operate themselves
  • Hospitals needing a full RIS/PACS suite beyond practice-oriented cloud archive and sharing

Consider instead when

  • When: You need a European cloud PACS peer outside Switzerland or broader multi-country packaging

    Consider: PostDICOM (Netherlands) or other EU cloud PACS vendors

    Feature parity is not claimed; compare residency contracts and viewer certification directly.

  • When: You primarily need raw cloud object storage or hospital-grade imaging services on a hyperscaler

    Consider: AWS or Azure health/imaging stacks with your own viewer and compliance design

    More infrastructure flexibility; you own more of the clinical workflow glue.

  • When: You must keep all image data on premises under your sole operational control

    Consider: Classic on-prem PACS plus a dedicated sharing portal

    Unomed is cloud SaaS with a local connector, not a self-hosted Unomed server product.

Open questions for due diligence

Open Telekom Cloud

  • Will T-Systems provide the current full subprocessor/subcontractor list and signed DPA annex for our legal entity and region?
  • What is the residual Huawei (or other non-EU) component inventory for the regions we will use, and is it acceptable under our procurement policy?
  • Which services in our target architecture are available in DE vs NL vs Swiss regions with which SLAs?
  • Can we obtain current C5 Type II and SOC 2 reports (not only marketing claims and SOC 3 summary) under NDA?
  • For AI workloads, which ModelArts/GPU SKUs and data paths apply, and how do they map to our EU AI Act role?

Unomed Cloud PACS

  • Will Unomed provide the current named subprocessor list (hosting, backup, email, SMS, identity) under NDA or in the ABV annex?
  • Which exact Swiss data-centre operators and certifications cover the DICOM archive?
  • Is a CE-marked / certified diagnostic viewer required for your reporting workflow, and which third-party option will Unomed integrate?
  • What SLA, backup/RPO and export support apply to your Cloud PACS tier?