Introducing LaunchKit - ShipUI Themes Upgraded to Full SaaS Starters
We built ShipUI because every Next.js starter on the internet looks the same. Seventeen themes later, the design problem was solved — but the next problem was obvious.
A beautiful landing page is not a SaaS. You still need auth, payments, a database, and email. And wiring all of that up takes longer than building the actual product.
So we built that too.
What is LaunchKit
LaunchKit is a new product line from Voltenworks. We're taking our best-looking ShipUI themes and upgrading them into full-stack SaaS applications — curated, not mass-produced. Each one is hand-picked for its design quality and then wired up with a real backend.
ShipUI gives you the frontend. LaunchKit gives you everything behind it.
The positioning is straightforward:
- ShipUI = themes for designers and developers who want a strong visual foundation
- LaunchKit = full-stack starters for developers building SaaS products
Same distinctive designs. Now with a real backend.
The Stack
Every LaunchKit starter ships with:
- Clerk authentication with fully custom UI (not the Clerk modal -- actual themed sign-in, sign-up, and account pages that match your design)
- Stripe subscriptions with a complete billing flow: checkout, portal, webhook handlers, plan management
- Neon Postgres + Drizzle ORM for the database layer, with migrations and seed scripts ready to go
- Resend for transactional emails (welcome, receipt, trial ending)
- Dashboard with real data views, not placeholder cards
- Pricing page with free and paid tiers wired to Stripe
- API routes for everything -- no "TODO: implement this" comments
- Webhook handlers for Stripe events, tested and typed
All of it themed. All of it typed. All of it works on first npm run dev after you plug in your env vars.
What You Get
Let's be specific. The first LaunchKit starter -- DECK // NEXT -- includes:
- 22 routes across marketing, auth, dashboard, billing, and API
- 3 email templates (welcome, payment receipt, trial expiration) built with React Email and sent via Resend
- Full Clerk custom UI -- sign-in, sign-up, forgot password, account settings, all matching the deck art theme
- Stripe integration with checkout sessions, customer portal redirects, webhook signature verification, and plan enforcement middleware
- Drizzle schema with users, subscriptions, and usage tables, plus a migration script
- Dashboard pages -- overview, usage, settings, billing history
- API route handlers with proper auth guards, rate limiting helpers, and error handling
- Middleware that handles auth redirects, subscription checks, and API key validation
- CLAUDE.md and .cursorrules files so AI coding agents understand the project structure from the start
deck-launchkit/
src/
app/
(marketing)/ # Landing, pricing, blog
(auth)/ # Sign-in, sign-up, forgot-password
(dashboard)/ # Overview, settings, billing, usage
api/
webhooks/stripe/ # Verified webhook handler
v1/ # Your API routes
components/
ui/ # Theme components
email/ # React Email templates
lib/
db/ # Drizzle schema, client, migrations
stripe/ # Checkout, portal, plan helpers
auth/ # Clerk helpers, middleware utils
Why Not ShipFast, Makerkit, or Supastarter
Fair question. Those are solid products. Here's where LaunchKit is different:
The design is actually unique. Most SaaS starters ship the same shadcn/ui default look with minor color tweaks. Every LaunchKit starter inherits a full ShipUI theme -- custom typography, color systems, spacing, component variants, dark mode. DECK looks nothing like NOIR looks nothing like GLASS. That's the point.
It's not generic. We don't build one boilerplate and re-skin it. Each theme's LaunchKit version is built specifically for that design system. The dashboard components, the email templates, the pricing page -- they all feel like they belong.
Security audited. Every LaunchKit starter goes through a security review. Webhook signatures are verified. API routes are auth-guarded. Environment variables are validated at build time. CSRF protections are in place. We document the security model in the README so you can audit it yourself.
AI agent files included. Every kit ships with CLAUDE.md and .cursorrules that map out the project structure, conventions, and patterns. When you hand your project to Claude Code or Cursor, the agent actually understands the codebase. This isn't an afterthought -- it's part of the build process.
You own everything. No SDK dependency. No vendor lock-in beyond the services you chose (and you can swap those). It's your code in your repo from day one.
The First Kit: DECK // NEXT
DECK is the first theme getting the LaunchKit treatment. Skate deck art aesthetic -- Permanent Marker headings, IBM Plex Mono body text, orange and yellow spray-paint accents on dark woodgrain. It's loud, it's distinctive, and now it runs a full SaaS backend.
$129. One-time purchase. Full source code. Unlimited projects.
That's less than a month of most SaaS starter subscriptions, and you get a product that doesn't look like it was generated by the same prompt as everyone else's.
What's Next
More themes are getting LaunchKit upgrades. NOIR, GLASS, and VAULT are next in the pipeline. Each one will have the same full-stack foundation adapted to its specific design language.
We're also working on LaunchKit API -- the same stack but optimized for API-first products. Docs site, API playground, usage dashboards, key management. More on that soon.
Get Started
If you're building a SaaS product and you're tired of starting from a boilerplate that looks like a boilerplate, check out DECK // NEXT LaunchKit.
Clone it. Plug in your keys. Ship something that looks like you actually designed it.