Hosting & Deployment

Run MediNeura on our cloud, your cloud, or your own hardware

Different organisations carry different obligations around data residency, control and procurement. The platform is identical in all three models — only where it runs changes.

Three deployment models

Shared Cloud · SaaS

Fully managed multi-tenant

The fastest route to production. We run, patch and scale everything; you configure and go live.

  • Fully managed by MediNeura
  • Multi-tenant architecture
  • Rapid deployment timeline
  • Automatic updates and patching
  • Predictable subscription pricing
  • Elastic capacity as you grow
Best fit for
Clinics, single-site hospitals and growing provider groups that want speed over infrastructure control.
Client Dedicated Cloud

Your own isolated environment

A dedicated tenancy in your chosen hyperscaler, isolated from every other customer and sized to your organisation.

  • Deploy on Azure, AWS or Google Cloud
  • Complete customer isolation
  • Enterprise scalability on demand
  • High-availability configuration
  • Disaster recovery and backup strategy
  • Choose your data residency region
Best fit for
Hospital groups and enterprise healthcare networks with data-residency requirements or existing cloud agreements.
On-Premises

Inside your own data centre

Installed and operated entirely within your infrastructure, behind your firewall, under your governance.

  • Installed within client infrastructure
  • Full control over data and access
  • Local database hosting
  • Custom integration with internal systems
  • Supports air-gapped configurations
  • Your team retains operational control
Best fit for
Government health bodies, military hospitals and institutions operating under statutory on-premises mandates.
Side by side

Comparing the three models

The platform capability is the same in every column. What changes is who operates the infrastructure and where the data physically lives.

Consideration Shared Cloud Dedicated Cloud On-Premises
Infrastructure managed byMediNeuraMediNeuraYour IT team
TenancyMulti-tenantSingle tenantSingle tenant
Data residency choiceRegionalRegion of your choiceYour premises
Time to first environmentFastestModerateLongest
Update cadenceAutomaticScheduled with youScheduled with you
Infrastructure cost modelSubscriptionSubscription + cloud spendCapital + licence
Air-gapped operationNot availableNot availableSupported
Custom internal integrationsStandard APIsExtendedFullest scope
Implementation

What happens between signature and go-live

Deployment model changes the infrastructure work, not the clinical preparation. Both run in parallel.

Discovery and design

We map your current systems, workflows and data, then agree the target configuration and integration scope in writing.

Environment provisioning

Infrastructure is built in your chosen model, with connectivity, identity and security controls configured to your standards.

Data migration

Historical records are extracted, mapped, validated and loaded. Reconciliation reports are produced for your team to sign off.

Integration build

Interfaces to laboratory, imaging, finance and identity systems are built and tested against your live environment.

Training and readiness

Role-based training for clinical and administrative staff, with super-users identified and prepared to support their colleagues.

Go-live and stabilisation

Cutover with on-site or remote support, followed by a defined stabilisation period before transition to standard support.

Talk through which model fits your governance

Bring your IT, security and procurement leads. We will work through data residency, integration scope and the operational split in detail.