What “review” means here, and what it does not

Tool reviews on the internet have a credibility problem. Most are sponsored content dressed as opinion, most quote feature lists rather than tradeoffs, and most never mention what the tool fails at — because if you list the failures, the affiliate program will not approve you. The reviews indexed on this page are written differently. Each one is a synthesis of three sources: the vendor's public documentation, public pricing pages on the date listed, and a structured read of user reports from communities like Indie Hackers, the relevant subreddits, and Hacker News threads. The conclusion in each review is a stage-by-founder-type recommendation that tries to say honestly when the tool is the right call, when it is overkill, and when it will fail you.

This means the reviews are not first-person hands-on reviews. We do not pretend to have shipped a production app on every single tool listed; nobody has done that. The honest description of what these are is: research-based decision frameworks built from public information, written for solo founders trying to pick between tools. That framing is on every individual review page and on the editorial policy. The benefit of that approach is that we can cover 20+ tools without inventing experience we do not have. The limit is that hands-on quirks — the small DX papercuts that surface only after a month of daily use — are not always captured. Where a specific quirk is widely reported, the review names it; where it is not, the review stays silent. That is the right tradeoff for solo founders who need a fast first read on a tool, not a 90-day deep dive.

The reviews are also opinionated. Each one ends with a clear “use this tool if X, do not use this tool if Y” section. That section is the most useful part of the page and is what distinguishes our reviews from feature-comparison sites. Tools have personalities. Cursor is for founders who want IDE-shaped AI assistance with full code ownership. Lovable is for founders who want a deployable scaffold from a sentence and are willing to live with framework choices made for them. Sentry is for founders who want errors and replay in one place at a real price. WorkOS is for founders chasing their first enterprise deal and only want to handle SAML SSO once. The personality of each tool determines which kind of founder should use it, and the reviews say so directly.

Methodology

Every review is dated. Every pricing claim is sourced from the vendor's public pricing page as of the review date. Every strength and weakness is supported either by official documentation or by repeated reports in public user communities — we do not invent. Where the review includes an affiliate link to one of the reviewed tools, it is disclosed inline and never alters the recommendation. Reviews are re-dated and reviewed when a vendor ships a material pricing or product change. Last reviewed May 2026.

AI build tools

