Launching today
Pinery Static
Turn WordPress into a static site on Cloudflare Pages
4 followers
Turn WordPress into a static site on Cloudflare Pages
4 followers
Pinery Static exports WordPress to HTML and deploys to Cloudflare Pages in one click — pure PHP, no Node/CLI. Comments, search, forms and WooCommerce still work. Free: full export + deploy, no page limit. Plus ($59.99 one-time) adds auto-deploy; Pro ($299) adds live WooCommerce prices and stock. ⭐⭐⭐⭐⭐ "A satisfied customer." — heathtom, who hired me on Fiverr to migrate his WordPress blog (~200 pages) to a static site on Cloudflare Pages. He even tried to tip me after delivery.
Hi everyone, I'm the solo developer behind Pinery Static.
Last week someone shared one of my older posts in a bigger group, and traffic jumped from the usual couple hundred visits a day to a few thousand in one afternoon. Normally that sentence ends with me staring at a database connection error while upgrading the hosting plan in a panic. This time nothing happened — the public site is just static files on Cloudflare Pages, so there's no database to fill up and no PHP workers to run out. That's Pinery Static at work on my own site.
Pinery Static exports your WordPress site to plain HTML and deploys it to Cloudflare Pages in one click. It's pure PHP — no Node, no wrangler, no command line — so it runs on ordinary shared hosting. You keep editing in WordPress like always; visitors just get static pages from 300+ edge locations.
Why I built it: the established exporters either charge a yearly subscription, limit the free version to exporting a ZIP file you still have to deploy yourself, or openly say WooCommerce stores aren't a fit. I wanted deployment included in the free plan, and shops supported properly.
What's in it:
- Free plan: full export AND deploy to Cloudflare Pages, no page limit
- Plus ($59.99 one-time): auto-deploy on publish, comments/search/forms keep working through WordPress, WebP conversion, same-domain switch with one-click rollback
- Pro ($299 one-time): adds live WooCommerce prices, stock and add-to-cart on static product pages
On our demo shop the static copy loads in 0.09s vs 1.6s for the WordPress original (median of 27 locations).
Honest limitations, because someone will ask: it only deploys to Cloudflare Pages, and your WordPress stays online (cheap hosting is fine) to serve wp-admin and the live features. It's a static front end, not a WordPress replacement.
How it got battle-tested: my first paying customer came from Fiverr — heathtom hired me for a $299 done-for-you migration. His author blog, 200+ pages, moved off WordPress onto Cloudflare Pages as a static site, with the broken bits (post titles, images, header, contact form) fixed along the way. He left a 5-star review, said "Looks great - thanks!", and told me I could mention the job and call him a satisfied customer. That one order drove 20+ plugin iterations — it's why Pinery is this solid now.
And a timely note: with this week's php2shell PHP vulnerabilities (two unauthenticated RCEs, CVSS 9.2), a static front end has a nice side effect — public visitors never touch PHP at all. Patching is still the real fix; we wrote up the details on our site.
Happy to answer anything — especially from WooCommerce folks and anyone with a huge content site. What would stop you from taking your site static?