Easypanel vs Unomed Cloud PACS

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

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

Logo: Easypanel

Easypanel

Romania· Cloud Computing

Needs review

Shortlist when you want a polished, proprietary self-hosted PaaS panel with Git builders, automatic HTTPS, databases, backups, and a large template catalogue on servers you control. Skip when you need a managed cloud runtime SLA, or when procurement requires an open-source control plane (consider Coolify or CapRover) or pure EU IaaS without a commercial panel (Hetzner or Scaleway alone).

EU-operatedSelf-hostedProprietaryDocker PaaS panelGit deploy
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
Easypanel vs Unomed Cloud PACS: Snapshot
FeatureLogo: EasypanelEasypanelLogo: Unomed Cloud PACSUnomed Cloud PACS
Country of originRomaniaSwitzerland
CategoryCloud ComputingCloud Computing
Open sourceNoNo
Self-hostedYesNo
HeadquartersRomaniaSwitzerland
Legal entityCanta Andrei PFA (CUI RO52148795)Unomed AG
US parent / controlNo known US parentNo known US parent
CLOUD Act exposure (indicative)MediumMedium
EU-hosted statusPartialPartial
Hosting / residencyApplication workloads and panel data on customer-controlled servers. Vendor account/license billing via Lemon Squeezy (US merchant of record). Public website uses Google for sign-in and optional analytics; DNS on Cloudflare.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

Self-hosted deployment platform for apps, databases, Docker images and Docker Compose projects, with automatic SSL, backups and monitoring.

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: Easypanel vs Unomed Cloud PACS
At a glanceLogo: EasypanelEasypanelLogo: Unomed Cloud PACSUnomed Cloud PACS
HQ / entityRomania (Canta Andrei PFA)Not listed
Product modelSelf-hosted proprietary panelNot listed
RuntimeDocker on your serverNot listed
License meteringPer server (free tier available)Not listed
Merchant of recordLemon SqueezyNot 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)
Workload regionsCustomer-chosen server or VPS regionNot listed
Compliance certs (vendor)No public ISO/SOC cert pages foundNot listed
Data residency regionsNot listedSwitzerland claimed for DICOM/hosting; some auxiliary processing in EU (IE/DK) per privacy policy
Key capabilities: Easypanel vs Unomed Cloud PACS
Key capabilitiesLogo: EasypanelEasypanelLogo: Unomed Cloud PACSUnomed Cloud PACS
EU-operatedYesYes
Self-hostedYesNot listed
ProprietaryYesNot listed
Docker PaaS panelYesNot listed
Git deployYesNot listed
Cloud PACS / VNANot listedYes
DICOM archiveNot listedYes
Browser viewerNot listedYes
PIS overlayNot listedYes

Easypanel

  • Git, image, and Compose deploys with multiple builders

    Connect GitHub or generic Git, upload archives, pull Docker images, or run Compose projects. Build with Dockerfile, Cloud Native Buildpacks, Nixpacks, or Railpack. Auto-deploy webhooks are available for GitHub sources. Limit: you still operate the underlying server and must keep ports 80/443 free on a typical install.

  • Automatic HTTPS domains and Traefik routing

    Attach hostnames to services, terminate TLS, and apply proxy middlewares from the dashboard. Useful for teams that want certificate renewal and routing without hand-editing reverse-proxy files. Limit: DNS and server firewall remain your responsibility.

  • Managed databases plus scheduled backups

    Run Postgres, MySQL, MongoDB, and Redis as services beside apps. Schedule database and volume backups to local disk, FTP/SFTP, S3-compatible storage, Dropbox, or Google Drive, then restore from the UI. Limit: a local-only backup destination does not protect against full server loss.

  • Large one-click application template catalogue

    Install maintained templates for hundreds of open-source apps (vendor states 750+) such as n8n, Supabase, WordPress, Immich, and Nextcloud, with service wiring handled by the panel. Limit: each upstream app still needs its own hardening, upgrades, and credential hygiene.

  • In-browser operations: metrics, logs, and shell

    Monitor CPU, memory, disk, and network, stream logs, and open a container shell or saved scripts without separate SSH tooling for routine tasks. Limit: deep incident response still needs host-level access and your own observability stack for production SLAs.

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: Easypanel vs Unomed Cloud PACS
Assurance & complianceLogo: EasypanelEasypanelLogo: Unomed Cloud PACSUnomed Cloud PACS
Independent security / no-logs audit
Not found

