Unomed Cloud PACS vs UpCloud

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

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

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

UpCloud

Finland· Cloud Computing

Needs review

Shortlist UpCloud when you want Finnish-contracted IaaS with MaxIOPS storage, CNCF Managed Kubernetes, managed open-source databases, and customer-pinned EU regions—plus optional global PoPs. Skip when you need hyperscaler-only PaaS depth or the absolute lowest bare-metal VPS pricing; consider Hetzner, Scaleway, or AWS/Azure/GCP depending on that gap.

Finnish-operated IaaSMaxIOPS block storageCNCF Managed KubernetesISO 27001 (claimed)Selectable EU regionsZero-cost egress policy

View listing Visit Website

Highlighted rows differ between the two products.

Unomed Cloud PACS vs UpCloud: Snapshot
Feature	Unomed Cloud PACS	UpCloud
Country of origin	Switzerland	Finland
Category	Cloud Computing	Cloud Computing
Open source	No	No
Self-hosted	No	No
Headquarters	Switzerland	Finland
Legal entity	Unomed AG	UpCloud Oy (Business ID 2431560-5), Aleksanterinkatu 15 B, 00100 Helsinki
Governing law	Not listed	Finland (Terms of Service; arbitration Helsinki)
US parent / control	No known US parent	No known US parent
CLOUD Act exposure (indicative)	Medium	Medium
EU-hosted status	Partial	Not listed
Hosting / residency	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.	Customer-selected regions across 15 DCs (EU majority: FI, SE, NO, DK, DE, NL, ES, PL, UK; plus US-CHI/NYC/SJO, SG, AU) in colocations (Equinix, Digital Realty, CoreSite, Telia, Verne, Green Mountain, etc.). Customer Data stays in chosen DC. Vendor: EU VMs have no customer-data subprocessors; group subsidiaries only otherwise. Account data in Finland with global support access (incl. US/SG). Payments/hCaptcha are separate third parties.
Summary	Swiss cloud PACS and vendor-neutral archive for storing, viewing and sharing DICOM medical images in the browser, integrated with existing medical practice workflows.	Finnish IaaS from UpCloud Oy (Helsinki): MaxIOPS block storage, Cloud Servers, managed Kubernetes and databases across 15 global regions with customer-selected residency.
Tags	pacs dicom medical-imaging healthcare cloud-pacs switzerland vna	cloud iaas infrastructure kubernetes gdpr api finland managed-databases

At a glance: Unomed Cloud PACS vs UpCloud
At a glance	Unomed Cloud PACS	UpCloud
HQ	Zurich, Switzerland	Helsinki, Finland
Legal entity	Unomed AG (CHE-374.858.885)	UpCloud Oy (2431560-5)
Product type	Cloud PACS / VNA SaaS	Not listed
Self-hosted	No (local connector only)	No (public/private cloud IaaS)
Default viewer	OHIF (not for diagnosis per GTCs)	Not listed
Founded	Not listed	2011
Regions	Not listed	15 DCs / 12 countries (EU-heavy + US/APAC)
Open source	Not listed	No (platform proprietary)
Commercial model	Not listed	Hourly pay-as-you-go; trial credits; zero-cost egress policy
Data residency regions	Switzerland claimed for DICOM/hosting; some auxiliary processing in EU (IE/DK) per privacy policy	Not listed

Key capabilities: Unomed Cloud PACS vs UpCloud
Key capabilities	Unomed Cloud PACS	UpCloud
Swiss-operated	Yes	Not listed
Cloud PACS / VNA	Yes	Not listed
DICOM archive	Yes	Not listed
Browser viewer	Yes	Not listed
PIS overlay	Yes	Not listed
Finnish-operated IaaS	Not listed	Yes
MaxIOPS block storage	Not listed	Yes
CNCF Managed Kubernetes	Not listed	Yes
ISO 27001 (claimed)	Not listed	Yes
Selectable EU regions	Not listed	Yes
Zero-cost egress policy	Not listed	Yes

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.

