OVHcloud vs Unomed Cloud PACS

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

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

OVHcloud

France· Cloud Computing

Needs review

Shortlist OVHcloud when you need a European-owned IaaS/bare-metal stack with SecNumCloud/HDS options and multi-continent regions you control per project. Skip when you need hyperscaler platform depth, or when even optional US subsidiaries/regions are a procurement red line—consider Scaleway for leaner French cloud or Hetzner for simpler dedicated/VPS estates.

EU-operated (global regions)Bare Metal + Public CloudOpenStack Public CloudSecNumCloud Private CloudAnti-DDoS includedEU / US / CA / APAC

View listing Visit Website

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

View listing Visit Website

Highlighted rows differ between the two products.

OVHcloud vs Unomed Cloud PACS: Snapshot
Feature	OVHcloud	Unomed Cloud PACS
Country of origin	France	Switzerland
Category	Cloud Computing	Cloud Computing
Open source	No	No
Self-hosted	No	No
Headquarters	France	Switzerland
Legal entity	OVH SAS / OVH Groupe (Roubaix); regional entities include OVH US LLC for US services	Unomed AG
Governing law	French/EU law for EU contracts; US terms apply for OVH US LLC-contracted services	Not listed
US parent / control	No known US parent	No known US parent
CLOUD Act exposure (indicative)	Medium	Medium
EU-hosted status	Not listed	Partial
Hosting / residency	Own global infrastructure: EU regions (FR including Paris 3-AZ, DE Limburg, PL Warsaw, UK Erith, IT Milan 3-AZ, many Local Zones); US (Vint Hill VA, Hillsboro OR); Canada (Beauharnois, Toronto); APAC (Singapore, Sydney, Mumbai). Primary hosting is OVH-operated, not AWS/GCP resale. Optional non-EU regions are first-class products.	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	French cloud and infrastructure group (Roubaix): Bare Metal dedicated servers, OpenStack Public Cloud, Hosted Private Cloud (incl. SecNumCloud), and Web Cloud on OVH-operated datacentres across Europe, North America, and Asia-Pacific.	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	cloud infrastructure bare-metal openstack gdpr secnumcloud european-cloud api	pacs dicom medical-imaging healthcare cloud-pacs switzerland vna

At a glance: OVHcloud vs Unomed Cloud PACS
At a glance	OVHcloud	Unomed Cloud PACS
HQ	Roubaix, France (OVH SAS / OVH Groupe)	Zurich, Switzerland
Founded	1999 (Octave Klaba)	Not listed
Hosting model	Own datacentres and network; multi-region IaaS/bare metal	Not listed
Open source product?	No (OpenStack-based public cloud uses open APIs)	Not listed
Commercial model	Hourly/monthly public cloud; dedicated server subscriptions; free public cloud trial credits (vendor)	Not listed
Notable certs (claimed)	ISO 27001 family, SOC 1/2/3, HDS, SecNumCloud (Private Cloud), PCI DSS	Not listed
Legal entity	Not listed	Unomed AG (CHE-374.858.885)
Product type	Not listed	Cloud PACS / VNA SaaS
Self-hosted	Not listed	No (local connector only)
Default viewer	Not listed	OHIF (not for diagnosis per GTCs)
Data residency regions	Not listed	Switzerland claimed for DICOM/hosting; some auxiliary processing in EU (IE/DK) per privacy policy

Key capabilities: OVHcloud vs Unomed Cloud PACS
Key capabilities	OVHcloud	Unomed Cloud PACS
EU-operated (global regions)	Yes	Yes
Bare Metal + Public Cloud	Yes	Not listed
OpenStack Public Cloud	Yes	Not listed
SecNumCloud Private Cloud	Yes	Not listed
Anti-DDoS included	Yes	Not listed
EU / US / CA / APAC	Yes	Not listed
Cloud PACS / VNA	Not listed	Yes
DICOM archive	Not listed	Yes
Browser viewer	Not listed	Yes
PIS overlay	Not listed	Yes

