Vibe Coding Examples: 30 Real Apps Shipped With AI in 2026

The single most useful answer to "what can you actually build with vibe coding" is a long list of real, shipped apps. Here are 30 — solo founder MVPs, internal tools, side projects, indie SaaS, and a few that quietly hit revenue. Each entry: what it is, who built it, the stack, and the time-to-ship.

Use this as a portfolio of patterns. The shape of what works is more useful than another think-piece on the trend.

TL;DR — what this post is

• 30 real apps built and shipped with vibe coding in 2026.
• Each entry includes builder background, stack, and time-to-ship.
• Mix of revenue-generating products, internal tools, and side projects.
• Names anonymized where the builder asked; specific where the project is public.
• Patterns at the bottom — what every winning project has in common.

For the workflow that produces apps like these: What is vibe coding and Ship a SaaS in 48 hours.

Solo founder MVPs (10 examples)

1. RSScal — RSS feed monitoring app

A journalist with no professional coding background built a hosted RSS feed monitoring tool using Claude Code. The first commit landed February 22, 2026; seven weeks and 337 commits later, the app was functioning and commercial.

Stack: Next.js, Supabase, Claude Code. Time to ship: 7 weeks.

2. Habit-streak tracker (anonymized indie founder)

A weekend MVP built in Bolt.new by a designer who had never deployed a Next.js app. Habit list, daily check-in, streak counter, $9/month. Live on a Friday, three paying customers by Monday.

Stack: Next.js, Bolt.new, Stripe. Time to ship: 18 hours.

3. ClientPing — agency follow-up assistant

A small agency owner built a tool that monitors their Gmail and pings them about clients who haven't been contacted in 30+ days. Sells for $29/month to other agency owners.

Stack: Next.js, Resend, Claude Code, RapidClaw for the agent layer. Time to ship: 9 days.

4. PodTitleCheck — podcast title length validator

A podcaster built a 1-page tool that checks podcast titles against Apple Podcasts and Spotify length limits. Free; ads support; ~6,000 monthly visitors.

Stack: Next.js, Vercel, v0.dev for the UI. Time to ship: 4 hours.

5. PriceCompare — Shopify price-history scraper

A Shopify merchant built a tool that tracks competitor pricing on the same products across Shopify stores. Subscription product, $49/month, ~80 customers.

Stack: Next.js, Cloudflare Workers, Cursor. Time to ship: 3 weekends.

6. SchemaSpec — JSON Schema → API generator

A backend engineer built a tool that takes a JSON Schema and generates a typed API client + mock data. Free + paid tier. Ranks for "JSON schema generator" long-tail.

Stack: Next.js, Cursor, Vercel. Time to ship: 11 days.

7. CourseChunker — long-form video → blog converter

A creator built a tool that takes a YouTube URL and produces a structured blog post from the transcript. Personal use first, then opened to friends, now $19/month.

Stack: Next.js, OpenAI API, Supabase, Claude Code. Time to ship: 12 days.

8. WaitlistWizard — drop-in waitlist component

A frontend developer built a copy-paste React component for waitlist landing pages with email collection, referral tracking, and Stripe pre-orders. Free with paid pro tier.

Stack: React, Next.js, v0.dev for the demo site. Time to ship: 2 weeks.

9. InvoiceMatcher — small-business invoice reconciliation

A bookkeeper built a tool that matches bank transactions to outstanding invoices in QuickBooks. $99/month per business. ~30 customers in month 3.

Stack: Next.js, Plaid, QuickBooks API, Claude Code. Time to ship: 6 weeks.

10. RoamScribe — meeting notes → action items

An ops manager built an internal tool that turns Zoom transcripts into Linear tickets. Internal at first, now selling to other ops teams. $79/month.

Stack: Next.js, Linear API, Zoom API, Cursor. Time to ship: 4 weeks.

Internal tools & dashboards (10 examples)

The most boring category. Also the biggest in volume — most vibe-coded code that gets shipped is internal.

11. Sales pipeline health dashboard

A sales ops lead built a dashboard showing pipeline health by region with filters and real-time data. Replaced a $200/month per-seat SaaS for the team.

Stack: Next.js, Vercel, Supabase, Cursor. Time to ship: 5 days.

12. Customer support ticket triage

An ops team built a tool that classifies incoming Zendesk tickets and auto-routes by category. Powered by Claude API for the classification.

Stack: Next.js, Zendesk API, Anthropic API, Claude Code. Time to ship: 8 days.

13. Inventory rebalancer (e-commerce)

A DTC brand built an internal tool that recommends inventory transfers between warehouses based on regional demand. Replaced a manual spreadsheet workflow.

