
Most hosting gives you a slice of one server and throttles you at the edge of it. This platform spreads your site across a cluster and lets it draw what it needs during a spike, with no per-account CPU, memory or process limits.
This is the part that matters most. A busy hour does not queue behind a resource limit, because there is no limit drawn around your account.
Each block is a unit of capacity. The grey blocks are what a fixed plan gives you all day, whether you need them or not.
When requests climb, processing power, memory and bandwidth are allocated from across the platform within seconds. When the spike passes, they go back. Nothing to provision, nothing to upgrade mid-campaign.
A site under sustained load is shifted onto dedicated capacity so it keeps answering, and so nobody else on the platform feels it.
You are not buying a fixed slice of one machine. Your site can reach across many servers, which is what makes a traffic surge survivable rather than fatal.
Campaign launches, a television mention, Black Friday, a post that travels further than expected: these are the moments hosting is actually judged on, and they are the moments a fixed resource cap hurts most.
Every plan runs on the same autoscaling cluster with the same absence of resource caps. What changes is the number of sites, the storage and what is included before you add anything.
A business site or a handful of small ones, on the same platform the big plans use.
The tier most businesses settle on: room for a portfolio of sites, with backups already included.
For stores and applications where an hour of slowness is measured in lost orders.
One account, Unlimited client sites.
Longer terms lock the price for the whole term. Site counts and storage are the only ceilings; there is no cap on CPU, memory, processes or bandwidth on any plan. Move up or down whenever you like and we prorate the difference.
All three are optional, all three are billed with the plan, and any of them can be switched off again.
The acceleration layer: compute nodes running at up to 4.20 GHz, your site pre-fetched by every CDN location worldwide, and a 5 GB database quota across every database on the package.
Daily protection for sites that change occasionally, with a dated timeline you restore from yourself.
Greater retention, email backups and stronger recovery coverage, for sites that change every day.
Autoscaling and high availability are the same architecture seen from two angles: many servers behind one site.
One node failing changes the picture for us, not for your visitors.
Requests are distributed across multiple web nodes. A node that stops answering is taken out of the pool automatically and the others carry the traffic.
Web, database, mail and storage each run as separate redundant services, so pressure or failure in one does not cascade into the others.
Files sit on replicated NVMe arrays built to survive drive and server failures without taking sites offline.
Health checks run constantly and our engineers are alerted on failures. Most incidents are handled before anyone notices enough to open a ticket.
Every plan carries a 99.9% uptime commitment, and the platform measured 100% over the last twelve months.
Most shared and cloud hosting in this market runs on a container system that caps each account's CPU, memory, processes and I/O. Hit the cap and your visitors wait, even though the server has capacity sitting idle.
Plans differ by how many sites and how much storage you need, not by how hard you are allowed to work the servers.
Off-the-shelf hosting software is built for one server. Running it across a cluster means changing it, and these are the two places where that work shows up in what you get.
The standard speed tools assume your site lives on a single machine, so they scale badly the moment it does not. The platform runs a customised PHP-FPM and opcode cache instead, written to hand a site the resources it needs while it is busy rather than rationing them.
A stock configuration with a resource limiter on top, which is what produces the per-account CPU and memory ceilings you are used to seeing.
Almost every host balances for failover: a server dies and your site is moved so it stays online. That is disaster recovery, and it is here too. The difference is what happens on the far more common day when nothing fails and everything is simply busy.
Failover only. Your site stays online when a server dies, but stays slow when a server is merely overloaded, which happens far more often.
Both of these are the reason the no-limits claim on this page is possible at all. You cannot remove the caps without first removing what made them necessary.
Autoscaling decides how much capacity answers your traffic. Turbo changes three separate things: where your code runs, how far ahead the cache is warmed, and how much room the database has.
Dynamic work runs on standard nodes, and the first visitor in each region waits while the cache fills.
The page is already at every edge before anyone asks for it, and what cannot be cached runs on faster processors.
Illustrative, not a benchmark: the gain depends on how cacheable your pages are and how much of your traffic is dynamic. We will measure yours before and after if you ask.
Requests are routed to high-frequency compute nodes running at up to 4.20 GHz. It shows up most in the work that cannot be cached at all: admin screens, checkouts, search and imports.
Your site is pulled into every CDN location worldwide in advance, instead of being cached the first time somebody asks for it. The first visitor in a region gets the fast response rather than paying for it.
The database quota rises to 5 GB, and it applies to every database on the package rather than to one of them. That ceiling is usually what constrains a large catalogue or a busy membership site.
Turbo goes on without downtime and comes off the same way. A cache report in the control panel shows you what is being served from cache and what is still reaching your application.
Images, scripts and stylesheets are served from edge caches close to the visitor instead of travelling back to the origin every time. It is part of the platform rather than a paid extra, and it is on for every plan including the smallest.
Visitors are answered by the nearest healthy edge automatically, with no per-region configuration to maintain.
No bandwidth allowance to watch and no overage invoice after a busy month.
The CDN and the page cache purge together, so a publish is live everywhere rather than in some places.
Shorter round trips improve the loading metrics search engines measure, particularly for visitors furthest from the origin.
Edge locations are part of the platform and change as it grows. Ask us which edges serve your main audience and we will tell you what we are seeing.
All of this is on every plan, Launch included. Turbo and the two backup tiers are the only paid extras.
Cloud hosting only means something if a failure somewhere does not become an outage for you, and if a busy hour does not become a throttle.
Requests arrive at the platform rather than at a machine. Routing picks capacity that is healthy and free, the autoscaler adds more when demand climbs, and anything that stops answering is taken out of rotation.
Many servers answer for one site, added and removed as demand moves through the day.
Replicated, with its own failover, so your queries do not queue behind a neighbour's.
A separate service on separate machines, so a busy website never holds up your email.
Redundant NVMe arrays that tolerate a drive, or a whole server, failing without losing anything.
Your site runs across the platform rather than on a machine you could point at. That is what makes both the scaling and the failover possible.
Web, database, mail and control panel run as independent redundant services, so pressure on one does not drag the others down.
A site under heavy load is moved onto dedicated capacity, so your performance does not depend on somebody else's bad day.
Health checks and alerting run continuously, with engineers on call rather than an answering service.
Changing plan changes the ceilings in place: same account, same IP, no reinstall and no migration window.
Hosted on our platform with local peering for Pakistani visitors and edge caches worldwide for everybody else.
Add-on means available at the price above; included means it is already in the plan.
| Feature | Launch | Business | Scale | Agency |
|---|---|---|---|---|
| Websites | 10 | 25 | 100 | Unlimited |
| NVMe storage | 50 GB | 150 GB | 400 GB | 1 TB |
| Bandwidth | Unmetered | Unmetered | Unmetered | Unmetered |
| CPU, memory, processes | No caps | No caps | No caps | No caps |
| Autoscaling | ||||
| High availability | ||||
| Global CDN | ||||
| Mailboxes (10 GB each) | 10 | Unlimited | Unlimited | Unlimited |
| MySQL databases | Unlimited | Unlimited | Unlimited | Unlimited |
| Wildcard SSL | ||||
| Web application firewall | ||||
| DDoS protection | ||||
| Malware scanning | ||||
| Backups included | ADD-ON | |||
| Snapshot retention | 30 days | 30 days | 30 days | 30 days |
| Email backups | ADD-ON | ADD-ON | ADD-ON | ADD-ON |
| Turbo acceleration | ADD-ON | ADD-ON | ADD-ON | ADD-ON |
| Staging and cloning | ||||
| Object cache | ||||
| SSH, Git and WP-CLI | ||||
| Separate client logins | ||||
| Free migrations | Unlimited | Unlimited | Unlimited | Unlimited |
| Support | 24/7 | 24/7 | 24/7 priority | 24/7 priority |
| Uptime commitment | 99.9% | 99.9% | 99.9% | 99.9% |
Move between plans at any time. We prorate the difference and nothing needs rebuilding, because the ceilings change rather than the machine.
Unlimited free migrations on every plan, from any control panel or a plain backup file.
No data loss, no downtime window to book, and nothing for you to reinstall.
Control panel login, or an archive if that is easier. We work the rest out from what is there.
Files, databases, mailboxes and DNS are copied and tested on a staging URL before anything changes for your visitors.
Usually overnight. DNS switched, mail verified, and we stay on the ticket until you confirm it is right.
A rough guide rather than a rule; tell us the traffic and we will size it properly.
Brochure sites, service businesses and anything where the enquiry form is the revenue.
Caching, object cache and staging tuned for the stack most Pakistani stores run on.
Laravel, Node and custom software that needs guaranteed CPU, SSH and deployment from Git.
Many client sites on one account, each isolated, with one invoice and separate logins.
What the Turbo add-on actually changes: faster processors, pre-fetching to every edge and a larger database quota.
Read more →Search and register the name, with DNS, transfer lock and reminders included.
Read more →Move an existing domain across. It adds a year and nothing goes offline.
Read more →Registration, renewal and transfer prices for every extension, in rupees or dollars.
Read more →What people ask us about autoscaling, limits and pricing.
When demand rises, the platform allocates more processing power, memory and bandwidth to your site from across many servers, then releases it when the spike passes. You do not provision anything, and there is no upgrade to buy in the middle of a busy afternoon.
When demand rises, the platform allocates more processing power, memory and bandwidth to your site from across many servers, then releases it when the spike passes. You do not provision anything, and there is no upgrade to buy in the middle of a busy afternoon.
Tell us what you run today. We will size the plan, migrate it free and stay on the ticket until it is stable.