Shared hosting is a hosting plan where many customer accounts run on the same server and share its processor, memory, disk and network connection. The provider installs and maintains the operating system, the web server, PHP and the database server, and you manage your own account through a web control panel. It is the simplest and cheapest way to put a website online, and it suits company sites, blogs and small shops that run on standard software such as WordPress.
#How shared hosting works
A shared server holds many separate accounts. Each account has its own home directory, its own databases and its own mailboxes, and the server software keeps the accounts apart so that one customer cannot read another customer's files. When a visitor opens your site, the web server finds your account by the domain name, runs your PHP code, reads from your database and sends the page back.
Because the hardware is shared, the provider sets limits for each account: how much CPU time and memory a script may use, how many processes may run at once and how many database connections are allowed. These limits stop one busy site from slowing down every other site on the machine. They are also the main difference between a cheap plan and a good one, even though they rarely appear in the headline of a plan table.
#What a shared hosting plan usually includes
- A control panel for files, domains, databases, email and account settings.
- Email on your domain: mailboxes, aliases, forwarders and webmail for reading mail in a browser.
- Databases, usually MySQL or MariaDB, with phpMyAdmin to browse, import and export them.
- An app installer that sets up WordPress, Joomla, Drupal, PrestaShop, OpenCart and similar software for you, including the database and its user.
- FTP or SFTP access for uploading files, and SSH on some plans.
- Cron jobs for scheduled tasks such as sending a newsletter or clearing a cache.
- An SSL certificate for HTTPS, either included in the plan or sold separately.
- Backup space for copies of your files and databases.
Check what each line means on the plan you are considering. Email may cover a handful of mailboxes or an unlimited number, with very different storage per mailbox. Backups may mean automatic copies that you can restore yourself, or only space where you keep copies you make. The plan table rarely tells you which, so ask.
#What shared hosting cannot do
The limits follow directly from sharing one server with other customers:
- Shared resources. Your site competes with other accounts for the same CPU, memory and disk. A well-run server enforces fair limits, but a traffic spike on your site runs into your account limit, and heavy load from a neighbor can still affect response times.
- No root access. You cannot install system packages, change server-wide settings or pick a database version the provider does not offer. You can change only what the control panel exposes.
- No long-running processes. Queue workers, WebSocket servers and other background programs are usually not allowed, or are stopped after a time limit. Scheduled work has to fit into cron jobs.
- A fixed software stack. You get the PHP versions and extensions the provider supports. Node.js, Python or Go applications may be unsupported, or available only as paid add-ons.
- A shared IP address. Many accounts often send mail from the same address, so a compromised account on the server can affect how mail from other accounts is delivered.
None of this matters for a typical company website. It matters a great deal for a custom application with background jobs, integrations with other systems or strict performance requirements.
#What to compare between plans beyond price
Most plan tables lead with disk space and bandwidth, often listed as unlimited. Those numbers rarely decide how a site performs. Compare these instead:
| What to check | What to ask |
|---|---|
| CPU and memory limits | What are the limits per account, and what happens when the site reaches them? |
| Sites and domains | How many domains can the plan host, and can each one have its own folder and settings? |
| How many mailboxes, how much storage each, and how many messages per hour may you send? | |
| Databases | How many databases, how large, and which engine and version? |
| PHP | Which versions are offered, and can you choose a version per site? |
| SSH and cron | Are they included, optional or missing? |
| Backups | How often are copies made, how long are they kept, and who restores them? |
| SSL | Is a trusted certificate included, and does it renew automatically? |
| Renewal terms | What does the plan cost after the first term? |
Two practical tests help. Ask the provider a specific technical question before you buy and see whether the answer is specific too. And confirm that you can download a full backup of your files and databases at any time, because that is what lets you move to another host later.
#What a hosting control panel does
A control panel is the web interface for running a hosting account without a terminal. In a typical panel you can:
- upload, edit and delete files in a file manager;
- create databases and database users, and open them in phpMyAdmin;
- add mailboxes, forwarders and spam filters;
- point domains and subdomains to folders and edit DNS records;
- install applications, set cron jobs, switch PHP versions and read statistics and logs.
cPanel and Hepsia are two well-known examples. cPanel is a commercial panel that many hosting providers license and run on their servers. Hepsia is a panel built for its own hosting platform, with hosting, domains and email managed in one interface. Both cover the everyday tasks above. They differ in layout and in which extra features the provider turns on.
The panel matters more than it seems, because it decides how much you can do yourself. If adding a mailbox or restoring a backup needs a support ticket, a five-minute job can take a day.
#When you have outgrown shared hosting
Shared hosting is enough for many sites for their whole life. These are the signs that it no longer is:
- Pages slow down under ordinary load, and the provider reports that your account keeps reaching its CPU or process limits.
- The application needs queue workers, WebSockets or another long-running process.
- You need a PHP extension, a runtime or a server setting that the panel does not offer.
- You want a staging environment that matches production exactly.
- The site handles data that you would rather not keep on a server shared with strangers.
The usual next step is a VPS, a virtual server with its own resources and root access. It also brings server maintenance, so decide who will do that work before you move. The article shared hosting or VPS: when to move and how covers the signs and the migration steps in detail, and types of web hosting explained compares every option from shared hosting to cloud.
#How PN Scripts can help
PN Scripts Hosting offers shared hosting plans managed from one control panel, with a file manager, webmail, phpMyAdmin, an installer for WordPress and dozens of other applications, and self-signed SSL on every plan. When a site needs more room, KVM VPS and dedicated servers are available from the same company. You can compare the shared hosting plans side by side.
Comments
Comments
Be the first to leave a comment.
Leave a comment