Technical writing, including our own mistakes

What we publish and what we refuse to

Most hosting blogs exist to rank for commercial keywords, which produces a recognisable genre: the ten-best-hosts listicle where the publisher happens to be first, the "ultimate guide" assembled from other people's guides, the tutorial written by someone who has never run the software. We are trying to write the other thing.

What goes on the blog

• Benchmarks with full methodology, published as ranges across many runs, including the results that do not flatter us.
• Debugging stories from real support tickets, anonymised, where the diagnosis was interesting.
• Post-mortems of our own incidents over fifteen minutes, covering what we got wrong.
• Guides written by the engineers on the support rota, tested against our current images.
• Opinion pieces on industry practices, clearly labelled as opinion.

What does not

• Listicles ranking hosting providers, particularly ones where we would appear.
• Content written backwards from a keyword rather than forwards from something worth saying.
• Guides for software we do not run, assembled from documentation we have not tested.
• Guest posts submitted for link-building purposes.
• Anything claiming a hosting change will directly improve your search rankings, which is a claim nobody can honestly make.

The practical consequence is that we publish less than most hosting companies, roughly two or three pieces a month rather than fifteen. We think that is the right trade. A blog nobody reads twice is not an asset.

Performance, Core Web Vitals and what actually moves rankings

Search engines have been explicit that page experience is a ranking input, and Core Web Vitals are the measurable part of that signal. What gets lost in most web hosting blog marketing is which of those metrics hosting can genuinely influence. Being precise about it saves you money, because it tells you when to buy a bigger article and when to fix your front end instead.

Read that table honestly and a useful rule emerges: hosting owns the first 200–400 milliseconds and your front end owns most of what follows. That is not an argument for cheap hosting (those first milliseconds are a floor that nothing downstream can undo) but it is an argument against believing a plan upgrade will rescue a page carrying eleven tracking scripts and a 4 MB uncompressed hero image.

The caching layers we ship enabled

KryoHost our writing ships with a caching stack that is configured on day one rather than left as an exercise. Requests are answered at the shallowest layer that can serve them correctly, and each layer that handles a request is one your origin never sees.

1. Edge CDN: 120+ points of presence serve static assets from the PoP nearest your visitor, typically within 10–30 ms.
2. Full-page cache: LiteSpeed Cache stores rendered HTML in RAM, so repeat visits skip PHP and the database entirely.
3. Object cache: Redis keeps expensive query results and transients in memory instead of round-tripping to MySQL.
4. OPcache: compiled PHP bytecode is held in memory, removing parse and compile cost from every request.
5. Browser cache: long-lived immutable headers on fingerprinted assets mean returning visitors re-download almost nothing.

Compression and protocol choices are handled at the edge too. Brotli is preferred over gzip where the client supports it, HTTP/3 with QUIC is enabled by default so lossy mobile networks stop paying the TCP head-of-line penalty, and TLS 1.3 removes a full round trip from the handshake. None of these require a support ticket; they are the default configuration on every article.

The infrastructure behind KryoHost KryoHost Blog

Every conversation about web hosting blog eventually comes back to hardware, and for good reason. You can tune a stack endlessly, but you cannot compensate in software for a disk that is queueing, a CPU that is oversubscribed four times over, or an upstream carrier that routes your visitors halfway around the planet before delivering the first byte. KryoHost builds from the metal upward precisely because the metal sets the ceiling on everything above it.

Our our writing fleet runs on dual-socket AMD EPYC and Intel Xeon Scalable nodes with ECC memory, paired exclusively with enterprise NVMe drives in RAID-10. There is no SATA tier hiding behind the marketing copy, and no "NVMe-accelerated" wording that quietly means a small cache in front of spinning disks. NVMe changes the character of a server rather than simply making it faster: random read latency drops from milliseconds to microseconds, so the database queries that dominate page-generation time on websites, servers and infrastructure decisions stop being the bottleneck. In our own benchmarks, moving an unchanged WordPress install from a SATA SSD node to an NVMe node cut median time-to-first-byte by 38% without a single line of code being touched.

Capacity planning is the unglamorous half of the story. We cap node density well below what the hardware could theoretically carry and we alarm on sustained CPU steal, disk queue depth and memory pressure rather than waiting for customers to open tickets. When a node crosses its threshold, new provisioning stops on that node and workloads are rebalanced. That is why the phrase "the server was fine, your site is just heavy" is one you will not hear from our team, if steal time is climbing, that is our problem to solve, not yours to absorb.

