Provisioning the Backbone: Choosing cPanel, CloudLinux, and JetBackup

There’s a moment in every build where things shift—from experimenting to establishing something real. For me, that moment came while setting up a Virtual Private Server (VPS) and deciding how I wanted to manage everything that would live on it.

I’ve spun up servers before. I’ve run applications, hosted projects, and stitched together systems. But this time feels different. This isn’t just about getting something running—it’s about creating a stable foundation for multiple projects, and possibly something more long-term.

That direction didn’t come out of nowhere.

Yesterday, I met with the director of the Small Business Development Center at Laurel Ridge, following a recommendation from the Chamber of Commerce’s director. We talked through ideas, direction, goals, skills, connections, history, and what building something sustainable might actually look like. One piece of advice stood out: start working on proposals.

For me, that didn’t mean writing documents—it meant building something real enough to stand behind before writing the proposal.

A Shift in Perspective

Around the same time, something else clicked into place.

I recently submitted a FOIA request (26-241) regarding the county’s tourism website, asking for a contract the county had approved, but hadn’t included in their board packet for review. The numbers seemed high, and I wanted to know why. What came back was more than I had expected. Two amendments to extend the original contract for an additional year at $1,495 for maintenance, and an original proposal of $42,500 submitted in response to an RFP to build the website. As mentioned, I previously spoke about the website’s pages with no content, broken links, and missing businesses within town limits.

At first, the numbers didn’t make sense. Then the responsibilities behind them did. As I dug deeper, it became clear that the cost wasn’t really about hosting.

It was about:

• reliability
• backups
• uptime
• reporting and statistics
• ongoing support

The infrastructure behind the site—the part most people never see—was the real value.

That reframed things for me.

If I’m going to build something and offer it to others, it can’t just be:

• “hosting”
• or “a server”

It has to be a dependable system with built-in value.

Something I can confidently explain to a client—not just what it does, but why it matters.

Something that makes it clear there’s real value in choosing a local provider—someone accessible, accountable, and known—rather than an anonymous service behind a login screen filled with stock photos.

Because once you look behind the curtain, you realize the value was never just hosting—it was everything built around it.

That’s the difference between selling space on a server—and building something people can rely on.

Building Something Worth Proposing

That’s where the advice from the SBDC started to connect.

If I’m going to create proposals, then what I’m proposing needs to be complete.

Not just:

• a website
• or a place to host files

But a package that includes:

• reliable backups (not just full-server snapshots)
• isolation between clients
• predictable performance
• a structure that reduces risk

That’s what pushed me to move beyond the trial phase.

Instead of continuing to experiment, I started purchasing the licenses needed to support that level of dependability.

Understanding Value (Including My Own Time)

Another important part of that conversation was about value—specifically, my own.

It’s easy to look at hosting costs and think:

“I can do this cheaper.”

And in some ways, that’s true.

By cutting out layers of providers and managing things directly, I can:

• lower costs
• increase margins

But that’s only part of the equation.

Looking at real proposals made it clear that people aren’t paying for hosting—they’re paying for everything that keeps it working when something goes wrong.

There’s also:

• the cost of the infrastructure (licenses, server, storage)
• the cost of maintenance
• and the cost of my time

That last part matters more than I’ve been giving it credit for. Lowering costs by removing the middleman also means inheriting the responsibility for everything they handled.

The SBDC director made a point that stuck with me: I need to stop undercutting my own value.

So this isn’t just about building something affordable—it’s about building something:

• reliable
• understandable
• and worth what I charge

Learning Hosting from the Inside

Hosting—at this level—is a bit new to me.

Not hosting a website. Not deploying an app. I’ve done that for years.

But managing the environment itself, making decisions about structure, isolation, backups, and scalability—that’s a different perspective.

So instead of jumping straight into offering hosting to others, I’m doing something more practical: I’m chewing on my own dog food.

I’m bringing my own websites and projects into one centralized environment:

• to reduce overall costs
• to simplify management
• to understand the system from the inside

If it works for me, I can confidently offer it to others later.

Why cPanel (Again)

Choosing the Right License: Why 30 Accounts

The licensing model has shifted over time, and now everything is based on account limits.

I chose: cPanel Pro Cloud (30 accounts)

Not because I need 30 accounts today—but because I know how I work.

I don’t build just one thing. I build:

• experiments
• tools
• community projects
• client work (current and future)

Trying to force all of that into 1 or even 5 accounts would lead to overlap, shared risk, and eventual cleanup.

Thirty accounts gives me:

• separation between systems
• room to grow
• flexibility to treat each project as its own environment

It’s not about using all 30—it’s about not hitting a wall early.

Why CloudLinux OS

Why JetBackup

What I Didn’t Choose — Yet

There were several other options available:

• LiteSpeed — Performance gains, especially for WordPress. It’s on my radar as a potential next upgrade, given the number of WordPress sites I work with.
• Imunify360 — Full security suite, more suited for larger environments.
• KernelCare — Live updates without rebooting.
• WHMCS — Billing and client management.

Each has its place—but not at this stage.

Skipping Server Monitoring (For Now)

There was also an option to enable external server monitoring.

I skipped it.

cPanel already provides built-in alerts, and at this stage:

• I’m actively involved
• I’m still learning the system

Adding another layer would just add noise.

Where Things Stand

At this point:

• cPanel is licensed and active
• CloudLinux is installing
• JetBackup is ready to be configured

More importantly, the direction feels clearer.

This isn’t about reselling hosting.

It’s about understanding what people are actually paying for—and building that intentionally.

It’s about:

• consolidating what I already have
• reducing costs
• building something dependable enough to stand behind
• and understanding the true value of what I’m offering

Looking Ahead

The goal isn’t just to offer hosting—it’s to offer something dependable enough that people don’t have to think about it.

Next comes the part that matters most:

• structuring accounts
• setting resource limits
• configuring backups properly
• continuing to migrate existing projects

That’s where this stops being theoretical and starts becoming real.

And for now, that’s enough—one step at a time.