Skip to content
LocumView

Deploy

Your infrastructure, your choice.

Your OS is a parameter, not a rewrite. LocumView is being built from code so that the operating system and the infrastructure underneath it become configuration choices. Today it runs on Red Hat Enterprise Linux; the other targets below are planned.
Why the choice matters

Data sovereignty starts with who controls the stack.

Clinical data is only as sovereign as the software and infrastructure it runs on. Because LocumView builds on open, auditable Linux and deploys wherever you decide, jurisdiction over patient data stays with your organization, not with a vendor.

  • You choose the jurisdiction

    Data residency is decided by where you deploy: your data center, your cloud account, or a sovereign provider.

  • No single-vendor dependency

    Open, enterprise-supported distributions mean no proprietary OS license or foreign platform holds the keys.

  • Auditable end to end

    Open source operating systems and code-defined builds let your security team inspect exactly what runs.

Supported operating systems

  1. Red HatDemonstrated

    Red Hat Enterprise Linux

    The reference build. The live demo runs here today; STIG hardening profiles are being applied next.

  2. openSUSEPlanned

    SUSE Linux Enterprise · openSUSE

    European-rooted enterprise Linux and a natural fit for sovereignty-focused deployments. Not built yet; the goal is the same code with equivalent hardening.

  3. DebianPlanned

    Debian

    Community-governed and vendor-neutral. Intended to build from the same definitions; not built yet, and validation will follow customer need.

EUFor European health systems

Sovereign by design. Your data stays where it belongs.

Digital sovereignty and data residency are now part of healthcare procurement. LocumView runs on open, enterprise Linux and is designed to deploy on European-owned infrastructure, with no dependency on a single US hyperscaler.

  • Planned: deployment on European-owned clouds such as IONOS, STACKIT, OVHcloud, Scaleway, and Hetzner
  • Planned: SUSE Linux Enterprise and other European-supported distributions
  • Data residency controlled by where you deploy, not by a vendor contract
  • Supports the move toward sovereign, open infrastructure in public healthcare

Infrastructure targets

  • On-premises virtualization

    Demonstrated on KVM/libvirt; designed for the hypervisors and hardware already in your data center.

  • Kubernetes

    Live: the access layer (Guacamole, Keycloak, and the tunnel) runs on k3s. Planned: desktops on Kubernetes with KubeVirt.

  • Public or sovereign cloud

    Planned: the cloud your governance allows, with the same images and controls.

  • Thin-client ready

    Because desktops are delivered through the browser, endpoints stay simple: any modern browser works, including on phones. Managed thin clients such as IGEL OS devices should work the same way but have not been tested yet.

How it ships

Same code, any target.

Planned: one set of definitions producing images for each supported OS and infrastructure target.

  1. Define once

    Desktop profiles, packages, and hardening live in one repository.

  2. Choose the OS

    The target distribution is a build parameter, with its matching hardening profile.

  3. Build and scan

    Each image is built in a pipeline and scanned with OpenSCAP before release.

  4. Deploy to target

    The signed image runs on-premises, on Kubernetes, or in your chosen cloud.