Hosting Terms
What is Nginx?
Nginx in plain English — the meaning, the comparison, and why it matters to anybody running a website.
Straight answer first
Nginx is the event-driven web server built for high concurrency — thousands of simultaneous connections handled on very little memory, and the internet's favourite reverse proxy into the bargain.
Below: the fuller explanation, a picture that makes it stick, why it matters in practice, and where you will actually run into it.
Written by the Hosting Seller staff · Checked 1 August 2026
0
Terms left unexplained
100+
Definitions, cross-linked
Real
Examples from real kit
Free
To read, naturally
Its architecture copes with floods of connections that a process-per-request model finds expensive, which is why it stands at the front door of so many busy stacks, usually passing requests back to application servers behind it.
It ignores .htaccess entirely, and on purpose. Configuration is central and applied on reload, trading shared hosting's per-customer flexibility for speed and predictability.
Nginx, by comparison
One exceptionally quick counter clerk serving a hall full of customers by never stopping, instead of hiring a clerk per customer. Both approaches get everyone served, at wildly different staffing costs.
Comparisons simplify, naturally — but this one holds together well enough to reason with, and reasoning is the whole point of a glossary.
Why this one is worth knowing
You will meet nginx on a VPS, either as your web server or as a proxy in front of something else, and in practically every modern tutorial. Knowing that it uses central config rather than .htaccess saves the classic hour spent wondering why your rules do nothing.
That is the test for any technical term, incidentally — not 'do I understand it fully' but 'do I know when it is the answer to my problem'. For this one, you now do.
One concrete example
A VPS owner puts nginx in front of a Node application. Certificates, compression and static files are handled at the proxy, and everything else is forwarded to the port the app listens on.
Perfectly ordinary once you have seen it, which is rather the point: most hosting concepts are simple machinery wearing an intimidating name.
Where you will meet it on our platform
You will meet it in the control panel and occasionally in a support conversation, usually already set the right way. If this term made sense, the natural next reads are Apache, LiteSpeed, VPS and CDN.
Real people answer the counter at any hour, including the awkward questions other hosts wave off as out of scope.
Why we bothered with a hundred definitions
Every confusing term in hosting turns into a support ticket sooner or later, so we defined the hundred most common ones properly, once, in the plain English we would use across the counter.
Real people answer the counter at any hour, including the awkward questions other hosts wave off as out of scope.
- 100+ terms, all in plain English
- Everyday comparisons and real examples
- Related concepts linked together
- Written by the people on the desk
Why Hosting Seller
On every plan, as standard
The next reads, mapped
Read on into Apache and LiteSpeed — terms rarely stand alone, so the neighbours are linked.
Linked, never siloed
Related terms cross-reference each other, so one lookup grows into a working understanding.
Honest about what to skip
Most terms are recognise-level rather than operate-level, and the glossary says which is which.
One term, fully landed
Nginx defined, pictured by comparison and placed in your own control panel — recognise-level in a single read.
Plain English first
Every term defined for people who run sites, not for other sysadmins — jargon translated rather than restated.
Pictures that stick
Each concept gets a comparison you will still remember at the moment you actually need it.
First Steps
From choosing to live
- 1
Find it in your own account
Open the control panel and find where this concept lives — seeing it attached to your own site is what turns a definition into understanding.
- 2
Check what the defaults are
Our platform ships sensible defaults for this — check rather than assume, and you will know your setup instead of hoping about it.
- 3
Follow the terms next door
Concepts travel in packs — Apache, LiteSpeed and VPS finish this one's picture, and each is a two-minute read away.
In the Box
Packed with every plan
- One-click installs for WordPress and 400+ other applications
- A 99.9% uptime commitment, watched by monitoring day and night
- The renewal price printed on the tag matches the order price
- A backup taken daily, with restores you run yourself
- The Softaculous installer for one-click application setup
- DDoS filtering handled out at the network edge
- A free SSL certificate on every plan, reissued before it lapses
- SSH, Git and Composer on the plans built for developers
- cPanel, the panel the rest of the trade already knows
- WebP image optimisation built in and costing nothing
Across the Counter
The questions we get asked most
Why do my .htaccess rules do nothing at all on nginx?
Because nginx never reads them. The same behaviour is written into its central configuration as rewrite and location blocks and applied on reload. Translation guides exist for all the common recipes; the difference is a philosophy, not an oversight.
Should I pick nginx for my own VPS?
For serving heavy concurrency or acting as a proxy, it is excellent. For following tutorials comfortably, Apache's ecosystem is gentler on a beginner. Both are fine choices — take the one whose documentation you will still tolerate at eleven at night.
Is there a refund if it does not suit?
Yes — thirty days. Put the hosting through real work, and if it is not right, ask for the money back and you get it; there is no retention script to survive first. Domain registrations are the one carve-out, because registries take that fee the moment the name is placed.
Does the price climb when the term is up?
No. What you pay to order is what you pay to renew, year after year. We do not run teaser rates, so there is no year-two ambush waiting in the calendar, and your bookkeeping can treat the hosting line as a fixed number.
Where do the servers actually sit?
Our hosting runs from European datacentres with London at the centre, behind server-level caching that keeps cached pages quick for visitors anywhere. For most sites the build of the platform — NVMe disks, LiteSpeed, sensible numbers of accounts per machine — decides the speed far more than the postcode does.
Are backups included, and can I put one back myself?
A backup is taken daily on every plan, and the restore is yours to run from the panel in minutes — files, databases or both, at three in the morning without waiting on a ticket. Keeping your own copy offsite as well is never a bad habit, and nothing here stops you.
What if the site outgrows the plan I bought?
You move up in place. Plan changes are made from the client area with no migration and no downtime, and the range runs from small shared accounts through VPS to whole dedicated servers. Growing becomes a line change on your account rather than a hunt for a new host.
Read next
Apache
Apache is the long-serving open-source web server whose conventions — .htaccess above all others — shaped t…
CDN (Content Delivery Network)
A CDN keeps copies of your site's assets on servers around the world, so each visitor is served from the ne…
PHP Hosting
Pick the PHP version site by site, on quick NVMe hardware.
Drupal Hosting
Drupal hosting with Composer, Drush and the PHP version set per site.
Packing up and moving host? Take our checklist.
A plain running order for a move nobody notices: what to copy first, how to carry email across without dropping a single message, when to point DNS, and the two slips behind nearly every hour of downtime we get called about.
Give your website a proper home.
From a first website to a rack of servers, moving up is a change to your account rather than a migration.
See the plans