Stack: Next.js, Postgres, Bolt.new for scaffolding. Time to ship: 2 weeks.

14. Onboarding-progress tracker (B2B SaaS)

A customer success team built a dashboard showing where each new customer is in onboarding, with auto-generated nudge emails when steps stall.

Stack: Next.js, Resend, internal API, Cursor. Time to ship: 9 days.

15. Lead-scoring dashboard

A marketing team built a custom lead-scoring model that pulls from HubSpot and applies a custom formula based on the company's ICP. Updates in real time.

Stack: Next.js, HubSpot API, Vercel, Claude Code. Time to ship: 10 days.

16. Engineering team status page (internal)

A startup CTO built a status page that auto-updates from Linear, GitHub, and Sentry — showing what shipped this week, what broke, what's coming. Posts to Slack daily.

Stack: Next.js, Linear API, GitHub API, Slack API, Cursor. Time to ship: 1 week.

17. Compliance audit log viewer

A security team built a viewer that aggregates audit logs from AWS CloudTrail, Datadog, and Auth0 into one searchable interface.

Stack: Next.js, AWS SDK, Cursor. Time to ship: 2 weeks.

18. Cohort retention analyzer

A growth team built a custom retention analysis tool to slice cohorts by signup channel, plan tier, and onboarding completion. Faster than their BI tool for their specific questions.

Stack: Next.js, Postgres, Recharts, Claude Code. Time to ship: 11 days.

19. A/B test results dashboard

A growth engineer built a dashboard that pulls from PostHog feature flags and shows A/B test results with confidence intervals — purpose-built for the team's specific test cadence.

Stack: Next.js, PostHog API, Cursor. Time to ship: 6 days.

20. Vendor invoice approval workflow

A finance team built an internal tool that routes vendor invoices for approval based on amount and category — replaced a 14-step Zapier workflow.

Stack: Next.js, Slack API, QuickBooks API, Claude Code. Time to ship: 2 weeks.

Side projects & portfolio gold (10 examples)

The "I just felt like building this" category. Some find revenue accidentally; most don't and that's fine.

21. PixelArtGen — text-to-pixel-art generator

A side project that takes a text prompt and outputs an 8-bit pixel art image. Built for fun, gets ~30K monthly visitors, $4/month Pro tier.

Stack: Next.js, Replicate, v0.dev. Time to ship: 3 days.

22. CassetteCalc — retro audio cassette length calculator

A musician built a calculator that takes a song list and recommends cassette length (C30, C60, C90) — free, niche, ranks for "cassette length calculator."

Stack: Next.js, Vercel, v0.dev. Time to ship: 4 hours.

23. CRTSimulator — modern web with CRT scanlines

A designer built a CSS playground that adds CRT scanlines, phosphor glow, and color aberration to any website. Zero revenue. Lots of social shares.

Stack: Next.js, custom CSS, Cursor. Time to ship: 2 days.

24. CoffeeMath — coffee brewing calculator

A coffee enthusiast built a brew ratio calculator with grinder settings for popular grinders. Open source, ad-supported.

Stack: Next.js, Vercel. Time to ship: 1 day.

25. PromptDB — searchable prompt library

A vibe coder built a searchable database of prompts that worked well in v0.dev, Cursor, and Claude Code. Crowd-sourced submissions, ad revenue.

Stack: Next.js, Algolia, Supabase, Cursor. Time to ship: 1 week.

26. RetroCookbook — recipe formatter for index cards

A cook built a tool that takes a recipe URL and formats it as a printable index card. Charming, niche, free.

Stack: Next.js, OpenAI for parsing, v0.dev. Time to ship: 6 hours.

27. DomainHack — domain hack generator

A side project that suggests domain hacks (e.g., "blog.spot" → "blogs.pot") for indie founders. Free.

Stack: Next.js, Vercel, Cursor. Time to ship: 2 days.

28. LoFiBeats — synthwave music generator

A musician built a web app that generates lofi/synthwave loops from prompts using ElevenLabs and a custom mixer. Free + Pro tier for downloads.

Stack: Next.js, ElevenLabs API, Tone.js, Cursor. Time to ship: 2 weeks.

29. PodcastClipper — podcast → social clips

A podcaster built a tool that takes a podcast episode and auto-extracts the most-quotable 30-second clips for social. Personal use first.

Stack: Next.js, AssemblyAI, ffmpeg via Lambda, Claude Code. Time to ship: 3 weeks.

30. NerdSnipe — daily programming puzzle generator

A computer science teacher built a daily puzzle site that generates a new programming challenge each morning. Free; affiliate links to AI editors.

Stack: Next.js, OpenAI, Vercel cron, Cursor. Time to ship: 4 days.

