A production server
set up correctly.
From day one.
LiteSpeed, JetBackup, CloudLinux, Imunify360, and a correctly configured mail stack. Not a default install — a deliberate baseline that doesn't require cleanup later.
Every layer, deliberate.
Nothing left at defaults.
Kernel Stack Setup is a complete production baseline for a single server. Here's what gets installed, configured, and documented.
LiteSpeed / LTS Installation
JetBackup + Backup Policy
CloudLinux Manager
Imunify360
Mail Stack — SPF / DKIM / DMARC
Handover Documentation
What's running,
and why each layer matters.
Every component has a specific role. Nothing is installed because it's popular — each layer solves a concrete problem in production.
LiteSpeed Web Server
PHP (LTS) + MySQL / MariaDB
CloudLinux + CageFS
Imunify360
JetBackup
Mail — SPF / DKIM / DMARC
Email that doesn't
land in spam.
SPF, DKIM, and DMARC are not optional extras. A server without correct mail authentication will see its outbound email rejected or silently discarded — often without any error visible to the sender.
-
No SPF record Anyone can send email pretending to be your domain. Receiving servers see no policy, treat it as suspicious.dig TXT yourdomain.com
; no SPF record found -
No DKIM signature Messages arrive unsigned. No cryptographic proof that they came from your server. High spam score.DKIM-Signature: none
Authentication-Results: dkim=fail -
No DMARC policy Receiving servers have no instruction for what to do when authentication fails. Most default to accepting anyway — or silently dropping.
-
SPF published and verified DNS TXT record defines exactly which servers are authorised to send on behalf of your domain.v=spf1 ip4:your.server.ip include:_spf.domain.com ~all
-
DKIM key generated and signed Private key on the server signs outbound messages. Public key published in DNS for receivers to verify.DKIM-Signature: pass
Authentication-Results: dkim=pass -
DMARC policy active Policy published telling receivers to quarantine or reject messages that fail SPF and DKIM. Reporting enabled so you can see authentication results.
A default cPanel install
is not a production environment.
Most servers ship with sane defaults for a reason — they work for the average case. Production hosting is not the average case. Here's what's missing out of the box.
-
✗
No account isolationAll accounts on the server share the same OS namespace. A vulnerable site can read files from other accounts.
-
✗
No active malware protectionImunify is not included by default. Infections go undetected until they cause visible damage or get flagged by a visitor's browser.
-
✗
Backup strategy undefinedcPanel's built-in backup is often misconfigured, stored locally (not useful for server failure), and not tested for restore reliability.
-
✗
Mail records missing or wrongSPF, DKIM, and DMARC require deliberate DNS configuration. Not done by default. Not verified automatically.
-
✗
No handover documentationThe person who set it up knows what they did. When they're gone, so is that knowledge.
-
✓
CloudLinux CageFS isolationEvery account runs in its own cage. Resource limits enforced. File system visibility restricted. Standard on Kernel Stack.
-
✓
Imunify360 active and configuredMalware scanner, WAF, and intrusion detection running — configured to act on findings, not just log them.
-
✓
JetBackup with documented policyRemote backup destination, tested restore path, retention schedule documented. You know exactly what's protected.
-
✓
SPF / DKIM / DMARC verifiedAll three DNS records published and confirmed. Authentication passes on setup day — not weeks later after diagnosing delivery failures.
-
✓
Written handover documentationEverything documented — versions, configuration decisions, what to watch. Readable by the next person who has to manage this server.
What's covered.
What's quoted separately.
Kernel Stack Setup is a single-server, single-environment engagement. Here's the exact boundary.
- LiteSpeed / LTS installation + baseline config
- JetBackup installation + backup policy documentation
- CloudLinux Manager + CageFS configuration
- Imunify360 installation + configuration
- Mail service setup (SPF / DKIM / DMARC)
- Google Workspace basic setup (optional)
- Handover documentation
- CloudLinux / Imunify / JetBackup licenses (your account)
- Multiple servers or environments
- Complex multi-server or load-balanced topologies
- Redis / object cache setup (→ Kernel Boost)
- Ongoing managed hosting (→ Kernel Host)
- WordPress maintenance (→ Kernel Care)
- Site migration (→ Kernel Deploy)
Build on a foundation
that holds.
Send us your current setup — panel, OS, what's already installed — and we'll confirm scope, what licenses you need, and what the engagement looks like.