OVHcloud

Bare Metal dedicated servers (in-house hardware)
Physical servers assembled and operated by OVHcloud across ranges such as Advance, Scale, High Grade, and Game—full CPU/RAM/storage without a hypervisor layer. Water cooling and hardware lifecycle are part of the industrial model. Best for performance-sensitive, virtualisation, gaming, or large single-tenant workloads where you administer the OS.
OpenStack Public Cloud and managed PaaS
On-demand compute, multi-class object storage (S3-compatible API), block/file storage, managed databases, Kubernetes/container services, networking, and data/AI platforms. Deploy via Control Panel or OpenStack APIs with 1-AZ or 3-AZ region options (for example Paris and Milan). Suited to cloud-native and hybrid automation without US hyperscaler lock-in.
Hosted Private Cloud with SecNumCloud path
VMware-based Hosted Private Cloud (and related stacks) for dedicated virtualisation estates. Selected Private Cloud offerings hold French ANSSI SecNumCloud qualification, with customer data under European regulation and hosting in French sites (Roubaix, Gravelines, Strasbourg)—relevant for French public sector and sensitive workloads under Cloud at the Center doctrine.
Global multi-region footprint (EU, US, CA, APAC)
Own datacentres and regions spanning Europe (France, Germany, Poland, UK, Italy, many Local Zones), North America (Vint Hill VA, Hillsboro OR, Beauharnois and Toronto in Canada), and Asia-Pacific (Singapore, Sydney, Mumbai and related offerings). Choose residency for latency and law; do not assume EU-only by default.
Anti-DDoS and vRack private networking included
Network-integrated anti-DDoS mitigation is standard across services. vRack provides private L2 networking across eligible OVHcloud locations so bare metal, public, and private cloud can interconnect without public exposure. Public bandwidth is typically unmetered in Europe and North America with fair-use rules; Asia-Pacific often uses lower default bandwidth and monthly traffic caps—verify per SKU.

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: OVHcloud vs Unomed Cloud PACS
Assurance & compliance	OVHcloud	Unomed Cloud PACS
Independent security / no-logs audit	Not applicable IaaS/hosting provider, not a no-logs VPN product. Security is covered via ISO/SOC programme rather than a public no-logs audit.	Not found No public independent security audit report located on unomed.ch.
ISO 27001	Vendor claimed Vendor compliance pages assert ISO/IEC 27001 (with 27017/27018) for cloud services and datacentres; US pages reference Schellman certificate directory. Confirm current scope per product and region.	Not found No ISO 27001 certificate or registry entry found on the official site.
SOC 2 / SOC 3	Vendor claimed Vendor asserts SSAE 18 Type 2 SOC 1, SOC 2 (+NIST), and SOC 3 attestations; reports available to prospective customers under vendor process.	Not found No SOC 2/3 report referenced on public pages reviewed.
GDPR / EU data protection	Vendor claimed EU headquartered; GDPR compliance asserted; DPA documents published for relevant subsidiaries. Residency depends on chosen region.	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 French group with no known US parent, but operates US datacentres (Vint Hill, Hillsboro) and OVH US LLC. Medium indicative exposure: EU-region workloads on EU contracts differ from US-region workloads. 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 Published DPAs form part of terms (e.g. OVH SAS Europe paths; separate US DPA for OVH US LLC). Obtain the DPA matching your contracting entity.	Vendor claimed GTCs require an Auftragsbearbeitungsvertrag (ABV) when patient data is processed on behalf of the healthcare provider.
EU AI Act	Not applicable Core product is IaaS/bare metal/hosting; AI/ML platforms are optional infrastructure offerings, not a single AI system product under typical procurement framing.	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.
ANSSI SecNumCloud	Vendor claimed Hosted Private Cloud (VMware on OVHcloud and related) holds SecNumCloud qualification; hosted in French sites (Roubaix, Gravelines, Strasbourg). Not all products are SecNumCloud-qualified.	Not listed
HDS (French health data hosting)	Vendor claimed Vendor lists HDS certification for healthcare data hosting options; confirm which products and locations are in scope.	Not listed
PCI DSS	Vendor claimed Vendor asserts PCI DSS Level 1 certification for payment data hosting—confirm applicability to your architecture.	Not listed
Diagnostic viewer certification	Not listed	Partial Default OHIF viewer explicitly not for diagnosis per GTCs; certified third-party viewers optional.

