Collect public sources
Official APIs are preferred. Official pages are considered only when an API is unavailable. Source language is kept separate from display language.
Methodology
Comparable, and traceable.
Host Bijia organizes public plan data. It is not a performance benchmark, reseller or endorsement of any provider. We separate what is known from what is not, so you can decide for yourself.
Normalize; don't guess
vCPU, memory, storage, storage persistence, transfer and billing periods are placed in one structure. Ports, stock, IPs or locations absent from the source remain unknown.
Validate before publishing
Builds check required fields, sensible values and source linkage. If a collector or validation fails, the batch does not replace the previous successful release.
Retain checkable evidence
Each run retains source URLs, timestamps, HTTP status and content fingerprints; the build also exposes readable JSON endpoints.
Pricing rule
Read the billing period before comparing a number.
A plan can be billed hourly, monthly, yearly or over a longer term. Tables prefer a non-regional price, then convert its actual billing period to a labelled monthly equivalent. Conversion supports comparison and does not mean a monthly purchase option exists.
One-time setup fees, minimum purchase terms, introductory prices and renewal prices are recorded separately. Monthly filters and sorting compare the current recurring charge without amortizing setup fees; introductory prices are labelled and are not presented as long-term renewal prices.
Tax, exchange fees, promotions, renewals, regional uplifts and stock can change. This site shows public information at collection time, not a final checkout quote.
Unknowns & policies
Unknown is not zero, and unlimited is never inferred.
Transfer is separated into explicit quotas, explicitly advertised unlimited transfer, and unknown quotas. Sales markets, currencies and page languages are not treated as datacenter locations. A plan can still be published with explicit unknowns when its core evidence is sufficient.
Refunds, backup responsibility, management scope, CPU use, China bandwidth basis and prohibited uses are extracted from official terms as separate facts. Each retains a normalized value, scope, source text and snapshot link; an uncollected policy is never treated as permission by default.
Incident & reputation rule
Community evidence matters, with visible attribution.
Official status pages, provider statements, community reports and independent monitoring are labelled separately and retain their original links. Community evidence may support conclusions, but is not presented as an official fact; multiple sources describing the same incident are automatically grouped as one event.
Incident count, scope, first response, public updates, cause, remediation, data loss and compensation are shown separately. An unconnected incident source means insufficient information, not an incident-free or more stable provider.
All rules are enforced by code, with no manual review step. A batch is automatically rejected when its structure fails validation or its evidence cannot be linked.
Limits & reminders
What these comparisons do not answer.
Not a benchmark
Advertised CPU, bandwidth or disk type cannot establish real-world performance. Test with a workload close to yours before drawing performance conclusions.
Not an availability promise
Regional, plan and IP stock can change immediately after a page is built. Confirm through the provider before ordering.
Not the whole market
Only sources that passed collection and validation are displayed. Absence does not mean a provider lacks a suitable plan.
Public interface
You can inspect the data directly.
This build contains a directory of 35 provider(s).
/api/v1/catalog.json
The directory links to each provider's public raw fields.