Next.js SaaS Starter vs boxyhq/saas-starter-kit vs wasp-lang/open-saas: Comparing Three Official Skeletons

1. Positioning differences

| Project | Positioning | Complexity | Learning cost | AI friendliness |
|------|------|--------|---------|---------|
| Next.js SaaS Starter | Official, most lightweight entry | Low | Low | Very high |
| boxyhq/saas-starter-kit | Enterprise-grade reference | High | High | Medium |
| wasp-lang/open-saas | Full-stack type safety | Medium | Medium | Very high |

2. Recommendations

**Choose Next.js SaaS Starter if:**
- You are a SaaS beginner
- You want to build an MVP or demo quickly
- You prefer a lightweight, standard Next.js project
- You iterate rapidly with Claude Code / Cursor
- Best fit recommended by this list

**Choose wasp-lang/open-saas if:**
- You need full-stack type safety and complete examples
- You want the structured approach of a next-generation framework
- Your project needs background jobs and file management
- You want one-click deploy to Railway / Fly.io
- Highest AI friendliness, good for deep AI coding

**Choose boxyhq/saas-starter-kit if:**
- You are learning enterprise SaaS architecture
- You need SSO, SAML, audit logging and similar features
- Your team is large and needs complex permission management
- Your production environment needs these features from the start

3. Tech stack comparison

| Item | Next.js | boxyhq | Wasp |
|--------|--------|--------|------|
| Framework | Next.js | Next.js | Wasp Lang |
| Backend | Node.js + Route Handlers | Node.js | Node.js |
| Database | PostgreSQL | PostgreSQL | PostgreSQL |
| ORM | Drizzle | Prisma | Prisma |
| Auth | Custom | NextAuth.js | Wasp Auth |
| Styling | Tailwind + shadcn | Tailwind | Tailwind |
| Type safety | TypeScript | TypeScript | Full-stack type checking |
| Tests | None | Yes | Yes |
| Docs | Good | Complete | Excellent |

4. Developer experience comparison

| Scenario | Recommended | Reason |
|------|------|------|
| Add a new page + data table | wasp-lang | Framework-generated, fully type-safe |
| Configure Stripe | Next.js | Least configuration, focus on integration logic |
| Implement an RBAC system | boxyhq | Complete examples and best practices |
| Rapid AI coding iteration | Next.js and wasp | Concise code, clear structure |
| Learn SaaS concepts | Next.js | Least distraction, focused on the core |

5. Suggested path

**MVP stage (1-3 months):**
Use Next.js SaaS Starter + Claude Code
- Ship core features quickly
- Focus on product iteration, not architecture details
- Highest AI-assisted development efficiency

**Validated and scaling (3-6 months):**
Migrate to wasp-lang/open-saas, or refactor up to boxyhq level
- If you need a complex permission system, go boxyhq
- If you need full-stack type safety + deep AI development, go Wasp

**Learning enterprise architecture (research):**
Study boxyhq/saas-starter-kit
- Not necessarily for production, but good for learning industry best practices
- Permission design ideas for larger, multi-person teams