ASAS HV · Use cases

ASAS HV deployment scenarios

How enterprise virtualization on ASAS HV is designed to be deployed across public-sector and regulated organisations.

Illustrative deployment scenario. These pages describe how VirtuWa is designed to be deployed for this type of organisation — they are not customer references and contain no named customers, quotes or measured customer results.

Scenarios

Where ASAS HV fits

Government entity

Consolidating a ministry data centre onto open foundations

A government entity runs internal services on ageing proprietary virtualization with renewal terms it no longer controls.

Requirements

Workloads and data must stay in national facilities
Licensing exposure at every renewal cycle
Operations team trained on classic hypervisor workflows

How VirtuWa is applied

ASAS HV clusters on KVM/QEMU using standard x86 servers
Central operation through Lejam Cloud Manager
Arabic-first operational interface for day-to-day teams

Operational outcomes to validate

Infrastructure control stays with the entity
Predictable cost model without per-socket lock-in
Familiar VM lifecycle for existing operators

Financial services

Core and non-core workloads on a controlled hypervisor estate

A regulated financial institution separates core banking from supporting workloads and needs auditable infrastructure control.

Requirements

Documented control over where workloads run
High availability for business hours and batch windows
Clear separation between environments

How VirtuWa is applied

Clustered ASAS HV hosts with HA and live migration
Role-based access and audit visibility from Lejam
Separate clusters per environment tier

Operational outcomes to validate

Verifiable workload placement
Planned maintenance without service windows
Consistent operations across environments

Industrial / utilities

Edge and plant-site virtualization with limited connectivity

An industrial operator runs plant-side applications where connectivity to central sites is intermittent.

Requirements

Local operation must continue when links drop
Small hardware footprint at each site
Remote teams with limited on-site staff

How VirtuWa is applied

Compact ASAS HV clusters per site
Central visibility when connectivity is available
Repeatable site builds through Mehad automation

Operational outcomes to validate

Local autonomy during disconnection
Standardised site configuration
Lower per-site operational overhead

Validation

What to validate in a POC

VM lifecycle, snapshots and templates on your own images
High availability behaviour under host failure
Live migration during planned maintenance
Performance against your representative workload profile
Arabic and English operations with your team

FAQ

Questions about this scenario

No. They are illustrative deployment scenarios describing how ASAS HV is designed to be used. We publish customer references only with the customer's approval.

ASAS HV

Enterprise virtualization platform

Validate ASAS HV in your own environment

Run a structured POC against your workloads instead of relying on published stories.

Request a POC Talk to an engineer