No public third-party audit PDF located on primary site.

Not found

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

ISO 27001
Not found
Not found

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

SOC 2 / SOC 3
Not found
Not found

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

GDPR / EU data protection
Vendor claimed

Romanian (EU) PFA entity and public Privacy Policy; confirm processing roles for your account data.

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

EU operator with no known US parent, but Lemon Squeezy (billing) and Google (website sign-in/analytics) are US-linked. Customer app data stays on the customer server unless backups are sent to US-group storage. 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)
Not found

No public DPA download found on marketing/docs pages during research.

Vendor claimed

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

EU AI Act
Not applicable

Deployment panel, not an AI system product.

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: Easypanel vs Unomed Cloud PACS
Considerations & known limitationsLogo: EasypanelEasypanelLogo: Unomed Cloud PACSUnomed Cloud PACS
Proprietary control plane
Medium

You cannot fork the panel under an OSI license. Budget for license renewals and an exit plan (Compose/export) if requirements change.

Not listed
You operate the server
Medium

Availability, OS patching, capacity, and firewall rules remain yours. This is not a managed PaaS SLA.

Not listed
US-linked account subprocessors
Medium

Lemon Squeezy handles checkout/licenses; Google appears on the website for sign-in/analytics. App data can stay local, but identity and billing metadata do not.

Not listed
Backup targets can leave your host
Low

Optional backup providers include S3-compatible services, Dropbox, and Google Drive. Choose EU-controlled destinations if residency of backups matters.

Not listed
No public independent audit package
Medium

No ISO/SOC or public penetration-test report was found. Enterprise procurement may need questionnaires and contractual security exhibits.

Medium

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

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.

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

Easypanel

Best fit when

  • Developers and small teams deploying apps and open-source stacks on their own VPS
  • Organisations that need workload and database data to remain on designated servers
  • Teams that want Heroku-style builders without a managed PaaS bill per dyno
  • Agencies standardising one-click templates (WordPress, n8n, Supabase, and similar) beside custom apps

Poor fit when

  • Buyers who need the vendor to operate the runtime under a managed PaaS SLA
  • Teams that require a fully open-source control plane they can fork and audit
  • Environments that forbid US-linked billing or analytics subprocessors for accounts (Lemon Squeezy, Google on the website)
  • Large multi-cluster Kubernetes platforms that need CNCF-native GitOps rather than a single-server panel

Consider instead when

  • When: You want an open-source self-hosted PaaS panel you can fork

    Consider: Coolify or CapRover

    Not currently separate EuropeanStack entries; evaluate licenses and multi-server features directly.

  • When: You want managed cloud app hosting instead of operating a VPS

    Consider: DigitalOcean App Platform or AWS application hosting

    Less server ops, less direct control of the host.

  • When: You only need EU IaaS and will run raw Docker or Kubernetes yourself

    Consider: Hetzner or Scaleway

    Complementary as places to install Easypanel, or alternatives if you reject a commercial panel.

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

Easypanel

  • Will the vendor sign a B2B DPA and publish a formal subprocessor list for account/billing systems?
  • Which governing law and venue apply to the Terms (the published Terms do not name Romania explicitly)?
  • Is there an enterprise security pack (pen test summary, questionnaire) available under NDA?
  • What is the supported multi-server / multi-node maturity path for larger fleets?

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?