The stack, the migration, the run.
We move web agencies, hosting resellers and businesses with WordPress fleets off shared hosting onto their own dedicated cPanel servers — and we run them from that point onwards. Below is the actual stack we build, the migration pipeline we use, and what ongoing management covers.
Linux Server Management
Most of our fleet runs Linux — Ubuntu LTS, Debian, CloudLinux, Rocky, RHEL. We've been running these distributions in production long enough that the weird edge cases are familiar.
We can take an existing server you already own, or we can build one from scratch on whatever provider you prefer. Either way, the goal is the same: a box that's monitored, patched, hardened, backed up, and not a surprise.
Included as standard
- OS-level patching on a defined cadence
- Web stack configuration (nginx / Apache / Caddy / OpenLiteSpeed)
- PHP-FPM, Node, Python runtime configuration and tuning
- MySQL / MariaDB / Postgres operations and slow-query review
- SSH hardening, fail2ban, firewall rule management
- SSL certificate provisioning and renewal (Let's Encrypt or paid CA)
- Log rotation, log shipping if you want it
- Cron, systemd timer and service management
The stack we deploy
- CloudLinux for per-account isolation and resource limits
- LiteSpeed Enterprise with object caching
- MariaDB tuning on every server we deploy
- PHP version management across the supported range
- Imunify360 + KernelCare for security and kernel patching
- JetBackup to offsite storage, restored to verify
- Mail stack with managed outbound delivery
- AutoSSL across every account
Dedicated cPanel servers, built once and run properly.
The cPanel servers we deploy aren't stock cPanel boxes. Every server runs the same documented build — the same OS, the same web server, the same security stack, the same backup target — so when something behaves oddly on one box, we already know what it is on the other thirty.
Web agencies are most of our cPanel client base. They come to us when shared hosting bills outgrow what makes sense, when a reseller plan can't be tuned for WordPress and WooCommerce traffic, or when a previous provider has quietly become unreachable. We move them onto their own server, and we run it.
Dedicated Server Management
Bare-metal box, sat in a data centre, costing real money each month — these deserve someone watching them. We'll take over a dedicated server you already have, or help you spec and procure a new one through your preferred hardware distributor and hosting provider.
The hardware itself isn't usually the hard part. The hard part is everything you put on top of it: the OS, the web stack, the database, the backup target, the off-box monitoring, the documented runbook for when the primary disk fails.
Where we operate
- Australian data centres (Sydney, Melbourne, Perth)
- NextDC, Equinix and other Australian DC tenants
- OVH, Hetzner — overseas if you've got a reason
- Your own rack, if you've got that
Out-of-band & recovery
- IPMI / iDRAC / iLO documented and accessible
- Recovery / rescue procedures tested, not assumed
- Hardware vendor case management when something fails
Common scenarios
- You bought a $20/mo VPS for a side project that turned into the business
- Your developer set the server up and then left
- You've got 3 VPSes you're not sure are still patched
- You want a dev/staging/prod split and someone to keep them aligned
- You're outgrowing shared hosting and need somewhere to go
VPS Management
VPS management is dedicated server management with smaller resources and a different bill at the end of the month. We treat them the same way: monitored, patched, backed up, documented.
We're provider-agnostic. If you're on DigitalOcean, Vultr, Linode, AWS Lightsail, OVH, Binary Lane, or somewhere we haven't heard of, we'll work with whatever's there. We can also help you move if your current host has become a problem.
Moving servers without breaking anything.
Server migrations are one of the things we do most. Old hardware end-of-lifing, a hosting provider gone bad, a cPanel box that needs to move to a bigger one, a Linux server that needs to leave OVH and land in Australia — we do this work weekly.
Map the source server
Every site, every database, every cron, every PHP version, every email account, every certificate, every IP allowlist. Written down before anything moves.
Build the destination dry
Destination server stood up to match the source. Sites copied across, databases imported, configs replicated. Test URLs (or hosts-file overrides) used to verify everything works before any DNS moves.
The window
Final delta sync. DNS TTLs lowered ahead of time. The cutover happens at the time you choose — not at the time it's convenient for us. Old server stays running until the new one is verified stable.
Old box, properly retired
Final backup taken from the source. Old server held for an agreed period in case anything was missed. Then decommissioned cleanly — not just abandoned with the bill still running.
How this is structured.
Per-server fixed fee covering monitoring, patching, business-hours response, and a defined incident SLA. Most clients sit here.
Migrations, hardening reviews, stack rebuilds, performance work. Scoped, quoted, signed off — no open-ended hourly drip.
Servers we don't manage but you need help with right now. Billed by the hour, no minimum retainer required.
Got a server you'd rather not think about?
Tell us what's running on it and what's been bothering you. We'll come back with what we'd do, what it'd cost, and whether we're the right team for the job.