Wisp review

Wisp is a headless CMS for adding and managing a blog on a Next.js or React site. It separates writing and organizing posts from the codebase: teams use a visual editor rather than writing Markdown, and Wisp hosts uploaded images instead of requiring them to live in the project. The product also says it delivers content and images through a global CDN.

For developers, Wisp offers a typed Next.js SDK and code samples for connecting a site and adding SEO elements, including JSON-LD, sitemaps, and metadata. That makes it a focused option for teams that want a blog without building their own publishing workflow. It is not a general-purpose site builder in the published product details; the stated use is managing blog content for Next.js and React sites.

Wisp’s appeal is the division of labor: writers get a visual editor, while developers can connect the CMS to a Next.js site with a typed SDK. Image hosting and CDN delivery are included in the product description, so teams can manage posts and their images without keeping those files in the codebase. The SEO materials cover practical implementation points—JSON-LD, sitemaps, and metadata—rather than leaving those tasks entirely unspecified.

The free tier is a useful way to start small. According to the pricing details checked on November 6, 2026, Free Forever costs $0 and includes unlimited blogs and posts, core features, and a fair-use policy. The catch is attribution: the free plan requires it. Pro removes attribution and adds early access to new features and priority email support, for $16 per user per month. There is also a $298 one-time Indie Hacker Pass for one user, with Pro features and lifetime access to current and future features; availability is listed as limited.

The free plan’s unlimited blogs and posts do not mean unlimited use: Wisp also lists a fair-use policy, but the published pricing details do not define its thresholds. Attribution is required on Free Forever, which may be a deal-breaker for a business site. Removing it means moving to Pro at $16 per user each month, so team costs rise with each user. The pricing details list no annual Pro price.

Wisp is also a specific fit: its stated focus is blogs on Next.js and React. The published materials do not publish details on other frameworks, migration tools, content export, API limits, storage caps, or CDN usage limits. Those gaps matter before switching an existing blog or committing a production site; ask Wisp for the relevant limits and export path rather than assuming they are included. A 14-day free trial is listed, but the published details do not say which plan it applies to.

Wisp’s Free Forever plan costs $0 and includes unlimited blogs and posts, but it requires attribution and comes with a fair-use policy. Pro costs $16 per user per month, with no annual price listed. That is the main pricing jump: you pay per seat to remove attribution and get early access to features and priority email support. The pricing details also list a 14-day free trial, but don’t specify which plan it applies to.

The Indie Hacker Pass is a $298 one-time payment for Pro features for one user, with lifetime access to current and future features. It’s marked as limited availability. Compared with paying $16 monthly for one user, the upfront price is roughly equivalent to 19 months of Pro; there’s no published annual discount to compare against. No paid add-ons are listed. The free tier may suit a small project, but attribution is a deal-breaker if your site can’t display it.

Wisp is positioned for Next.js and React sites, and its product description says the typed Next.js SDK can be integrated with a few lines of code. That suggests a relatively direct setup for an existing site in those frameworks, but the published material doesn’t describe migration tools or a process for importing an existing blog. Check what your current CMS can export and what Wisp accepts before planning a move.

Wisp handles content and image hosting, so switching away means you’ll need a plan for both. Its data-export options and any exit tooling are not published on the vendor's site; don’t assume you can move everything in a particular format. We also weren’t given Reddit posts or comments to substantiate common reasons users leave, so we can’t report a community pattern. The clearest fit issue is framework: teams outside React or Next.js should weigh whether Wisp fits their stack before moving content.