Hosting Glossary

Inode

Inode in plain English — the definition, the analogy, and why it matters to anyone who runs a website.

The short answer

An inode is the filesystem's record for a single file or folder — hosting plans cap inode counts, effectively limiting how many files an account may hold.

The sections below unpack it properly — how it works, why a site owner should care, and a concrete example of it in the wild.

Jargon left unexplained

100+

Linked definitions

Real

Platform examples

Free

To read, obviously

Storage bytes and inode counts are separate budgets: a million tiny cache files can exhaust inodes while using little space, and one huge video does the reverse.

The classic inode gluttons are cache directories, mail archives (every message is a file), session files and node_modules-style dependency trees.

A picture that makes Inode stick

Library index cards versus shelf space — the shelves (gigabytes) may be half empty while the card catalogue (inodes) is full, and no new book enters without a card.

Analogies simplify, of course — but this one holds up well enough to reason with, and reasoning is the point of a glossary.

The practical stakes

Accounts hit inode ceilings mysteriously long before storage ones — knowing the concept turns 'disk full but it isn't' support tickets into a cache-purge and mail-cleanup afternoon.

That's the test for every technical term, incidentally — not 'do I understand it fully' but 'do I know when it's the answer to my problem'. For this one, now you do.

A concrete example

A WordPress site's abandoned cache plugin left 800,000 stale fragment files — trivial in gigabytes, most of the inode allowance — deleted in one panel operation once identified.

Multiply that example across every site on the internet and you have the concept's entire job description.

How this shows up in your hosting

On our hosting this mostly takes care of itself — the platform applies the sensible defaults, and the panel exposes the controls when you want them. The concepts worth knowing next: Disk Space, Cache, Mailbox Quota and Backup.

Daily automatic backups with one-click restores come with every plan.

Person managing a hosting account through the cPanel dashboard

A glossary from people who answer tickets

Every confusing term in hosting eventually becomes a support ticket — so we defined the hundred most common ones properly, once, in the plain English we'd use on the phone.

Renewal prices match signup prices, so the year-two invoice is the most boring email you'll get from us.

100+ terms, plain English
Analogies and real examples
Cross-linked related concepts
Written by the support desk

Why HostingAlly

What you get with every plan

Honest about what you can skip

Most terms are recognise-level, not operate-level — the glossary says which is which.

Analogies that stick

Each concept gets a picture you'll remember at the moment you actually need it.

Plain English first

Every term defined for site owners, not for other sysadmins — jargon translated, not restated.

The practical stakes named

Not just what it is — when it's the answer to a problem you're having.

Linked, not siloed

Related terms cross-reference, so one lookup becomes a working understanding.

Grounded in a real platform

Examples reference the hosting you'd actually use, not abstract diagrams.

Getting Started

How to get going

1
Spot it in your own setup
Open your control panel and find where this concept lives — seeing it attached to your own site is what converts definition into understanding.
2
Check the defaults
Confirm how your account has this configured — usually correctly by default here, and now you'll know rather than guess.
3
Follow the related terms
Concepts travel in packs — Disk Space, Cache and Mailbox Quota complete this one's picture, and each is a two-minute read away.

Included

What's covered on our plans

cPanel — the industry-standard control panel
SSH, Git and Composer access on developer-friendly plans
DDoS protection at the network level
No setup fees, ever
Renewal prices that match signup prices
Per-site PHP version selection
LiteSpeed server-level caching
Free domain for the first year on annual plans
24/7 support from real people
Email accounts on your own domain

FAQ

Your questions, answered

How do I see my inode usage?

The panel's statistics show the count against your plan's limit. Rising counts with stable content point at caches, sessions or mail — the renewable resources that accumulate silently.

How do I reduce inode usage safely?

Purge application caches (they rebuild), clean old mail (every message is a file), delete stale backups-inside-the-account, and prune unused installations. The candidates are always the many-small-files categories.

What happens if I outgrow my plan?

You upgrade in place — plan changes apply from your client area without migrations or downtime, and our range runs from small shared plans through VPS to dedicated servers, so growth is an account change rather than a new-host project.

Are backups included, and can I restore them myself?

Daily automatic backups are standard, restorable from the panel in minutes — files, databases or both, at 3am without a ticket if that's when you need it. For extra cover, you're welcome to run your own offsite copies alongside.

Do you include email with hosting?

Yes — mailboxes on your own domain come with every hosting plan, with webmail, IMAP/POP/SMTP access and spam filtering. Standalone email hosting also exists for domains whose websites live elsewhere.

Is SSL really included at no cost?

On every plan, with no exceptions — certificates are issued automatically when your domain points to us and renew themselves before expiry. The encryption is identical to paid DV certificates; paid tiers exist only for wildcard convenience or organisation-level validation.

Which control panel do you provide?

cPanel — the industry standard, which means every tutorial on the internet matches your screen, your backups restore anywhere cPanel runs, and skills learned here transfer for life. Plesk and DirectAdmin options exist on specific plans for those who prefer them.

Put an ally behind your website.

From your first site to a fleet of servers, the upgrade path is an account change, not a migration.

See Hosting Plans