Marketing sites on Vercel
Optimize hero and CMS images while keeping App Router hosting on Vercel.
Route next/image through Cache Rocket and warm URLs after every deploy.
Cache Rocket for Next.js sits beside your existing host. Keep SSR and HTML on Vercel, Netlify, or Cloudflare Pages. Install @cacherocket/next to send next/image through img.cacherocket.com with automatic width, quality, and format transforms—and warm critical URLs when you ship.
withCacheRocket wraps your Next.js config and wires a custom image loader. Absolute image URLs—or relative /public paths when you set an asset origin—are rewritten to path-based transform URLs on img.cacherocket.com so the edge can cache each size and format reliably.
Hosting, SSR, and your existing Data Cache stay where they are. Cache Rocket only optimizes and delivers images, and can warm page URLs after deploy.
Deploys wipe edge and framework caches. Use onVercelDeploy() in a Route Handler, or call warm and purge from CI, so the first real visitor after a release does not pay the cold-start cost.
The same image-opt and CDN bandwidth meters power WordPress Managed CDN when you use both—so plan quotas stay predictable in one place.
In Account → Next.js, create a site, copy the site token and API keys, and set your image host allowlist.
Add the package, wrap next.config with withCacheRocket, and set env vars on Vercel or locally.
Use next/image as usual, then point a deploy webhook at onVercelDeploy() or your public warm webhook.
Optimize hero and CMS images while keeping App Router hosting on Vercel.
Allowlist Shopify or CMS image hosts and serve resized WebP/AVIF from Cache Rocket.
Combine image CDN with post-deploy warming so releases never greet users with cold routes.
സൗജന്യ Cache Rocket അക്കൗണ്ട് സൃഷ്ടിക്കുക, ഒരു ഹോസ്റ്റ്നെയിം പരിശോധിക്കുക, നിങ്ങളുടെ സൈറ്റിനോ API-ക്കോ ഈ കഴിവ് ഓണാക്കുക.