Hey Product Hunt — I’m Alok Deep, building ApexCache. We got tired of two bad options: sprinkle redis.del() through every service, or fight CDN cache rules that don’t understand which API routes are safe to cache. So we built a layer you put in front of your origin (usually one CNAME + TXT). You pick paths — api routes, catalog pages, even /* for public GETs if that’s your setup. GET/HEAD can be cached with TTLs you control. POST, checkout, auth, and mutations always go to your server. Default is “don’t cache unless you said so.” What you’ll notice in five minutes: Sign up → app.getapexcache.com (free tier, no card for the trial path we advertise on the site) Add a hostname → verify DNS curl -I the same URL twice → look for X-ApexCache-Status: HIT on the second request We also do purge via webhooks (and CDC if you wire it) so you’re not stuck until TTL expires. Need the gateway in your own cloud? We have a BYOC path for that — happy to point you at the docs in thread. I’ll be here all day answering questions: WordPress/Woo, Next API routes, AI products drowning in GET /models traffic, “will this cache my payment endpoint?” (short answer: not if it’s POST — and we don’t cache non-GET methods by design). Roast welcome. If something’s confusing in onboarding, tell me — that’s what launch day is for. Thanks for taking a look → getapexcache.com

ApexCache

REAL-TIME ACCELERATION FOR YOUR APIs

REAL-TIME ACCELERATION FOR YOUR APIs