Fleet Handbook
Hosting for side projects — Nine ideas, one account: where that arrangement stops being clever
Written for people running several small things at once — where a single multi-site plan is genuinely the right answer, and the specific moment it stops being one.
Straight answer first
Put the whole shelf on one Pro plan: twenty-five sites on a single account, one flat cost, a new idea live in minutes, and no per-project platform fee stacking up while eight of the nine sit idle.
The judgement this page is really about is the exit from that arrangement. The moment a project has a paying user, a partner or a client attached to it, shared quotas and a shared filesystem stop being an economy and start being a liability — and the fix is a separate account, not a bigger one.
Written by the Hosting Seller staff · Checked 24 August 2026
Free
Migration into the account
24/7
Cover at any hour
Daily
Backups across every site
$0
To open a new account
Side projects are cheap to start and expensive to administer. The cost that catches people is not the hosting; it is the accumulated admin of nine half-finished things sharing one set of credentials, one backup and one person's memory of how any of it was wired together.
So this is an account-structure question before it is a hosting question. Get the structure right early and moving a project out — because it grew, or because somebody bought it, or because it now has a customer — is a two-hour job rather than an archaeology dig.
Where one account genuinely is the right answer
For work that is entirely your own, a single multi-site plan wins on every axis that matters. Pro carries twenty-five sites on one account with 20 GB of NVMe and a terabyte of bandwidth, which is a great deal of shelf for a collection of experiments that mostly sit still.
The economics are the point. Per-project platform pricing bills you for nine things while one of them is doing anything, and the bill arrives monthly whether or not the projects do. A flat account absorbs the quiet majority and lets the busy one borrow the headroom.
Setup speed matters more than it sounds. Enthusiasm for a new idea has a short half-life, and a new domain, a database and a one-click install inside an existing account is a five-minute job rather than an afternoon of provisioning.
What separate accounts actually buy
Isolation, first. Each account has its own filesystem, its own database users, its own quota and its own backup. A runaway import script on one project cannot fill the disk that another project needs, and a compromise on one is contained rather than shared.
Delegation, second. You can hand somebody a login to one account without handing them a view of the other eight. On a shared plan, any access you grant is access to everything, and there is no partial version of that.
Portability, third — and this is the one people wish they had thought about. Moving an account is moving an account. Extracting one site from an account containing nine means picking apart a filesystem, a database list and a backup that was never built to be split.
The project that acquires a customer
The transition is usually invisible on the day it happens. Somebody pays for something, or a friend starts relying on the thing, and the project quietly acquires an obligation. From that point the arrangement has to survive somebody else's expectations, not just your own tolerance.
Practically, that means the site needs its own account, its own backup you can actually point at, and a support story that does not consist of you remembering. If there are two or three of these, reseller hosting is the structure that fits: a cPanel per project, WHM above them, quotas you set per account, and daily backups run per account rather than across the whole heap.
It also means billing becomes real. A standalone WHMCS licence sits on our shelf for exactly this reason — the point where invoices, renewals and proration stop being something you can do by hand without eventually getting one of them wrong.
Sizing it without guessing
Count sites, not visitors. Nine domains on one account is a plan-tier question; ten thousand visitors a month on one of them is not, because a cached page costs almost nothing to serve. The tier that fails you is nearly always the one that ran out of sites or disk, not the one that ran out of speed.
Watch disk rather than bandwidth. Media libraries and database backups grow quietly and monotonically, and the first sign of trouble is usually a failed backup rather than a slow page.
When one project does break out, move that one and leave the rest alone. Plan changes happen in place from the client area, and the range continues into VPS and dedicated hardware, so a good month is spent shipping rather than replatforming.
A host recommending hosting, said plainly
There is no affiliate fee behind the answer on this page, because we are the supplier. That is a bias worth stating out loud rather than concealing behind a scoring table, and it leaves the rest of the page free to be about structure rather than about ranking.
The whole ladder — single site, multi-site, reseller, VPS, dedicated — is one catalogue and one account, so moving between rungs is a change to your billing rather than a migration to somebody new.
- One flat cost across a shelf of idle projects
- A new site live inside an existing account in minutes
- Isolation available the moment a project needs it
- Plan changes made in place, without a migration
Why Hosting Seller
On every plan, as standard
Twenty-five sites, one invoice
The Pro plan holds the whole shelf on a single account, so eight quiet projects cost nothing extra to keep on the air.
Isolation when it starts to matter
Reseller accounts give each project its own cPanel, quota and backup — the structure you want the day somebody else depends on one.
Setup fast enough to keep the idea
A domain, a database and a one-click install inside an existing account is minutes of work, not an afternoon of provisioning.
A clean way out for the winner
Plan changes are made in place from the client area, so the project that breaks out moves up without a rebuild.
Billing that can grow up with you
A standalone WHMCS licence is on the shelf for the point where invoices and renewals stop being something you do by hand.
Backups per account, not per heap
Daily backups run at account level with self-service restores, which is what makes separating projects worth the effort.
Price Tags Compared
How we compare with the household names
Typical sign-up and renewal prices across the market, set next to ours — the second number most comparison charts leave off.
| Line item | Hosting SellerBest seller | Typical big-brand host | Typical budget host | Typical loss-leader |
|---|---|---|---|---|
| Entry price / mo* | $2.42/mo | $4–$6 | $2–$4 | $1–$3 |
| Price at renewal / mo | $2.42/mo | $10–$15 | $8–$12 | $4–$6 |
| Renewal price on the entry plan is unchanged | ||||
| SSL on every plan | ||||
| Site migration included | ||||
| The entry plan uses NVMe storage | ||||
| Entry plan gets a backup daily | ||||
| Live human support, 24/7 |
*The number in our column is the cheapest plan on our shelf, priced on an annual term and pulled live from the very catalogue that feeds the pricing page, so it cannot drift out of date. Other columns show the ranges shared hosting tends to advertise inside each bracket: introductory rates that normally ask for a one-to-four-year commitment, then climb once that term expires. Naming individual competitors and printing their prices is something we have stopped doing. A figure we cannot re-check on the day you read it has no business sitting in front of you. So compare us with whoever you are genuinely weighing up, and read the renewal line first. That line tells you more than the headline ever will.
First Steps
From choosing to live
- 1
Decide the structure before the third project
Write down which projects are entirely yours and which have another person attached. That single list decides whether you need one account or several, and it is much cheaper to answer now than after ten.
- 2
Watch the disk figure, not the visitor count
Media and database backups are what actually fill a plan. Check the disk usage in the panel once a month and you will see the tier change coming a long way off.
- 3
Move the breakout project on its own
When one takes off, upgrade or separate that one and leave the other eight where they are. Plan changes happen in place, so the busy week is spent on the project rather than on a migration.
In the Box
Packed with every plan
- Twenty-five sites on one Pro account, each with its own domain
- Per-account quotas and isolation available on reseller plans
- A backup taken daily with restores you run from the panel
- PHP chosen per site, so an old project and a new one coexist
- SSH, Git and Composer for deploying without a file manager
- Softaculous one-click installs for WordPress and 240+ applications
- Plan changes applied in place, with no move between hosts
- NVMe disks and LiteSpeed caching at every tier, not only the top one
- A standalone WHMCS licence available when billing gets real
- Mailboxes on your own domain included with the plan
Across the Counter
Things people ask us all the time
How many side projects can sensibly share one account?
As many as the plan allows, provided every one of them is yours. Pro holds twenty-five sites on 20 GB of NVMe. The limit that bites first is usually disk rather than the site count, because media libraries and database dumps grow quietly. Check the disk figure in the panel monthly and you will see it coming.
What actually goes wrong when a project has a partner and shares my account?
Three things at once. They cannot be given a login without seeing everything else on the account. Their site's backup is entangled with yours. And when the partnership ends, handing the site over means extracting it from a shared filesystem and a shared database list. Separate accounts avoid all three for a modest amount of money.
Is a reseller account overkill for four small projects?
If all four are yours, yes — a multi-site plan is cheaper and simpler. If two of them have somebody else attached, the reseller structure earns its keep straight away through isolation, per-account quotas and the ability to hand one over intact rather than picking it out of a heap.
What happens to the other eight projects when one of them gets busy?
Nothing, if you move only the one that grew. Plan changes are made in place from the client area and the range continues through VPS to dedicated hardware, so the busy project climbs a rung while the quiet ones stay exactly where they are on the same flat cost.
Read next
Joomla Hosting Plans
Joomla hosting judged by what the platform actually asks of a host, and what it costs you to support.
VPS Hosting for Developers
Root access and a real server, weighed against what you would have to take on to run one.
Web Hosting
cPanel hosting on NVMe with SSL, migration and the first year of the domain included.
VPS Hosting
KVM virtual servers with root access, DDoS filtering at the edge and one flat price.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Put the whole shelf on one account.
Twenty-five sites, one flat cost, a new project live in minutes, and isolation available the day one of them needs it.
See Web Hosting plans