Network, peering and routing

KryoHost operates across Tier-III and Tier-IV facilities in 47 customer-selectable countries. Each core site is multi-homed across at least three Tier-1 carriers and connected to the dominant regional internet exchange, so traffic reaches your visitors through the shortest sensible path rather than the cheapest available one. Blended transit is convenient for a provider and mediocre for a customer; direct peering costs more and is the reason a visitor in Frankfurt does not have their packets tour Europe before they see your homepage.

• Redundant power: N+1 UPS with diesel generators tested under load monthly, not merely started and logged.
• Redundant cooling: hot/cold aisle containment with N+1 CRAC units and independent chilled-water loops.
• Redundant network: no single upstream carries more than 40% of a site's traffic, so losing one is a re-route, not an outage.
• Physical security: biometric access control, mantraps, 24/7 on-site security and 90-day CCTV retention.
• Independent audit: facilities hold SOC 2 Type II and ISO 27001 certification, with reports available to enterprise customers under NDA.

The practical effect of all this is measurable rather than decorative. Our published 99.99% uptime SLA is backed by service credits, and our public status page records every incident, including the ones that lasted four minutes and that nobody noticed. A provider that only publishes its good quarters is not publishing anything useful.

Security, backups and disaster recovery

Most sites are not compromised by a determined attacker studying them for weeks. They are compromised by automated scanners walking the entire IPv4 space, trying known plugin vulnerabilities and credential lists against everything that answers on port 443. Defence against that reality is layered and mostly boring, which is exactly why it works, and why it should already be switched on when your article is delivered rather than sold as an upsell after the incident.

What runs by default

• Web application firewall: ModSecurity with continuously updated OWASP and vendor rule sets, tuned per stack to keep false positives low.
• Malware scanning: Imunify360 scans on write and on schedule, quarantines known-bad files and can auto-clean common injections.
• Brute-force protection: progressive rate limiting and automatic IP throttling on login endpoints, SSH and mail services.
• DDoS mitigation: always-on L3/L4 scrubbing at the network edge, with L7 protection available on request.
• Account isolation: CageFS confines each account to its own virtualised filesystem, so one compromised neighbour cannot read another's data.
• Free TLS: automatically issued and renewed certificates with modern cipher suites and HSTS available in one click.
• Patched kernels: KernelCare applies security patches without reboots, removing the trade-off between staying current and staying up.

Backups, and what they actually cover

Website files on every article are backed up twice a week, with email accounts backed up on a separate schedule so both are protected without either job blocking the other. You can also generate and download a full account backup at any time from cPanel, and our support team can help with a restore if you need one.

A twice-weekly schedule is not the same as continuous protection, and we would rather you knew that than assumed otherwise. If you publish or sell something several times a day, keep your own more frequent backup for the hours between our scheduled runs, particularly for a database that changes constantly, such as an order table.

Compliance-wise, our infrastructure supports GDPR data-residency requirements through EU-only regions, and we sign Data Processing Agreements on request. For workloads touching payment data, our environment is PCI-DSS ready, you still own the compliance of your own application, but the platform underneath will not be the reason an assessment fails.

Support that answers the question you actually asked

Support is where hosting companies quietly differ most, and where the difference is hardest to evaluate before you buy. Every provider claims 24/7 availability. Far fewer will tell you who is on the other end at 03:00 on a Sunday, how many tickets that person is holding, or what percentage get resolved without being escalated into a queue you cannot see.

KryoHost staffs Linux system administrators across three timezones. There is no offshore first line whose job is to send you a knowledgebase link and close the ticket. Our commitment is a first response inside < 15 min on anything service-affecting, escalating automatically to on-call if that is missed. When something does need a second pair of hands it moves to a named senior engineer and you are told who owns it, not dropped into a silent queue.

What is included, and what is genuinely out of scope

Being clear about scope up front prevents the most common support frustration: discovering after an incident that the thing you assumed was covered never was.

Support reaches you through live chat, tickets and email, and (on business and VPS plans) a scheduled screen-share call when something genuinely needs a live conversation. The same standard of engineer answers at any hour, which matters more than it sounds when you are describing an intermittent fault under pressure at two in the morning.

KryoHost Blog terminology, decoded

Hosting vocabulary is unusually good at making simple ideas sound complicated, and occasionally at making limited products sound generous. Here is what the terms on a web hosting blog comparison page actually mean in practice.

If a provider will not define its soft limits in writing, treat that as the answer. Ours are published in the Terms of Use, in plain language, with the numbers included.