Your first client project goes well. You build the site, they love it, and then they ask: "So how do we get this thing online?"
And you realize you have no answer ready.
Hosting doesn't come up much when you're learning to code. Tutorials assume you already know what it is, or they skip it entirely and deploy to Vercel with one click. But your client's local bakery isn't going on Vercel. They want an email that says @theirbakery.com and a URL they can put on a business card.
Here's what you actually need to know before that conversation happens.
The three things every client site needs
Get clear on the difference between a domain, hosting, and SSL. Junior devs often mix these up, and clients always will.
A domain is the address: theirbakery.com. You register it through a domain registrar (Namecheap, Porkbun, or through your hosting provider). A .com costs roughly $10–15/year.
Hosting is where the website files live. When someone types the domain into a browser, their computer connects to the hosting server and loads the files. Shared hosting (where the client's site sits on a server alongside hundreds of other sites) costs $2–10/month and handles almost every small business site fine.
SSL is the padlock in the browser bar. It means the connection is encrypted. You need it. Google flags sites without it. Most hosting providers include it free via Let's Encrypt, so this is usually a checkbox during setup, not a separate purchase.
Those three things are the floor. Everything else is optional until the client asks for it.
Who should own the hosting account
This is where junior developers most often make a mistake. The answer is: the client.
If the hosting account is in your name and the relationship ends badly, you're holding their website hostage. If they want to hire someone else later, they're stuck waiting on you. If you get hit by a bus, they lose access to their own site.
Set the account up in the client's name using their email address and their payment method. You can be added as a collaborator or get the login credentials to manage it, but the account is theirs.
Same rule for the domain. Register it in their name. Disputes over domain ownership are slow, expensive, and completely avoidable.
Shared hosting is fine for most small clients
A lot of junior devs assume clients need something powerful: a VPS, a cloud server, something that sounds serious. For a brochure site or a WordPress blog getting a few hundred visitors a day, they don't.
Shared hosting means the client's site runs on a server shared with other sites, splitting the resources. For low-traffic sites this is almost indistinguishable from dedicated resources in practice. It's cheap because the cost is shared, not because it's bad.
For most early client projects, the Hostinger Premium or Business plan covers everything you need. The Premium plan is around $2.99/month and lets you host up to 100 websites, which matters once you have a few clients, because you're not paying for a separate account per project. One plan, multiple sites, free domain in the first year, SSL included.
When does shared hosting stop being enough? When a site gets consistent traffic in the tens of thousands of monthly visitors, runs resource-heavy custom code, or processes a lot of simultaneous transactions. A WooCommerce store doing serious volume needs a VPS or a managed host. A florist's five-page website does not.
What cPanel actually is
Most shared hosting accounts come with cPanel, a browser-based dashboard for managing the hosting. It's where you'll spend most of your time.
From cPanel you can create email accounts, install WordPress in about 90 seconds, manage files through a built-in file manager, create MySQL databases, configure DNS records, set up subdomains, and check error logs.
You don't need to memorize it before you start. The layout is consistent enough across providers that you'll figure it out as you go. The main thing is knowing it exists: it's your primary interface for managing a client site, not the command line, at least not for typical small projects.
Some hosts use a custom dashboard instead of cPanel. Hostinger uses one called hPanel. Same concept, different layout.
Clients always want email
If you don't ask about email before you build the site, your client will ask about it after launch.
They want hello@theirbusiness.com, not hello@gmail.com. Most hosting plans include email hosting. You create the accounts in cPanel and hand over the credentials. The client then connects that address to whatever app they use (Gmail, Outlook, Apple Mail) using IMAP settings the host provides.
Walk them through the setup, or write them a short guide. "How do I check my business email in Gmail" is the most common post-launch question you'll get, almost without exception.
One thing worth knowing: email on shared hosting is basic. It works fine for a small business that needs a contact address and maybe two or three accounts. If a client sends mass newsletters or runs a sales team with real email volume, they need a dedicated service like Google Workspace ($6/user/month) instead. Know which situation you're in before launch.
Backups: have this conversation before something breaks
Most hosting providers run automated backups, but the frequency varies. Hostinger does weekly backups on the basic plans and daily backups on higher-tier ones. If the site gets hacked on a Wednesday and your backup schedule is weekly, you might be restoring a version that's six days old.
Tell the client this. Ask if they want a more aggressive setup. A WordPress plugin like UpdraftPlus can run its own backups to Google Drive regardless of what the host does. It's worth installing on every WordPress project, full stop.
The time not to be explaining backup schedules is while you're trying to recover a broken site at 11pm.
A checklist for your first handoff
Before you hand anything over:
- Hosting account in the client's name with their payment info
- Domain registered in the client's name
- SSL active (confirm the padlock appears in the browser)
- Email accounts set up, client can log in
- Client has their cPanel or hPanel credentials
- Backups are running
- You've agreed in writing on whether you're doing ongoing maintenance or they're on their own
That last one matters. If they expect free updates and you expect to be done at launch, someone is going to be annoyed in three months. Make it explicit before the project ends, not after.
Hosting feels complicated before you've dealt with it. By your third client site it's close to routine. The first one takes longer because you're learning where the buttons are. That's normal.
The part that trips people up isn't technical. It's the account ownership conversation and the email conversation. Have both of them early, and most of the rest is just clicking through a setup wizard.
If you're ready to get your first client site online, Hostinger is where I'd start — 20% off with that link, free domain in the first year, and everything covered in this article works out of the box.
Top comments (0)