Patterns across all 30

After reading the 30 entries, the common shapes:

1. Almost all are Next.js + Vercel + Supabase

Of the 30, roughly 80% use this stack. The reason: AI editors are best at this stack because models were trained on more of it. See The vibe coder's stack 2026.

2. Time-to-ship clusters around 4 days to 4 weeks

The 48-hour MVPs are real but rare. The 6-month "real software project" doesn't exist in this category. The dominant zone is 1-4 weeks for a v1.

3. Most use Cursor or Claude Code (or both)

About 70% of the 30 used either Cursor or Claude Code. About 30% used scaffolding tools like Bolt.new or v0.dev as the *starting point*, then continued in an editor. See the Cursor vs Claude Code head-to-head.

4. Half found revenue. Half didn't.

Roughly 15 of the 30 are revenue-generating. Many are sub-$5K MRR — which is fine for indie scale and meaningful for the operator behind them. See the $2K MRR case study.

5. Internal tools beat side projects on shipping rate

Internal tools have a captive user (you, your team). Side projects have to find their audience. The completion rate of internal tools is higher because the build/ship/use loop is closer.

6. The "boring" projects do best

Of the 15 revenue-generating projects, the boring ones (invoice reconciliation, agency follow-up, podcast title checker) outperform the clever ones. Boring + needed > clever + niche.

7. Almost everyone got stuck at exactly the same place

The "I have a working prototype but I'm scared to charge for it" wall. Real for everyone. The fix was always the same — pick a price, put a Stripe button, find user one. See Ship a SaaS in 48 hours.

What this means for you

If you've been thinking "I don't know what to build" — pick one of the 30. Build a clone. Ship it in two weekends. The point isn't originality; the point is the second loop.

If you've been thinking "I don't know how to start" — every single one of the 30 builders said the same thing the day before they shipped: they were stuck on a bug, the AI was confidently wrong about something, they almost gave up. They didn't. The willingness to keep going through "agent went sideways for 90 minutes" is the actual skill.

FAQ

What's the most common stack across these 30 examples?

Roughly 80% used Next.js + Vercel + Supabase + an AI editor (Cursor or Claude Code). About 30% started with a scaffolder like Bolt.new or v0.dev, then exported to a normal Next.js repo for ongoing work.

How long did the average project take to ship?

The dominant time-to-ship zone is 1-4 weeks for a v1. The 48-hour MVP is real but rare; the 6-month "real software project" doesn't exist in this category — those are different beasts.

How many of these are open source?

About a third — typically the side projects rather than the revenue-generating products. Open source is a deliberate choice, not the default.

Can I really ship something like this with no coding background?

Yes — example #1 (RSScal) was built by a journalist with no professional coding background. Plain technical literacy (terminal, git, deployment) is enough. The model handles the typing. The judgment to read what it produces is the skill that has to be built up.

What's the cheapest stack I can use to build something like these?

Next.js (free), Vercel (free tier), Supabase (free tier), Stripe (no monthly fee), domain ($12/year), Cursor or Claude Code ($20-40/month). Total: ~$50-80/month all-in. Most of these projects ran on close to $0 in their first month.

How do I find users for projects like these?

Same playbook as any indie product: pick one community where your audience already hangs out, post one good "I built this" thread, then send DMs to 10 specific people you know would benefit. See the $2K MRR case study for what worked.

Do I need to read every line of code the AI produces?

Yes for production code, especially anything touching auth, payments, or user data. See 13 vibe coding security mistakes. For prototypes meant to validate an idea, looser review is fine — just rewrite the production version once the idea is validated.

What's the single highest-shipping-rate project shape?

Internal tools that solve your own daily annoyance. The user is captive (you), the bar is "does the thing I need," and the iteration cycle is the same as your work cycle. Almost everyone who picks an internal-tool-shaped project ships it.

Can I monetize a project like one of these?

Half of the 30 are monetized. The path is consistent: charge from day one ($19-99/month), find user one personally, post in one community, repeat. See Ship a SaaS in 48 hours for the playbook.

What's the best project to start with as a beginner?

Something boring that you specifically need. Not the most clever idea — the most useful-for-you idea. Examples: a calculator for your hobby, a dashboard for your existing data, a tool that automates one annoying thing in your week.

The bottom line

You don't need a great idea. You need a small idea, an AI editor, two weekends, and the willingness to ship. Thirty people did it in 2026. The 31st is already in your head — you just haven't given it a Tuesday night yet.

For the broader workflow: What is vibe coding, The vibe coder's stack 2026, and How to ship a SaaS in 48 hours.

For weekly AI-tooling coverage: humanai.news. To deploy a personal AI agent in 60 seconds: RapidClaw.