Hostinger standards

Most plugin developers build for beefy dev environments; WBP builds for shared-hosting constraints first, then layers VPS and dedicated optimisations on top. The Hostinger entry-tier plan is the reference environment — 128 MB memory ceiling, no system cron, LiteSpeed cache in front. If a plugin ships cleanly here, it ships cleanly anywhere.

TL;DR: Baseline for shared: 128 MB memory, no system cron, chunked batches, 1 page per cron cycle, CSV imports batched at 50 rows. VPS unlocks Redis, native cron, 512 MB+ memory, and 5–10 concurrent publishing jobs.

1. Shared-hosting constraints + solutions

128 MB memory limit

WBP streams rows in chunks and flushes the object cache between batches — never loads a full dataset into memory.

No system cron

wp-cron works but is unreliable on low-traffic sites. WBP supports third-party cron services (EasyCron, Cronitor) as first-class option.

60-second execution timeout

Every batch that would exceed this is auto-split. Background queue publishes 1 page per cron cycle to stay well inside the ceiling.

CSV import size

CSV imports are batched at 50 rows per pass so a 10,000-row file streams through without hitting the timeout or the memory cap.

2. Plugin-specific adaptations

Bulk Page Publisher — chunked publishing, 1 page per cron cycle on shared. Higher throughput unlocks automatically on VPS.
WBP Security — malware scans run in slices of 500 files per pass, resuming on the next cron.
WBP Optimization — CSS/JS bundling happens once at save, cached forever; never on the request path.
Content Generation Engine — API calls to LLM providers are queued and retried, not blocking on the publish action.
No plugin loads more than its dashboard needs on any admin screen — every heavy asset is deferred.

3. VPS / dedicated enhancements

Redis object cache — Action Scheduler queues persist across restarts, cache invalidation is O(1).
Native system cron — WP-cron replaced by a system-level scheduler for predictable timing.
512 MB+ memory — chunk sizes scale up automatically; CSV batches jump from 50 to 500 rows per pass.
5–10 concurrent Action Scheduler jobs — parallel publishing at up to 10× shared throughput.
Direct MySQL access — the diagnostics plugin surfaces slow queries without needing panel tooling.

4. What we don't do

We do not require system cron. wp-cron and third-party services both work end-to-end.
We do not require SSH. Every diagnostic is a dashboard action.
We do not silently degrade on shared. If a feature needs VPS we say so before you enable it.
We do not push the memory ceiling. 128 MB is a design target, not a fallback.

5. How WBP validates against Hostinger

Every plugin release is deployed to a Hostinger baseline test site as part of CI. The test suite publishes 5,000 rows across three templates, forces cache invalidation and measures TTFB before and after. A regression on any metric blocks the release.

When Hostinger ships an infrastructure change (PHP version bump, LSCache upgrade), WBP tracks the change on the compatibility board and publishes a patch or advisory within 7 days.