Get Started
Pricing · Hardware translation

Give us your server specs. Get a cloud bill of quantities.

Enter the kit you run today — sockets, cores, RAM, disk. We translate it into sized cloud lines with storage, backup, DR and monitoring, then price it three ways so the saving is on the table.

Start with your hardwareJump to the savingDesign it component by component
How you want to consume it

The hardware you run today

One line per server model. Group identical machines and set the quantity — everything else is per server.

Physical estate
7 servers · 128 cores · 1.1 TB RAM · 20 TB disk
Line nameWorkload roleServersSocketsCores / sktRAM (GB)Disk (TB)
GPU or AI hardware?Add GPU nodes in Architect Your Cloud.

How we translate it

Change any assumption and the bill of quantities re-sizes.

Threads per core
Hyperthreaded hosts: one physical core presents two vCPU.
80% of installed capacity
Most estates run well below their nameplate. 100% is a like-for-like rebuild.
+20%
Applied to vCPU, RAM and every storage line.
30% of production
Dev, test and staging, sized at half the production shape.
20% of data
Archives, media and backups of record move off block storage.
14 days
Sized at 3% daily change on top of a full copy.
Disaster recovery
60% of production
4 hours
15 min
Cost basis for the comparison
1 FTE
Patching, monitoring, backup checks and out-of-hours cover, at USD 6,500 per FTE-month fully loaded.
8 TB
Metered by public cloud, free on our flat fee — set it to what you actually move.
36-month commitment: 15% off the flat fee and a fixed rate card.
Network edge & security
Firewalls and load balancers in HA pairs, sized at 5 Gbps, plus a WAF in front of the web tier.
Your cloud bill of quantities
21
cloud instances across 18 BoQ lines
vCPU
528
RAM
2.2 TB
Storage
84.1 TB

Compute

7 lines
LineServiceQtySizing per unitRole
web-appCore Cloud Servers×430 vCPU · 120 GB RAM · 600 GB diskProduction
core-dbPrime Cloud Servers×246 vCPU · 248 GB RAM · 600 GB diskProduction
file-serverCore Cloud Servers×130 vCPU · 64 GB RAM · 600 GB diskProduction
nonprod-poolCore Cloud Servers×318 vCPU · 72 GB RAM · 100 GB diskNon-prod
web-app-drCore Cloud Servers×330 vCPU · 120 GB RAM · 600 GB diskDR
core-db-drPrime Cloud Servers×246 vCPU · 248 GB RAM · 600 GB diskDR
file-server-drCore Cloud Servers×130 vCPU · 64 GB RAM · 600 GB diskDR

Storage & data

4 lines
LineServiceQtySizing per unitRole
app-data-volBlock Storage×115.8 TB usableProduction
archive-bucketObject Storage×14 TB usableProduction
nonprod-data-volBlock Storage×14.8 TB usableNon-prod
dr-data-volBlock Storage×19.5 TB usableDR

Network edge

4 lines
LineServiceQtySizing per unitRole
perimeter-fwFirewalls×25 Gbps · 4 vCPU · 8 GB RAM · 60 GB diskProduction
public-lbLoad Balancer×25 Gbps · 4 vCPU · 8 GB RAM · 60 GB diskProduction
app-wafWAF×14 vCPU · 8 GB RAM · 60 GB diskProduction
edge-ipsPublic IPs×18 IPsProduction

Protection & operations

3 lines
LineServiceQtySizing per unitRole
nightly-backupBackup Service×121 instances protected · 41.5 TB backup · 14-day retentionProduction
obersvaObersva×121 instances monitored · 200 GB retainedProduction
dr-planDisaster Recovery×14 h RTO · 15 min RPO · 6 instances replicatedDR

What we assumed

Each physical server becomes one cloud instance: cores × 2 threads × 80% utilisation × +20% headroom, rounded to our standard shapes.
Local disk splits into an OS and application disk on the instance (capped at 500 GB) with the remainder as 19.8 TB of shared block and object capacity.
Databases and ERP land on Prime Cloud Servers; web, application, VDI and file servers on Core.
Backup covers all 21 instances — production, non-prod, DR and virtual appliances — at 14-day retention.
DR replicates 6 instances into a second region against a 4 h RTO and 15 min RPO.
Availability zones, regions, service groups and billing terms are set per line in Architect Your Cloud.
This is a sizing, not a quote.
Send it over and a solution architect validates the shapes, applies your term and returns one flat monthly figure.
Email me this BoQGet the flat fee
What the move is worth

Three ways to run this estate, priced side by side.

Same sizing, same protection, same growth headroom — only the operating model changes. 3-year committed figures, indicative regional shapes.

YallaCloud, 3-year committed
USD 10,540
Option 1
Keep it on-premise
USD 16,128
your own kit, your own hands
Hardware, over 5 yearsUSD 895
Maintenance & support (18%/yr)USD 805
Hypervisor licencesUSD 1,017
Rack, power, cooling, portsUSD 2,861
Storage arrays & backup targetUSD 2,507
Your operations teamUSD 6,540
Second site for DRUSD 1,502
Capex amortised over 60 months. Refresh lands again in year five.
Option 2
Public cloud, metered
USD 35,788
same sizing, consumption pricing
ComputeUSD 16,362
Idle / over-provisioned (25%)USD 4,090
StorageUSD 3,522
EgressUSD 828
Support tier (10%)USD 1,988
Operations you still staffUSD 3,270
Disaster recoveryUSD 5,727
Every line moves with usage — the invoice is a forecast, not a number.
Option 3
YallaCloud, flat fee
USD 10,540
3-year · everything included
Compute, right-sizedUSD 6,387
Storage & backupUSD 2,236
Licencesincluded
Disaster recoveryUSD 1,916
3-year commitment−15% applied above
Operations & 24/7 supportincluded
Egress & per-ticket feesnone
Obersva monitoringincluded
One number, fixed for the term. Idle capacity is our problem, not your invoice.
Saving vs staying on-premise
USD 5,588 / month
35% less than running it yourself · USD 201,152 over 36 months
Saving vs public cloud
USD 25,247 / month
71% less than the consumption meter · USD 908,907 over 36 months
Over a 36-month term
USD 908,907 saved
against public cloud — USD 201,152 saved against on-premise.
Indicative regional shapes, not a quotation: USD 245 per core and USD 15 per GB RAM of hardware over 60 months, 18% annual maintenance, USD 410 per host per month for rack, power, cooling and ports.
Operations costed at USD 6,500 per FTE-month fully loaded — public cloud keeps half that effort with you, our flat fee keeps none.
Public cloud is priced at list with committed-use discounts applied at term, plus 25% idle capacity, a 10% support tier and metered egress; the flat fee carries none of the three.
Both modes price compute from the same capacity basis — amortised iron, vendor support and our DC, power and network, plus margin. Managed instances add 45% for running your guests and carry 106 cores' worth of platform capacity at 2.5:1; dedicated capacity is the raw pool, so it prices lower per unit.
Hypervisor licensing follows your choice above (VMware vSphere); tell us if you'd rather bring your own and we adjust the fee.
A solution architect validates the sizing and returns the committed figure — this page is for direction, not signature.
After the sizing

Three ways to take this further

Refine it component by componentOpen the sizing in the builder, drop the lines onto layers, set regions, zones and billing terms per component.Architect Your Cloud →Compare it against your billModel three years of flat fee against per-item public cloud pricing and your current on-premise run cost.TCO Calculator →Have us do the migrationAssessment, wave planning, cutover and day-2 operations under one SLA and one accountable team.Managed Services →