UpCloud

MaxIOPS clustered block storage
In-house all-flash block tier rated up to ~100,000 read IOPS at 4K, separate from compute hosts, with Standard and Archive tiers for capacity. Attach up to 16 devices per server (up to 64 TB total); encryption at rest optional. Suits databases and I/O-heavy apps that outgrow commodity cloud disks.
Cloud Servers on AMD EPYC with automation
Linux/Windows VMs with Starter, Premium, and Cloud Native plan families, hot resize options, firewall, utility and SDN private networking. Full lifecycle via control panel, REST API, CLI, Terraform/OpenTofu, Pulumi, and Crossplane—for teams automating fleets rather than clicking one-off VPS.
CNCF Managed Kubernetes (UKS)
Managed control planes with CNCF-certified Kubernetes versions, autoscaler integration, CSI block volumes, load-balancer integration, and private-only clusters. Worker nodes use ordinary Cloud Server plans including Private Cloud hosts—good fit when you want K8s without running etcd yourself.
Managed PostgreSQL, MySQL, Valkey, OpenSearch
Turnkey databases with automated backups, multi-node HA options, private utility/SDN connectivity, and point-in-time recovery on relational plans. Reduces ops load for product teams that still want open engines rather than proprietary hyperscaler databases.
Customer-selected global regions (EU-first footprint)
Fifteen data centers across twelve countries: dense Northern/Central Europe (Helsinki x2, Stockholm, Stavanger, Copenhagen, Amsterdam, Frankfurt, Madrid, Warsaw, London) plus US, Singapore, and Sydney. Customer Data stays in the chosen zone unless you request a move—use EU zones for residency programmes.
Zero-cost egress packaging and 99.999% SLA line
Public pricing emphasises no per-GB internet egress charges under a Fair Transfer Policy, plus Premium-class 99.999% SLA with service credits for unscheduled downtime. Simplifies bills for chatty APIs and multi-service architectures compared with classic egress meters—confirm fair-use limits for extreme transfer cases.

Assurance & compliance: Unomed Cloud PACS vs UpCloud
Assurance & compliance	Unomed Cloud PACS	UpCloud
Independent security / no-logs audit	Not found No public independent security audit report located on unomed.ch.	Vendor claimed Vendor states cloud services audited against Finnish PiTuKri criteria by an independent firm; ISO 27001 ISMS regularly audited. Public PiTuKri report not fully reproduced on marketing pages—request artefacts.
ISO 27001	Not found No ISO 27001 certificate or registry entry found on the official site.	Vendor claimed Vendor asserts ISO 27001 certified ISMS and publishes certificate PDF; independent registry re-check not completed in this draft.
SOC 2 / SOC 3	Not found No SOC 2/3 report referenced on public pages reviewed.	Not found Facility providers list SOC reports; no clear first-party UpCloud SOC 2 Type II product claim found on compliance pages reviewed.
GDPR / EU data protection	Vendor claimed Swiss FADP (DSG) primary; privacy policy also cites GDPR bases. Confirm DPA/ABV for your use case.	Vendor claimed Finnish controller/processor under GDPR; customer chooses region; DPA in ToS; CISPE Code of Conduct adherence claimed.
US CLOUD Act exposure (indicative)	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.	Partial Finnish entity / no known US parent; EU-region VMs can avoid US storage. Material exceptions: optional US DCs, US/SG support affiliates for account ops, US colocations if selected. Assessment not a vendor safety claim. Not legal advice.
Data processing agreement (B2B)	Vendor claimed GTCs require an Auftragsbearbeitungsvertrag (ABV) when patient data is processed on behalf of the healthcare provider.	Vendor claimed DPA incorporated into Terms of Service; binding on acceptance without separate signature per vendor.
EU AI Act	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.	Not applicable General-purpose IaaS/platform; not an AI system provider by primary product.
Diagnostic viewer certification	Partial Default OHIF viewer explicitly not for diagnosis per GTCs; certified third-party viewers optional.	Not listed
CISPE Code of Conduct	Not listed	Vendor claimed Vendor states adherence to CISPE data protection code for cloud infrastructure providers.

