New format
What hosting is and how to choose a provider
Hosting means putting the site’s files and databases on a server that answers visitors around the clock. Without it a domain is only a name — nowhere to serve the content from.
Below: hosting types and how to choose for the job. Plans, panels, and SLAs change; trust the current contract and support, not 2017 screenshots.
Why you need hosting
When someone opens a page, the browser asks a server for data. Hosting takes the request and returns HTML, images, API answers. Servers usually sit in data centers: power, bandwidth, cooling, physical security.
Analogy: the site is the art; hosting is a 24/7 gallery. A home PC for a public site is almost always worse — unstable link, IP, noise, security.
Free vs paid
Free platforms often cut CPU and disk, show their own ads, and barely own downtime or deletion. Fine for a practice landing; for leads and payments — reputation and downtime risk.
Paid hosting is sold in packs: space, traffic, PHP/DB, mail, backups, SSL. Price rises with resource guarantees and support level.
Typical free downsides:
- small quotas and resource queues
- provider ads or redirects
- weak accountability for data
- CMS and cron limits
- painful migration when the project grows
Paid hosting types
Shared: many sites on one machine, resources split. Cheap and simple — a neighbor with a heavy script can still eat performance.
VPS — a dedicated slice of CPU/RAM/disk in a virtual machine. More control (often root), more responsibility for the OS and updates.
Dedicated — a whole physical machine. Colocation — your server in the provider’s rack: you pay for space, power, and bandwidth. Cloud — a pool of machines with scaling; billing is often for use, not “one disk forever.”
Roughly by job:
- brochure / blog — shared
- store, Bitrix, spikes — VPS or managed cloud
- high load and your own stack — dedicated / cloud
- your own hardware — colocation
What to check when choosing
Start with site type and growth: brochure, catalog, store, customer account. Then stack (PHP/Node, DB version), whether you need root, who administers.
Provider age and reputation help, but league tables can be paid — read fresh support and incident reviews, not only “place on a chart.”
Practical checklist:
- uptime and SLA in the contract, not only in ads
- latency and data-center geography vs your audience
- backups: frequency, retention, restore test
- panel, SSH, mail, SSL, inode/CPU limits
- 24/7 support and language
- renewal price, not only the first month
Speed, uptime, and search
Slow TTFB and frequent 5xx hurt conversion and crawl. “Server response under 200 ms” is a useful engineering target — not a magic ranking formula.
Search engines care about availability and page experience, but hosting alone does not rank you. First a stable server response and correct HTTPS, then content and demand. Ranking work is planned over months, not a one-month flip.
Legal and ops nuances
If the site collects personal data, policy, consent, and where data is processed matter. Rules change — check current norms and a lawyer, not one paragraph of an old guide.
Separately lock access: who owns the hosting account, where invoices go, whether 2FA and a password manager are in place. A staff change should not leave the site ownerless.
What to remember
Hosting is infrastructure under the site: from shared to cloud. Choose by load, stack, and who will admin.
Domain, DNS, and hosting can be split. Backups and support beat a pretty first-month price.
FAQ
Are hosting and domain the same?
No. A domain is a name in DNS. Hosting is where the site and DB live. Buy them from different companies if you want — link them via NS.
Is free hosting OK for a business?
For a throwaway “try it” card, sometimes. For commerce — provider ads, tight limits, weak accountability, and thin support.
Shared or VPS for a beginner?
A brochure site and a small blog often live on shared. A store, CRM, or traffic spikes — closer to VPS or cloud with clear resources.
Does 99.9% uptime guarantee rankings?
No. Availability helps users and crawl, but rankings are a separate story: content, demand, competition. Prep ≠ page one in a month — ranking work is planned over 2–6 months.
Where should personal data live?
If you process personal data of Russian residents, account for localization rules and the provider contract. That’s legal/security territory — not an “obvious plan checkbox.”
Picking hosting for a site?
We’ll match the type and criteria — without “uptime = TOP” myths and paid rankings.
Discuss the task
