A small SaaS starter. Room for your own idea.

What we mean by less bloat

A starter becomes your application's codebase. Every extra feature can introduce settings to understand, screens to customize, and behavior to check. We keep Ghoststack focused on the foundations shared by many small web apps: accounts, a database, subscriptions, and an interface you can edit.

You get a landing page, login, pricing, dashboard, and account settings. Supabase handles authentication and data access; Stripe handles subscription checkout and the customer billing portal. Email templates and a sending helper use Resend. An OpenRouter helper is available if your app needs AI text responses. These services still need your accounts and configuration.

A blog, waitlist, team workspace, or finished AI chat interface is additional work. We don't claim the starter has no dependencies or that you will never remove code. A lean starting point is a choice about scope.

A simple design framework you can build on

The interface uses Tailwind CSS and DaisyUI. Buttons, forms, cards, and theme colors follow one set of conventions. Your AI can look at nearby code and use the same patterns when adding a page. You can change the theme without replacing the app's authentication or billing code.

For example, changing a button's appearance usually starts with its DaisyUI classes and the theme settings. You don't need to adopt a second component library just to add a form. The public styling guide shows the workflow and the files involved. The framework itself is documented by DaisyUI.

What “AI-native” means here

For Ghoststack, it means ordinary project files with explicit instructions. The starter uses TypeScript and the Next.js App Router, with named locations for authentication, billing, email, and AI helpers. AGENTS.md explains the commands, conventions, and boundaries; a small Claude Code adapter shares that context.

Choose Codex, Claude Code, or Cursor and follow the corresponding setup guide. Optional MCP connection templates help your coding assistant access services after you configure and authorize them. Neither project instructions nor a template alone grants access. You can begin with a local preview before connecting any service.

Prompts let optional features stay optional

If you need a waitlist, use the waitlist guide to ask your AI to add it. If you need a blog later, follow that guide then. You get a plan for building the feature, including prerequisites and checks, without carrying every possible feature in the app from the start.

The docs live on this site, with a Markdown reference included in the starter for you and your agent. They cover setup, a first useful feature, troubleshooting, optional additions, and deployment. Read three public prompt examples to see how that differs from a bare instruction to “build my app.”

When a larger starter might fit better

If your first release requires team roles, an administration console, or several authentication methods, a starter that already includes those features deserves a look. If you enjoy assembling your own stack, starting from scratch can also make sense. Ghoststack fits someone who wants one focused starting point and guidance while learning. Our comparison pages explain those choices in more detail.