Cloud hosting deals show 6 of the 29 resource limits the provider publishes
Answer first: The plan card that Hostinger's cloud hosting page delivers in its HTML names six of the resource parameters the same provider publishes for that plan, and the page's own FAQ links to the table that publishes the rest. That table, Parameters and limits for hosting plans, carries 29 parameter rows for Cloud Startup. CPU cores, RAM, disk space, inodes, PHP workers and website count appear on both pages; the other 23 rows - among them bandwidth, I/O, parked domains, database count and size, the 10,240 MB MySQL backup ceiling, every PHP memory and upload ceiling, the four OPCache values and the mailbox count - appear only in the table. The VPS deal cards show four of the seven parameters the table publishes for the KVM plans. Two cells are blank on every page read: a backup size ceiling for VPS, and any numeric support limit for any plan. And where the two cloud pages do overlap, one number disagrees - the deal card says Unlimited websites for Cloud Startup, and the table says 100.
Published: 2026-09-24 00:05
What this guide adds
This page keeps two things apart. First, what Hostinger's own pages state, each statement tied to the URL it came from and quoted only in short fragments. Second, the counts, ratios and comparisons this site ran on top of those statements, labelled (derived). Every sourced figure was read from a provider page on 24 September 2026 (UTC); every derived figure is arithmetic on those figures and nothing else. No price, discount, transfer figure, resource value, success rate or customer count has been estimated, converted or inferred, and cells the provider does not publish are printed as not published rather than filled in.
What was compared, and when
Three pages were read on 24 September 2026 (UTC): the cloud hosting page at hostinger.com/cloud-hosting, the VPS hosting page at hostinger.com/vps-hosting, and the parameters page that both of them link to from their own FAQ. All three returned HTTP 200, and all three are permitted by the provider's robots.txt, which disallows only its special-offer subpaths, cart, API proxy, tag pages and query-string variants.
The link is worth stating precisely, because it is the provider's own signpost rather than a page this site went looking for. The cloud hosting page's FAQ asks what the CPU, RAM, inode and disk limits of Hostinger plans are, and it answers by sending the reader to that article. The VPS page carries the same question and the same link. So the deal pages themselves say the resource numbers live somewhere else.
One limit on the comparison, stated up front. The cloud hosting page delivers a single plan card in its HTML. That card's resource lines - 4 CPU cores, 4 GB RAM, 100 GB NVMe storage, 2 000 000 inodes - match the Cloud Startup column of the parameters table, so Cloud Startup is the plan compared below. Cards for the other cloud plans are not present in the delivered HTML and are not assessed here.
The resource lines the deal card does show
Cloud Startup's card on the cloud hosting page carries eighteen feature lines. Six of them name a parameter that also has a row in the parameters table. Here they are beside the value the table publishes for the same plan:
4 CPU cores on the card; CPU cores 4 in the table.
4 GB RAM on the card; Memory (RAM) 4 GB in the table.
100 GB NVMe storage on the card; Disk space 100 GB in the table.
2 000 000 inodes (files and directories) on the card; Inodes 2 000 000 in the table.
100 PHP workers on the card; PHP workers 100 in the table.
Unlimited websites on the card; Number of websites 100 in the table.
The card's other twelve lines - 10 Web Apps, Access sharing, a free domain for one year, unlimited SSL, 15 vibe coding credits, unlimited mailboxes per website free for one year, managed hosting for WordPress and WooCommerce and Web Apps, CDN included, a dedicated IP address, priority 24/7 expert support, a 30-day money-back guarantee and AI SEO ready - have no same-named row in the parameters table. They are features rather than measured limits, and this page does not count them as equivalent to one.
The 29 parameters the provider publishes for the same plan
These are the rows the parameters page prints for Cloud Startup, quoted as published. The table gives the same 29 rows for Cloud Professional, Cloud Enterprise and Cloud Enterprise Plus:
Number of websites 100; Node.js websites 10; parked domains 300; CPU cores 4; memory (RAM) 4 GB; disk space 100 GB; inodes 2 000 000; I/O 20 480 KB/s; bandwidth Unlimited; database count 300; database size 6 GB; MySQL max backup size 10240 MB; MySQL max connections (global) 500; MySQL max connections per user 100; MySQL max import size 10240 MB; MySQL max statement time 3600 s; MySQL max query time 1800 s; PHP workers 100; PHP max execution time 480 s; PHP max input time 480 s; PHP memory limit 3072 MB; PHP max POST size 3072 MB; PHP max upload file size 3072 MB; server-based email sending 10 per minute and max 100 per day; OPCache memory 384 MB; OPCache interned strings buffer 32 MB; OPCache max accelerated files 32531; OPCache max file size 512 KB; mailbox count 10 per website.
Two things about this table are worth flagging before the comparison. First, it names four cloud plans, while the cloud hosting page's own FAQ names three - Cloud Startup, Cloud Professional and Cloud Enterprise, at $7.99, $15.99 and $29.99 per month for the 48-month plan. Cloud Enterprise Plus appears in the limits table and nowhere on the deal page.
Second, the table closes with two sentences that bound how far any of it can be relied on. It states that the parameters and limits outlined are fixed, that additional resources require a plan upgrade, and that individual resources cannot be upgraded separately. It then states that hosting parameters are subject to change without notice and directs the reader to the provider dashboard for the most up-to-date information.
What the deal card leaves out (derived)
Six of the 29 published rows are named on the card; 23 are not. The 23 are node.js websites, parked domains, I/O, bandwidth, database count, database size, MySQL max backup size, both MySQL connection ceilings, MySQL max import size, both MySQL time limits, PHP max execution time, PHP max input time, PHP memory limit, PHP max POST size, PHP max upload file size, server-based email sending, the four OPCache values and the mailbox count.
In practical terms the omissions cluster in three places. Transfer is absent: bandwidth is published for the plan and does not appear on the card. Databases are absent as a group - count, size, import ceiling, connection ceilings and the backup ceiling all live only in the table. And the application ceiling is absent except for its worker count: a buyer learns that the plan runs 100 PHP workers but not how much memory each request may use, how large an upload may be, or how long a script may run.
The same table also shows why the resource multiple quoted on the deal page cannot be checked. The cloud hosting page's FAQ states that managed cloud hosting offers 4X more speed and 20X more resources compared to traditional web hosting, and its meta description says up to 20X more resources. The parameters table publishes web hosting plans too - Web Single, Web Premium and Unlimited - so a baseline is available. Against Web Premium, Cloud Startup's published 4 CPU cores, 4 GB RAM, 100 GB disk and 2 000 000 inodes are 4x, 2x, 5x and 5x the web hosting values of 1, 2 GB, 20 GB and 400 000. Against Web Single the widest ratio is 10x, on disk space and inodes. No pairing in the table produces 20x. The provider does not name the baseline it used, so this is not evidence that the claim is wrong - it is evidence that the claim cannot be reproduced from the numbers the provider itself publishes, which is the same problem as the missing rows.
The one number the two pages disagree on (derived)
The card says Unlimited websites. The parameters page's first row for Cloud Startup is Number of websites 100, and it prints 100 for all four cloud plans. Both statements come from the same provider, both were readable on 24 September 2026, and the deal page links to the table that contradicts it.
This page cannot say which one governs a purchase. The table's closing note points readers to the provider dashboard for current information, which makes the table the more conservative source of the two; but the card is the page a buyer actually sees before deciding. What can be said is narrower and still useful: a limit described as unlimited on one page and as 100 on another is not a limit a buyer can plan against until the provider reconciles it, and the reconciliation is not published.
Cloud against VPS: the same provider, two shapes of limit (derived)
The VPS cards do better than the cloud card on one row and worse on three. Each KVM card carries four resource lines, and the parameters table publishes seven rows for the same four plans: vCPU cores, memory, disk space, IPv4 and IPv6 allocation, inodes, I/O and bandwidth. So the cards show four of seven.
What the cards print, as published: KVM 1 has 1 vCPU core, 4 GB RAM, 50 GB NVMe disk space and 4 TB bandwidth. KVM 2 has 2 vCPU cores, 8 GB RAM, 100 GB NVMe and 8 TB bandwidth. KVM 4 has 4 vCPU cores, 16 GB RAM, 200 GB NVMe and 16 TB bandwidth. KVM 8 has 8 vCPU cores, 32 GB RAM, 400 GB NVMe and 32 TB bandwidth. The table's remaining three rows for those plans are IPv4 and IPv6 allocation of 1, inodes unlimited, and I/O of 300 MB/s - all three of which the cards omit.
Bandwidth is the clearest case in the whole comparison. The parameters table publishes bandwidth as Unlimited for all four cloud plans. The cloud deal card does not mention bandwidth at all. The VPS cards do mention it, and there it is metered: 4, 8, 16 and 32 TB. So the deal page whose published allowance is unlimited keeps quiet about it, while the page whose allowance is finite prints the number. That is the reverse of what a buyer scanning for value would expect, and it is only visible if you open the table the deal page links to.
One further difference sits in the table rather than the cards. The cloud table expresses I/O in kilobytes per second, with Cloud Startup at 20 480 KB/s. The VPS table expresses the same parameter in megabytes per second, at 300 MB/s. Neither table states a conversion, and this page does not perform one; the point is that a reader comparing those two columns is comparing two different units, and inodes run the other way - 2 000 000 on the cloud plan against unlimited on the VPS plans.
Backup and support: the cells that are not published
Backup is the clearest blank cell, and it is blank in two different ways.
On cloud, the deal page states 99.9% uptime, daily backups and DDoS protection. The parameters table publishes a ceiling for the same plan - MySQL max backup size 10240 MB - but no cadence. So the cadence is on the page without the ceiling and the ceiling is in the table without the cadence, and no page read carries both. A buyer who wants to know how large a backup can be before the free service stops covering it has to assemble that answer from two pages.
On VPS the ceiling is missing altogether. The VPS deal page states Free weekly VPS backups and snapshots, and explains that the service includes automatic weekly backups plus manual snapshots you can use to revert your server if something goes wrong. The parameters table's KVM block has no backup row at all. So for VPS the cadence is published and the size ceiling is not published anywhere this check could read.
Support has the same shape. Both deal pages advertise priority 24/7 expert support, and the cloud page defines it: available 24/7 via live chat, with a median response time of one minute for requests in English, plus support in 10 other languages. The parameters page publishes no support row for any plan. There is therefore no published numeric support limit for any plan read here - no response ceiling, no escalation time, no remedy - and a median response time is a median, not a ceiling.
What this check cannot tell you
The unknowns are worth naming, because they are the part a deal page leaves out.
No page checked carried a machine-readable published or modified date, so the age of the text cannot be verified from metadata. Everything here was read on 24 September 2026 (UTC), and the parameters page states outright that hosting parameters can change without notice.
The parameters table covers cloud plans, web hosting plans, agency plans, VPS plans, game panel plans and several legacy and regional plan families. Only the cloud and KVM blocks were used here; the others sit outside the two deal pages examined.
The Cloud Startup card is the only cloud plan card in the delivered HTML, so this comparison says nothing about what the Cloud Professional or Cloud Enterprise cards show once the page's plan selector is used.
No page publishes a backup ceiling for VPS, a numeric support limit for any plan, or the baseline behind the 20x resource claim. And none of this says whether a plan is good value: a published limit is not a measured one, no resource was tested here, and the comparison is only between what the provider prints and what its own deal page chooses to show.
A repeatable method for reading a deal card's resource claims
Deal cards are summaries, and summaries drop things. The check takes about five minutes per provider.
First, open the deal page and list every line on the plan card that names a quantity: cores, memory, storage, inodes, workers, websites, bandwidth, backups. Those are the numbers the page wants you to buy on, and the list is usually shorter than you expect.
Second, search the same page's FAQ for a question about limits. Providers tend to answer it by linking to a table rather than printing the table, and that link is the signpost that matters.
Third, open that table and count its rows. The gap between the two counts is what the card left out, and it is usually the rows a buyer would care about: transfer, database ceilings, backup ceilings, PHP memory.
Fourth, compare only the rows that appear on both pages, and check the values agree. A card that says unlimited where the table says a number is the highest-value thing you can find, because it changes what you can plan for.
Fifth, write not published in the cells the provider leaves empty instead of filling them from a neighbouring plan. A blank is a fact about the deal, and it is the one thing a deal page will never print.