Considerations & known limitations: OVHcloud vs Unomed Cloud PACS
Considerations & known limitations	OVHcloud	Unomed Cloud PACS
US regions and US subsidiary	Medium US East/West datacentres and OVH US LLC mean CLOUD Act and US process risk apply to US-placed data and some contracts. EU-only deployment reduces this but buyers must enforce region and contracting path.	Not listed
2021 Strasbourg datacentre fire (resilience history)	Medium A major fire at SBG caused widespread customer outages. Treat multi-AZ/multi-region backup design as mandatory for critical data; do not rely on single-site assumptions.	Not listed
Certification scope is product- and region-specific	Medium ISO, SOC, HDS, SecNumCloud, and PCI claims do not automatically cover every SKU and location. Procurement should request the exact report for the services ordered.	Not listed
APAC bandwidth and traffic rules differ	Low Vendor documents unmetered traffic exceptions for Asia-Pacific (lower default bandwidth and monthly volume caps vs Europe/North America). Model egress and bandwidth options for APAC workloads.	Not listed
Broad catalogue complexity	Low Bare Metal, Public Cloud, Private Cloud, and Web Cloud under one brand can confuse account structure, IAM, and billing. Define landing-zone standards early.	Not listed
US-group cloud components in the data path	Not 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 diagnosis	Not 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 audit	Not listed	Medium Assurance currently rests on vendor policies, Swiss entity status and contractual ABV rather than published certificates.
Subprocessor list not published	Not 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

OVHcloud

Best fit when

Teams wanting European ownership with optional global regions (EU, US, Canada, APAC) under one operator
Workloads that need exclusive Bare Metal performance or hybrid bare metal + OpenStack/vRack designs
French public sector or sensitive estates needing ANSSI SecNumCloud-qualified Hosted Private Cloud paths
Organisations standardising on OpenStack APIs and S3-compatible object storage for reversibility
Sites that benefit from network-integrated anti-DDoS and private multi-site networking as defaults

Poor fit when

Buyers who require the deepest managed AI/marketplace/IAM ecosystems of AWS, Azure, or GCP
Policies that forbid any provider with US legal entities or US datacentre options regardless of region selection
Teams seeking the simplest low-SKU VPS experience—Hetzner or similar may fit better
Anyone assuming EU-only residency without selecting and enforcing EU regions in architecture

Consider instead when

When: You want a leaner French public cloud with a strong developer product surface and less enterprise sovereign packaging
Consider: Scaleway
Often simpler for cloud-native teams; confirm region and compliance fit.
When: You primarily need price-performance VPS or dedicated servers with a smaller catalogue
Consider: Hetzner
Strong for lean estates; different sovereign/cert posture and global region set.
When: You need maximum managed-service breadth, global account tooling, and partner marketplace density
Consider: Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform
Hyperscalers win platform depth; accept US ownership and CLOUD Act parent exposure.
When: You want German SMB hosting plus cloud IaaS with EU and some non-EU options
Consider: IONOS
Different product mix and compliance packaging than OVHcloud's bare-metal industrial model.

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

OVHcloud

Which contracting entity and DPA (EU OVH SAS path vs OVH US LLC) will apply to our account?
Which exact products/regions are in scope for the ISO/SOC/HDS/SecNumCloud certificates we need?
What is our multi-region DR design given historical single-site fire risk?
Are any non-OVH subprocessors used for our specific managed services (support, monitoring, payments) beyond OVH-operated infrastructure?
Do APAC or Local Zone bandwidth/SLA terms meet our traffic profile?

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?