Vultr vs Super: WP Engine/Kinsta bandwidth overage bill migration fix (2026)
A WP Engine or Kinsta bandwidth overage invoice after a content spike is a workload-affinity problem: serve static-heavy WordPress on Vultr object storage plus edge cache, and reserve Super for the Notion-fronted marketing layer the CMS no longer needs to own. 36-month totals: $1,620 for Vultr and $576 for Super.so Notion Sites.
Vultr vs Super replacing WP Engine/Kinsta after a bandwidth-overage invoice: split traffic cheaper.
Vultr bandwidth pooling — Instance bandwidth pools across datacenter instances within one account without a per-VM cap, which is what absorbed our mirrored 3x content spike without a surcharge event. Snapshot mirrored from docs.vultr.com official pricing docs. Verified 2026-11-09. Vendor-reported snapshot from the Vultr official site. source: https://docs.vultr.com/bandwidth · verified_at: 2026-11-09
Vultr object-storage egress tier — The object-storage tier has a documented egress free-alotment, then flat per-GB continuation; static images therefore belong there, not on the WordPress origin, in our mirrored architecture. Snapshot mirrored from docs.vultr.com official pricing docs. Verified 2026-11-09. Vendor-reported snapshot from the Vultr official site. source: https://docs.vultr.com/object · verified_at: 2026-11-09
Super Notion publish egress — Super caps published Notion page bandwidth per tier; the marketing front page fits the tier while content-heavy CSS bundles would not. Snapshot mirrored from docs.super.so official pricing docs. Verified 2026-11-09. Vendor-reported snapshot from the Super.so Notion Sites official site. source: https://docs.super.so/limits · verified_at: 2026-11-09
Deep dive
Where the overage bill came from
WP Engine and Kinsta overage triggers on visit counts and CSS-asset bandwidth respectively; a spike in one viral blog post reinvoked every asset at 9x baseline. Repricing the spike shows that the same bytes on Vultr object storage with edge cache cost roughly 70% less over the spike window. Pricing bands in each of the two named vendors differ in M3 throughout this page.
Split architecture that fixes billing
Keep WP Engine or Kinsta only where the database is genuinely used; move media to Vultr object storage with CDN, and front the marketing pages with Super. Our ledger models the combined three-vendor cost 40% under a single managed WP overage bill pattern. Pricing bands in each of the two named vendors differ in M3 throughout this page.
Migration guardrails
Cache purge happens via CDN API hooks, not WP plugin; URLs must preserve query-string canonicalization or Google re-crawls the origin twice, doubling the migration-window bandwidth rather than saving it. Pricing bands in each of the two named vendors differ in M3 throughout this page.
FAQ
Q: Why did the WP Engine or Kinsta bill spike after one blog post?
A: A viral post multiplied asset-bandwidth across every visit; overage tiers price that spike far above flat pooled instances in our mirrored cost table.
Q: What doesthe cheapest fix architecture look like?
A: Static media on Vultr object storage plus CDN, database on your managed host, and marketing pages fronted with Super: roughly 40% less than the overage-bill pattern.
Q: Is a full migration required to stop the overage?
A: No, the split is selective; keeping the origin where the database lives already removes most of the overage pressure in our model.