Solutions / Cloud Solutions

Cloud Solutions

Hosting, migration and infrastructure for healthcare software — including AI that runs on machines you control.

Healthcare hosting has one constraint most hosting does not: you have to be able to say where the data is and who could reach it. We deploy and migrate healthcare software on AWS and Azure with that as the starting question — including running AI inference on our own GPUs, so a de-identified record does not have to be sent to a third-party model provider to be useful.

How the AI works

  1. 01

    Migrate without a dark weekend

    Systems move in stages with the old one still running, verified against record counts, and cut over only once the new one has been proven on real data.

  2. 02

    Assume a failure will happen

    Backups that have actually been restored in a test, not backups that have only ever been written. An untested backup is a belief, not a recovery plan.

  3. 03

    Keep the AI in your perimeter

    We run our own inference on our own GPUs. Where a workload needs a model, it can stay inside infrastructure you control rather than being posted to an external provider.

Humans in the loop. By architecture.

Encryption in transit and at rest, access logging, and least-privilege roles are set up at the start rather than added during a security review. A signed BAA with the cloud provider is part of the setup, not an afterthought.

Questions, answered

AWS or Azure?+

Both sign BAAs and both are fine for healthcare. The deciding factor is usually what you already run and what your team already knows, not a technical difference between them.

Can we run AI without sending patient data to OpenAI or Google?+

Yes, and we do it ourselves. GetMax runs its own models on its own GPUs, which is why the tools on this site can process a document without it going to an external model provider. The same architecture can be deployed for you.

We are on an ageing on-premise server. Is moving worth it?+

Often, but not always. An on-premise server that is backed up, patched and running fine is not an emergency. The honest triggers are hardware nearing end of life, a backup that has never been restored, or needing access from outside the building.

How is this sized for us?+

It depends on data volume and uptime requirements, and we would rather size it against your actual numbers than put a figure here that turns out to be wrong in either direction.