How to Handle Hosting for Your Web Development Clients
Tags: freelancing, beginners
Published: 2019-02-10 00:11:34

---
title: How to Handle Hosting for Your Web Development Clients
description: Learn about your options when it comes to hosting your clients' sites and how I approach this with my own clients.
published: true
tags: freelancing, beginners
canonical_url: https://raddevon.com/articles/how-to-handle-hosting-for-your-web-development-clients/
cover_image: https://raddevon.com/wp-content/uploads/2019/01/server-cabinets.jpg
---
You have several options for hosting your clients’ sites depending on **what you built** and **how involved you want to be in hosting**. I’ll share a few of the options and tell you **how I host sites for my clients**.

Ways to Provide Clients with Hosting
------------------------------------

### They "Host"

The client isn’t actually hosting the app, but **they own the account the app is hosted on**. If you don’t want to be involved at all in hosting, this is your jam.

That doesn’t mean you can’t still make some money from the deal. You’re providing the host with access to a valuable asset: **your customers**. You’ve taken time to build a relationship and trust with them. Most providers are willing to pay you for access to that customer. When your client signs up (or once they’ve been hosted for a few months), you’ll get a one-time payout for the referral.

**Don’t refer your client to a provider just because they offer the biggest payout.** The relationship you have with them going forward is worth far more than a quick buck in the near-term. That trust you’ve spent time cultivating can be gone in an instant if they have a horrible experience with the provider you recommend. My approach is to research the best option for a client _first_ and only _then_ seek out an affiliate program. That way, my choice isn’t clouded by the referral payout.

To find these programs, look for a “referral,” “partner,” or “affiliate” program. You’ll usually have to sign up and be approved, so do this now rather than waiting until you’re up against a deadline.

>**Not sure how to get started with freelancing?** Take the [Freelancing Crash Course](https://raddevon.com/enroll-in-the-freelancing-crash-course/) to learn everything you need to know to start freelancing **in just a week**!

### They Host (For Real This Time)

No, really. This time, the client actually hosts the thing you built for them. In general, this makes everyone’s life harder. **Some enterprise clients will require that applications be hosted on-prem** (on premises, meaning they can’t be hosted in the cloud). They may want to deploy the app themselves, or they may want to give you remote access to deploy the app. Enterprise clients pay well, so the hassle should be worth it.

### You Host

You can host client’s sites by owning the hosting or cloud account where your clients’ applications live. You’ll pay the fees and bill them through to your clients, usually with a bit of a markup which covers maintenance, support, or whatever recurring services you want to provide your clients. This creates some **recurring income** to help keep you out of the feast and famine cycle freelancers have to deal with.

### A Hybrid Approach

Some hosts offer **white-labeling**. This allows for a hybrid of they host/you host. With white labeling, you re-sell a provider’s services, just like if you host. Instead of paying you, though, the client pays the host directly. You’ll typically either earn a percentage of the monthly fee or you can choose to mark up the monthly service, receiving the difference as a payment from the host.

The client pays the host directly, but the host’s logo never appears on invoices, admin panels, or anything else. (That’s the white-label part.) You can instead put your _own_ logo on everything. This allows you to own the relationship with your customer while the host takes care of all the hosting.

What _I_ Do
-----------

As enticing as recurring income is, **I never want to get a call at 2am because a site or an app is down**. I want to make sure my clients understand who is responsible for making sure their site is up so they know who to call when it’s down. That handoff happens by way of a referral. They sign up for the service level I recommend and I deploy the site for them.

I’ve considered trying “hosting” or even going the white-labeling route, but in either case, I would be the face of the hosting for my client. I enjoy building software, but I don’t enjoy supporting infrastructure. I’ve made **a conscious choice to do what I like** instead of making the most money.

That’s what I do for static sites, WordPress, and other PHP CMS-backed sites. In every case other, my clients have already had cloud accounts where they wanted applications deployed. If and when this comes up for me, I’ll utilize partner programs so that I can get paid for the referral and walk away from supporting the infrastructure.

I still want to help my clients any way I can. If they call me, I’ll do whatever I can to help. My goal with this approach is just to make sure I’m not the _first_ person all my clients think of when their site goes down for a few minutes.

This model works great for me. I get to work on the things I like, and I get paid when I refer a client to a host. I’m probably leaving some money on the table, but **that’s a sacrifice I’m willing to make**.