SOLHEA

DEPLOYMENT MODELS

One product. An agreed operating model.

The Java backend, PostgreSQL and Staff/Patient frontends are separate. Choosing an environment includes security, responsibilities and service levels.

Request a demo ↗

01 / SOLHEA

SOLHEA SaaS

The reference model is a managed service. Updates, maintenance and operational responsibilities are defined contractually. Real use remains subject to pilot gates, acceptance testing and agreements.

02 / SOLHEA

Dedicated cloud

A specific environment can be sized with the customer: network, data location, integrations, capacity, costs and responsibilities. No universal, already available configuration is promised.

03 / SOLHEA

Customer or third-party servers

Installation on customer-designated infrastructure is a post-V1 project possibility. It requires feasibility analysis, implementation, hardening and acceptance testing. It is not an already certified on-premise product.

04 / SOLHEA

Operating conditions are part of the project

Each scenario requires agreement on domains, certificates, access, patching, monitoring, backup/restore, incident handling and disaster recovery. RPO/RTO, availability and maintenance cannot be inferred from containerization alone.

Let’s build your first Journey together.

Tell us how you coordinate journeys today. We start with people, steps and responsibilities, for a demonstration that reflects your organization.

Request a demo ↗