Considerations & known limitations: Unomed Cloud PACS vs UpCloud
Considerations & known limitations	Unomed Cloud PACS	UpCloud
US-group cloud components in the data path	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.	Not listed
Default viewer not for diagnosis	High If radiologists must report from the included viewer, Unomed alone is the wrong shortlist item unless a certified diagnostic viewer is contracted.	Not listed
No public ISO/SOC or independent audit	Medium Assurance currently rests on vendor policies, Swiss entity status and contractual ABV rather than published certificates.	Not listed
Subprocessor list not published	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.	Not listed
Optional non-EU regions and support access	Not listed	Medium US, Singapore, and Sydney zones are first-class options. Mis-pinned workloads or defaults can place Customer Data outside the EU. Account information is accessible to non-EEA support staff even when VMs stay in Europe.
Narrower catalogue than hyperscalers	Not listed	Low Strong IaaS and focused managed services; missing many proprietary AWS/Azure/GCP PaaS and AI products. Multi-cloud or dual-vendor designs may still be required.
Limited public SOC 2 for UpCloud entity	Not listed	Medium ISO 27001 and PiTuKri claims are published; a customer-facing SOC 2 Type II for UpCloud itself was not found. Enterprise questionnaires may need NDA artefacts or reliance on ISO plus facility reports.
Colocation facility dependency	Not listed	Low Platform runs in third-party data centres. Facility certifications differ by site; treat them as complementary to UpCloud’s own ISMS, not a substitute for vendor due diligence.
Fair Transfer Policy on zero egress	Not listed	Low Zero-cost egress is a commercial differentiator but is governed by a Fair Transfer Policy—extreme or abusive transfer patterns may fall outside the marketing promise. Validate for CDN-scale or bulk egress designs.

Fit

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.

UpCloud

Best fit when

EU product teams needing IaaS with Finnish legal entity and pin-to-zone residency
Workloads sensitive to block I/O that benefit from MaxIOPS-class SSDs
Cloud-native stacks on managed Kubernetes plus managed PostgreSQL/MySQL/Valkey
Multi-service apps where predictable outbound transfer packaging matters
Agencies and SaaS operators standardising on API/Terraform automation

Poor fit when

Organisations that require a full hyperscaler catalogue (proprietary AI/PaaS breadth)
Buyers optimising solely for the lowest-cost bare metal or unlimited-traffic VPS
Programmes that forbid any non-EU group support access to account metadata without extra controls
Teams that will deploy only to US regions yet still market the stack as EU-sovereign

Consider instead when

When: You need cheaper raw compute or dedicated servers more than managed K8s packaging
Consider: Hetzner
Often stronger on price for VPS/dedicated; compare managed service depth separately.
When: You want a broader French/EU public-cloud portfolio or different regional SKUs
Consider: OVHcloud or Scaleway
Different product breadth and commercial culture; still European-operated peers.
When: You need hyperscaler-managed platforms, global enterprise contracts, or deep marketplace ecosystems
Consider: AWS, Google Cloud, or Microsoft Azure
Trade European HQ simplicity for catalogue depth and global account teams.
When: You want a compact European cloud with Swiss roots and a tighter region set
Consider: Exoscale
Compare region map and managed feature parity to UpCloud’s 15-DC footprint.

Open questions for due diligence

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?

UpCloud

Obtain current ISO 27001 certificate scope/dates and any PiTuKri or other audit reports under NDA if required.
Confirm DPA Appendix 1 legal names and countries of all group-company subprocessors for your service mix.
Document which regions and backup/object-storage endpoints will be allow-listed for EU-only programmes.
Ask whether a SOC 2 or equivalent report for UpCloud Oy is available for enterprise review.
Validate Fair Transfer Policy thresholds for your expected egress profile.