This is the category that has changed the most in the last twelve months and is changing again as you read this. The five reviews in this group cover the canonical players: Lovable (prompt-to-app generator with Supabase under the hood), Cursor (VS Code fork with deep AI integration and the dominant AI code editor for serious code), Bolt.new (browser-based AI app builder from StackBlitz), Windsurf (Codeium's editor with the Cascade agent for autonomous multi-step work), Replit (cloud IDE with AI Agent and built-in Postgres), v0 by Vercel (UI generator from a prompt, shadcn-quality), and Continue.dev (open-source BYO-model AI extension for VS Code).

The decision rarely comes down to “which is best.” It comes down to “which two should I use, in what order.” A solo founder who scaffolds with Lovable, then iterates in Cursor, then deploys via Vercel has a perfectly reasonable stack. A solo founder who scaffolds with Bolt and iterates in Replit has a perfectly reasonable different stack. The Continue.dev review covers the BYO-model angle for founders who care about either cost discipline or being able to swap models. Read each review for the “use this if” section — that is where the picking happens.

Auth

Two auth products are reviewed individually: Better Auth (a framework-agnostic, MIT-licensed library that is the Auth.js challenger) and WorkOS (SAML SSO and SCIM as an API for founders chasing their first enterprise deal). The Better Auth review is for founders who want to own their auth code rather than rent it; the WorkOS review is for founders who have a $40K enterprise deal in their inbox conditional on supporting SAML and want to ship it in a week without becoming an identity expert. These are different problems for different founder stages. Read the WorkOS review specifically if you are in the position of being asked for SSO — the “sso.tax” debate has settled, and the honest answer is to use WorkOS or Clerk Enterprise rather than build the plumbing yourself.

Email

Loops is the single tool reviewed individually in this section, and it is reviewed because it represents a category bet most solo founders have not made: unifying transactional and marketing email under one platform. The traditional advice is to keep them separate because the deliverability profiles differ. Loops argues that the line is artificial for solo SaaS and that you should be able to send a welcome email, a billing-failed email, and a product-launch email from the same audience system. The review takes a position on whether that bet pays off for a solo founder. The short answer in 2026 is: yes, for the right shape of SaaS, and the review documents which shape.

Background jobs

Background jobs is a category where the right answer is to use Vercel Cron until you can't, and to switch to a real durable-runs platform when you start needing fan-out, step-level retries, or long-running work. The two reviews here cover the two best options. Trigger.dev is durable runs with self-host and a polished SDK; Inngest is event-driven fan-out with a different mental model. Both are excellent. The reviews are written so that you can read either one and end up with a decision; the head-to-head comparison is linked from each and is the right next stop if you have not committed yet.

Observability

Solo founders need exactly one observability tool, and most of them install three and look at none. The Sentry review covers the one tool that is the right default for almost all solo SaaS: error tracking, performance traces, and session replay for Next.js in a single SDK. The free tier covers most early-stage SaaS by event volume, and the noise filters needed to keep it from turning into Slack spam are documented in the review. Most founders should install Sentry on day one, configure the noise filters by week one, and not think about observability tooling again until they are at $10K MRR or have a specific reliability incident that motivates more.

Boilerplates

Boilerplates is a category where the answer is “buy one only if you would not otherwise build the same thing in less than four billable hours,” and the two reviews here cover the two boilerplates most worth comparing in that frame. ShipFast at $199 is the cheap option, written by Marc Lou, optimized for Next.js solo founders who want a working app shell with Stripe and email and a couple of marketing pages in an afternoon. Makerkit at higher tiers is the production-ready option, with multi-tenancy and RBAC and team accounts wired in for B2B SaaS founders who are going to need that plumbing anyway.

Each review covers the exact list of what ships in the box and the exact list of what does not. Each review also covers the hidden cost most founders forget: the mismatch debt. If the boilerplate's defaults do not match your product's shape, you pay in code-deletion time on day one and update conflicts on every future boilerplate release. The reviews are honest about when that cost is small (and the boilerplate pays for itself) and when it is large (and you would have been faster from scratch).

Analytics

PostHog is the one analytics product reviewed individually in this index, because it is the only one that does enough by itself to deserve a long-form review. Events, funnels, session recording, feature flags, A/B testing, and product analytics in one SDK on a 1-million-events-per-month free tier. The honest take in the review is that PostHog is overkill for the first $1K MRR of most solo SaaS but is the right install for any product that depends on understanding user behavior at scale — AI tools, productivity apps, anything with an onboarding funnel longer than two steps. The review documents the autocapture cost trap (autocapture explodes event volume; the free tier survives it but barely) and the reverse-proxy fix for ad-blocker-friendly tracking.

Collaboration

Liveblocks is the one tool reviewed in this section because real-time collaboration is the rare layer where solo founders should not build their own infrastructure. Presence, multi-user cursors, Yjs document sync, threaded comments, AI copilots — building any of these from scratch with WebSockets and a CRDT library is a six-month side quest. Liveblocks gives you all of it as an API. The review is for founders building anything Figma-shaped, Notion-shaped, or co-editing-shaped: the price is real, the time saved is also real, and the comparison is to a six-month project rather than to a cheaper SaaS vendor.

Backend

Convex is the one backend reviewed individually in this index, because it is genuinely different from the Supabase / Firebase / Neon options that dominate the head-to-head comparison content. Convex is a reactive backend with end-to-end TypeScript: queries that re-run automatically when their data changes, scheduled functions in the same language, and file storage in the same SDK. The review documents where Convex beats Supabase (real-time apps and end-to-end TypeScript discipline are the headline wins), where it does not (Postgres ecosystem depth, RLS familiarity, raw SQL), and which founder type should pick it. Convex is the right call for a small but specific slice of solo SaaS — primarily collaborative tools and apps where real-time is core — and the review names that slice directly.

Get one SaaS build breakdown every week

The stack, prompts, pricing, and mistakes to avoid — for solo founders building with AI.