Backups that prove themselves.

Policy-based backup across VMs, databases and files — immutable copies, scheduled restore tests, retention mapped to your compliance calendar.

Immutable copiesRestore-testedPolicy-based

Talk to us All Resilience

Capabilities

Protection you can show the auditor

Policy-based

Workloads inherit backup policy by tier — nothing forgotten by omission.

Set once, applied estate-wide

Immutable copies

Ransomware-safe, WORM-locked recovery points.

Ransomware cannot rewrite history

Restore testsScheduled restores verify recoverability — green ticks aren't evidence.Proven, not presumed

Compliance retentionRetention schedules mapped to regulatory requirements.Regulator-ready schedules

VM, database & file coverageOne service protects VMs, managed databases and file shares under the same policies.One protection standard

Application-consistentQuiesced, application-aware copies for databases and transactional systems.Restores that boot

Cross-zone copiesBackup data can replicate to a second sovereign zone for site-level events.Survives more than a disk

Self-service restoreTeams restore files and VMs inside their own scope — no ticket for routine recoveries.Minutes, not queues

Encrypted end to endCopies are encrypted in flight and at rest with keys separated from production.Blast radius contained

Reporting & evidenceSuccess rates, restore times and policy coverage reported monthly.Answers before audits

Compare the policies

Standard, immutable, or long-retention

Every policy is verified by restore testing — the difference is how hard the copies are to destroy and how long they live.

ProductionEdgeComing soon

POLICY 01Start here

Standard Protection

Daily, tested

Policy-based backup across VMs, databases and object buckets with scheduled restore tests — protection that has been proven, not assumed.

Best for

Whole-estate protectionDatabase backupsFile share protection

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiSingaporeAbu DhabiMilanFrankfurtNairobi

Plans

StandardDaily backup · 30-day retention · restore testsSign in →Standard PlusMultiple daily points · 90-day retentionSign in →CustomAny schedule, retention and test cadenceSign in →

POLICY 02

Immutable Vault

Ransomware cannot rewrite it

Write-once copies in a separate vault with dual-control deletion — the copy that survives an attacker with your admin credentials.

Best for

Ransomware resilienceRegulated workloadsCrown-jewel systems

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

ImmutableWORM copies · dual-control releaseSign in →Immutable PlusWORM · second-zone copy · air-gapped scheduleSign in →CustomAny immutability window and approval chainSign in →

POLICY 03

Long Retention

Years, not weeks

Retention measured in years, tiered into Archive Storage so compliance obligations do not sit on expensive capacity.

Best for

Regulatory retentionLegal holdHistorical records

Where it runs

Dubai AZ1Dubai AZ2RiyadhBahrainMumbaiAbu DhabiFrankfurtNairobi

Plans

Long7-year retention · archive tieringSign in →Long Plus10-year retention · legal hold · evidence exportsSign in →CustomAny retention schedule and tiering policySign in →

Two ways to run it

Per estate, or per pool

Both include verified restores. The difference is whether one policy set covers the whole estate or each pool keeps its own.

Per EstateOne policy setBackup policies, schedules and retention applied across the whole estate, so every workload and pool inherits protection by tier.

Estate-wide policy by tier

One protection report for all workloads

Central restore-test evidence

Best for:A single governed organisation

Explore Per Estate plans

Per PoolScoped per poolProtection scoped to each capacity pool, subsidiary or entity — isolated policies, isolated retention and reporting, one relationship.

Policies and retention per pool

Separate protection report each

Independent restore evidence

Best for:Multi-entity or reseller estates

Explore Per Pool plans

Who decides, who runs it

What each group gets from Backup

Four groups shape a cloud decision. Pick the one you belong to — the platform reads differently from each seat.

“The backup claim is now evidenced”

Restore tests produce reports, so the statement that data is protected is backed by results rather than by a schedule.

GovernedSovereignPredictable

FAQs

Do you test restores?

Yes — scheduled restore verification is part of the service, with results reported per policy.

What is protected?

VMs, managed databases and object buckets, with policies set per workload tier.

Can backups survive a compromised admin account?

That is what the Immutable Vault is for — write-once copies with dual-control deletion.

Where are the copies stored?

In-country, with second-zone copies available, and long retention tiered into Archive Storage.

How fast is a restore?

To the recovery objective agreed per tier — file-level restores are typically minutes, full systems longer.

How is the flat fee different from public cloud pricing?

Everything inside the plan you opt for is included — no additional charge for the components that make it up. Public clouds meter each component on consumption, so the bill moves with usage. Here the plan is reserved for you and the figure you agreed is the figure you pay.

Can we drive it from Terraform and CI?

Yes. Every operation is exposed through the REST API, CLI and a maintained Terraform provider, with scoped API keys per team. If the console can do it, your pipeline can do it.

How do limits and quotas work?

Quotas are yours to shape — carve capacity per team or project and delegate inside it. Hard ceilings are a conversation, not a wall; the estate re-baselines at thresholds you approve.

Can security services be included in my plan?

Yes. Endpoint security, firewalls and WAF are scoped into the same flat fee when you add them — one figure, no separate security invoice.

Better together