The Problem
What pain point this idea addresses
In modern web development using a headless CMS (like Contentful or Sanity), Next.js with Incremental Static Regeneration (ISR), and Vercel hosting, a critical and frustrating problem frequently occurs: stale content. A content editor spends time crafting a blog post, correcting a typo, or updating a product price. They hit 'publish' in the CMS, and a webhook is supposed to trigger a cache invalidation on Vercel's edge network. However, this process is often a 'black box' and notoriously brittle. The webhook might fail silently, the logic for determining which cache tags to purge might be incorrect or incomplete (e.g., updating a post should clear the post page, the homepage, and the author's page), or a Vercel deployment might reset the cache unexpectedly. The result is the same: the old, incorrect content remains live. The content editor is frustrated, believing their work is lost or the system is broken. They file a support ticket. The developer then has to drop everything to debug a distributed system, sifting through CMS webhook logs and Vercel deployment logs, trying to figure out why the invalidation failed. This wastes hours of expensive developer time and erodes trust between the content and engineering teams.
Real-world signals
Reddit
Our headless CMS + Next ISR deploys are slow — editors publish blog posts but cache tags never invalidate on Vercel edge.
The Solution
How the product solves the problem
PurgeLink is a managed middleware service that sits between your headless CMS and Vercel, providing a reliable and transparent cache invalidation workflow. Instead of pointing your CMS webhooks directly at your Next.js app, you point them to a unique PurgeLink endpoint. Within the PurgeLink dashboard, you create simple, powerful rules to map incoming webhook data to Vercel cache tags. For example: 'When a 'blogPost' entry is published in Contentful, invalidate the cache tags: `homepage`, `blog-index`, and `post:${entry.slug}`.' PurgeLink intelligently constructs the correct API call to Vercel's cache invalidation endpoint. The core value lies in its observability and reliability. PurgeLink provides a live, real-time log of every incoming webhook, how it was processed by your rules, and the success or failure of the resulting Vercel API call. No more black boxes. If an invalidation fails, PurgeLink can automatically retry and send an alert via Slack or email. It turns a brittle, custom-coded script into a robust, configurable, and fully managed part of the content delivery pipeline, giving developers peace of mind and content editors the confidence that their updates will go live instantly.
Target Audience
Who will pay and why they care
The primary target user is a mid-level to senior Frontend or Full-Stack Developer, or a Tech Lead at a digital agency or a company with a modern web stack. This individual, let's call her 'Alex,' is 28-40 years old and is highly proficient with the Jamstack ecosystem, particularly Next.js, Vercel, and at least one headless CMS. Alex values efficiency and hates wasting time on repetitive, low-level debugging. Her pain is acute because the 'stale cache' problem is a high-visibility failure that m…
Why This Can Win Fast
Speed-to-traction advantages
PurgeLink solves a niche, but intensely painful, problem for a highly-connected and vocal community: Next.js and Vercel developers. This group actively shares tools and solutions that make their lives easier. Growth will be driven by word-of-mouth. A developer who fixes their nagging cache issues in 10 minutes with PurgeLink will eagerly share it in their team's Slack, on Twitter, or in a relevant Discord channel. The product is not a 'nice-to-have,' but a critical piece of infrastructure for a…