Taking Control: Consolidating Hosting and Refocusing My Work
A Shift in Direction
Tonight wasn’t about helping a single client.
It was about changing how I run my business.
For years, I’ve managed websites spread across multiple hosting providers—each with their own quirks, pricing, limitations, and support models. Every new project meant evaluating options, comparing features, and adapting to someone else’s environment.
That model worked—but it wasn’t efficient, and it wasn’t scalable.
Tonight, I took a step toward fixing that.
From Managing Hosting to Owning It
I spun up my first VPS and brought cPanel & WHM online.
That single move changes everything.
Instead of working within different hosting platforms, I now have control over:
- how sites are configured
- how performance is tuned
- how backups and security are handled
- how accounts are structured
This isn’t just a technical upgrade—it’s an operational shift.
Why This Matters for My Work
I’ve been thinking a lot about where I want to focus.
After a conversation with the Chamber of Commerce last week, it became clear:
There’s real opportunity in serving smaller, local clients better.
Not with generic hosting.
Not with one-size-fits-all solutions.
But with something more personal, more flexible, and more responsive.
Learning What People Actually Need
Alongside setting this up, I’ve started asking people more directly about their websites:
- why they chose their current platform
- what they like about it
- what frustrates them
The answers have been consistent in interesting ways.
Some are frustrated with:
- rising costs
- limited flexibility
- features locked behind higher tiers
- pricing that changes unexpectedly
Others raised concerns I hadn’t expected, like:
- where the hosting company is geographically located
A few rely on:
- ecommerce features for booking
- event management and scheduling
- collecting information through forms and managing submissions
That last one comes up more often than expected—people need simple ways to gather data, whether it’s registrations, inquiries, or internal workflows.
Even if none of these conversations turn directly into clients, they’re valuable.
They’re helping me understand:
what people actually need when they’re starting out
and where existing platforms fall short
When Pricing and Platforms Create Friction
With Hostinger, the challenges are a bit different.
It’s not just about cost—it’s about consistency and control.
While researching, I came across videos promoting low entry prices, often paired with discount codes. But when I went to verify those same plans, the pricing had already increased—sometimes significantly, and in a relatively short period of time.
That kind of instability creates hesitation.
When pricing shifts frequently:
- it becomes harder to plan long-term
- it raises questions about future costs
- it creates uncertainty for both me and my clients
But beyond pricing, there’s also the platform itself.
Hostinger uses a custom-built control panel instead of something widely adopted like cPanel or Plesk. While that can make things feel simpler on the surface, it introduces other challenges:
- fewer developers are familiar with the interface
- troubleshooting becomes less intuitive
- documentation and community support are limited
- support relies heavily on internal chat rather than shared knowledge
Instead of working within a known ecosystem, it can feel like working inside a closed system—where access and control are more limited.
Consolidation as a Strategy
Right now, my sites are scattered:
- different hosts
- different control panels
- different pricing models
That fragmentation creates friction:
- more accounts to manage
- more environments to remember
- more inconsistencies to troubleshoot
By consolidating into my own infrastructure, I’m simplifying everything:
- one environment
- one set of tools
- one place to manage it all
When “Basic Features” Aren’t Basic
One of the more frustrating patterns I’ve run into is how everyday functionality is treated as a premium upgrade.
On some platforms:
- uploading video requires higher-tier plans
- performing backups isn’t always accessible
- form builders and submission management are limited or locked behind add-ons
Forms, in particular, are something nearly every organization needs:
- contact forms
- event registrations
- booking requests
- applications or surveys
And it’s not just about collecting the data—it’s about being able to review it, manage it, and use it effectively.
These aren’t advanced features—they’re foundational.
Now that I’m running my own hosting environment, I can treat them that way.
If a site needs:
- form creation and submission storage
- direct video uploads
- reliable backup access
those can be included as part of the environment itself—not gated behind tiers or upgrades.
Supporting Nonprofits, Sustainably
A big part of my work involves helping nonprofit organizations, often free of charge.
I don’t feel great about charging for charitable efforts—but at the same time, it’s still my time, my experience, and my energy. That creates a tension between wanting to help and needing to sustain the work.
A recent conversation with the Chamber of Commerce reframed that for me.
If I don’t charge for my services, organizations will still spend the money—they’ll just spend it elsewhere.
Often with:
- someone less connected to the community
- someone who doesn’t understand their needs as well
- someone they can’t easily reach or trust
That perspective stuck with me.
Charging doesn’t mean I care less—it means I can continue to show up, support, and contribute in a way that’s sustainable.
Breaking Past Artificial Limits
Another constraint I’ve been running into is scale—not from a technical standpoint, but from account limits.
On Bluehost, I’m limited to:
- 20 websites
- 40 databases
That might sound like a lot, but it fills up quickly when you like to work the way I do.
I tend to:
- spin up small sites for focused purposes
- use subdomains for experiments or micro-projects
- keep databases isolated and purpose-driven
That approach works well—but it doesn’t fit neatly into a capped environment.
By moving to my own hosting infrastructure, those limits disappear.
The Reality of Getting There
The migration isn’t finished yet—and that’s an important part of the story.
There are still steps to complete:
- setting up nameservers
- updating DNS records
- verifying SSL certificates
- confirming database connections
- testing each site and subdomain
There are many small pieces—but they’re coming together.
What Comes Next
I still have several websites to migrate—from Hostinger, WordPress, and Bluehost.
I’ve also scheduled an appointment with the Laurel Ridge Small Business Development Center to help shape this direction further.
The message I keep hearing is clear:
I already know people in the community.
I just need to refocus what I’m offering.
That may also mean rethinking my brand.
I started quickly, chose a name, and moved on to the work.
If that name becomes a limitation, I have no issue letting it go and building something that better reflects what I’m doing now.
A Broader Perspective
This isn’t just about hosting.
It’s about control.
It’s about efficiency.
It’s about removing unnecessary limitations.
Instead of adapting to platforms, I’m building one that fits.
Final Thought
There’s a difference between:
using infrastructure
and
owning it
Tonight, I made that transition.
And while the work isn’t finished yet, everything is coming together.
