Neytom vs shared hosting
Shared hosting packs many sites on one OS user space. Neytom gives each domain an isolated stack.
| Typical shared | Neytom | |
|---|---|---|
| Isolation | Shared neighbors | LXC/CT (Micro+) · Shared free Nano |
| Deploy | Manual / slow | ~60s stacks + templates |
| Email & SSL | Often add-ons | Included on plans |
| Backups | Host-dependent | ZFS backup + snapshot |
| Trial | Rarely free | Nano free 30 days |
The shared hosting bargain
Classic shared hosting sells density: many customers per machine, a familiar control panel, and a low monthly sticker. That model works until one neighbor saturates disks, until a PHP worker pool is exhausted, or until a security incident in an unrelated account increases your risk surface. “Unlimited” marketing rarely means unlimited isolation.
What isolation buys you
Neytom’s hosting model gives Micro+ one LXC/CT per domain (Nano is Shared free) stack. CPU, memory, and filesystem boundaries belong to that site. You still get a panel and one-click templates — you are not forced into raw SSH just to escape shared packing. When you outgrow managed hosting, Cloud VPS and the custom builder keep the same account.
Operational basics that should not be upsells
- TLS certificates as part of the hosting plan, not a checkbox buried in add-ons.
- Mailbox path included so “we will figure mail later” does not become a deliverability fire drill.
- ZFS backup + snapshot so restore is a product feature, not a ticket lottery.
- ~60s deploy templates for WordPress and other stacks — see Templates.
Decision checklist
- Do you host more than one client or brand on the same account? Prefer isolation.
- Have you ever unexplained slowdowns at peak hours? Prefer isolation.
- Do you need root/Docker immediately? Skip shared entirely and open vs generic VPS.
- Still unsure? Take Nano for 30 days and measure real deploy + TTFB yourself.
Learn and migrate
Practical guides: Migration guide, Vision Deploy WordPress, and Free Nano + WordPress. See the full comparison hub under All alternatives.
Security and blast radius
Shared environments increase blast radius. A vulnerable plugin on another account should not be your incident. LXC/CT (Micro+) · Shared free Nano does not replace patching WordPress, but it shrinks the shared attack surface and keeps filesystem credentials scoped. Pair isolation with sane updates — Vision’s WordPress tutorials cover deploy and day-two hygiene without pretending security is “set and forget”.
Performance myths
“LiteSpeed + cache plugin” can mask shared contention until traffic or a noisy neighbor returns. Measure TTFB and origin CPU on a quiet Nano trial, then compare against your current shared host under the same content. If the gap is small, stay. If production regularly stalls for reasons unrelated to your code, isolation is cheaper than another year of guesswork.
FAQ
What is “noisy neighbors”?
Other sites on the same shared environment consuming CPU, I/O, or memory so your pages slow down even though your code did not change.
Is Neytom still “hosting” or a VPS?
Managed hosting with per-domain LXC isolation. If you want full root/Docker, use Cloud VPS instead of fighting a bare VPS from day one.
Do I lose email and SSL?
No — SSL and email are included on Neytom hosting plans, not bolted on after signup.
Can I try before paying?
Yes. Nano is free for new users for 30 days (no card) so you can deploy and measure.
When is shared hosting fine?
Static brochure sites with tiny traffic and zero isolation requirements. The moment you run shops, agencies, or multiple clients, isolation pays for itself.
How do I leave shared hosting?
Follow the migration guide: export, restore on Neytom, verify SSL/mail, then cut DNS.