Cyso Cloud
Netherlands· Cloud Computing
Cyso Cloud vs Unomed Cloud PACS
Compare Cyso Cloud y Unomed Cloud PACS en capacidades, jurisdicción, garantías y encaje para compradores europeos.
Ambos figuran como alternativas a: 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
Las filas resaltadas diferencian a los dos productos.
| Característica | Cyso Cloud | Unomed Cloud PACS |
|---|---|---|
| País de origen | Netherlands | Switzerland |
| Categoría | Cloud Computing | Cloud Computing |
| Código abierto | Sí | No |
| Autoalojado | No | No |
| Sede | No indicado | Switzerland |
| Entidad legal | No indicado | Unomed AG |
| Matriz / control EE.UU. | No indicado | Sin matriz estadounidense conocida |
| Exposición CLOUD Act (indicativa) | No indicado | Medio |
| Estado de alojamiento en la UE | No indicado | Parcial |
| Alojamiento / residencia | No indicado | 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. |
| Resumen | Dutch OpenStack IaaS from Cyso B.V. with AMS/FRA regions, managed Kubernetes (KCSP), S3-compatible object storage, and EU data residency for teams avoiding hyperscaler lock-in. | Swiss cloud PACS and vendor-neutral archive for storing, viewing and sharing DICOM medical images in the browser, integrated with existing medical practice workflows. |
| Etiquetas |
| De un vistazo | Cyso Cloud | Unomed Cloud PACS |
|---|---|---|
| HQ | No indicado | Zurich, Switzerland |
| Legal entity | No indicado | Unomed AG (CHE-374.858.885) |
| Product type | No indicado | Cloud PACS / VNA SaaS |
| Self-hosted | No indicado | No (local connector only) |
| Default viewer | No indicado | OHIF (not for diagnosis per GTCs) |
| Data residency regions | No indicado | Switzerland claimed for DICOM/hosting; some auxiliary processing in EU (IE/DK) per privacy policy |
| Key capabilities | Cyso Cloud | Unomed Cloud PACS |
|---|---|---|
| Swiss-operated | No indicado | Sí |
| Cloud PACS / VNA | No indicado | Sí |
| DICOM archive | No indicado | Sí |
| Browser viewer | No indicado | Sí |
| PIS overlay | No indicado | Sí |
Cyso Cloud
Instancias de compute escalables
Las instancias se lanzan en segundos con flavors adaptados a cargas de trabajo: estándar (equilibrado), optimizado para CPU (hasta 64 vCPUs) u optimizado para memoria (hasta 512 GB RAM). El almacenamiento efímero se vincula al ciclo de vida de la instancia; los volúmenes persistentes ofrecen triple replicación y escalado de IOPS (5-25 por GB). Las tarifas por hora empiezan en 0,026 € para especificaciones de entrada, permitiendo ajuste preciso de costes sin sobreaprovisionamiento.
Object storage compatible con S3
Diseñado para copias de seguridad y grandes conjuntos de datos, este servicio ofrece capacidad ilimitada con SLA de disponibilidad del 99,99 %. Las unidades NVMe garantizan baja latencia; los datos permanecen en regiones de la UE seleccionadas. Precios: 0,055 €/GB almacenamiento, entrada gratuita, 0,055 €/GB salida. Las operaciones cuestan 0,055 € por 10.000 solicitudes PUT/LIST, soportando acceso REST API para integración fluida.
Kubernetes gestionado
Enterprise Managed Kubernetes (EMK) incluye un plano de control a 29,99 € mensuales (HA a 59,99 €), con actualizaciones automatizadas e hibernación para ahorro de costes. El SLA del 99,9 % cubre clústeres de alta disponibilidad. Los usuarios despliegan vía panel; funciones como autoscaling gestionan cargas variables. La documentación guía la configuración en minutos.
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 | Cyso Cloud | Unomed Cloud PACS |
|---|---|---|
| Independent security / no-logs audit | No indicado | Not found No public independent security audit report located on unomed.ch. |
| ISO 27001 | No indicado | Not found No ISO 27001 certificate or registry entry found on the official site. |
| SOC 2 / SOC 3 | No indicado | Not found No SOC 2/3 report referenced on public pages reviewed. |
| GDPR / EU data protection | No indicado | Vendor claimed Swiss FADP (DSG) primary; privacy policy also cites GDPR bases. Confirm DPA/ABV for your use case. |
| US CLOUD Act exposure (indicative) | No indicado | 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) | No indicado | Vendor claimed GTCs require an Auftragsbearbeitungsvertrag (ABV) when patient data is processed on behalf of the healthcare provider. |
| EU AI Act | No indicado | 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 certification | No indicado | Partial Default OHIF viewer explicitly not for diagnosis per GTCs; certified third-party viewers optional. |
| Considerations & known limitations | Cyso Cloud | Unomed Cloud PACS |
|---|---|---|
| US-group cloud components in the data path | No indicado | 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 | No indicado | 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 | No indicado | Medium Assurance currently rests on vendor policies, Swiss entity status and contractual ABV rather than published certificates. |
| Subprocessor list not published | No indicado | 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. |
Encaje
Cyso Cloud
Best fit when
No indicado
Poor fit when
No indicado
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
Cyso Cloud
No indicado
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?