Better Fullstack Starter Packs

Starter packs are opinionated paths through Better Fullstack. Use them when you know the product outcome you want before you know every library choice.

Each pack explains what to create, which stack it uses, how to generate it, and what to change first after scaffolding.

Choose a pack

Sell subscriptions

SaaS App

Next.js with auth, relational data, payments, email, and a deployment-ready app shape.

For Founders validating paid products

Read pack guide

Build with agents

AI Agent App

A Next.js workspace prepared for AI CLI flows, MCP, skills, and generated agent docs.

For Teams building agent-assisted products

Read pack guide

Expose a service

REST API

FastAPI with SQLAlchemy, Pydantic, Ruff, and a small API-first Python project layout.

For Backend teams exposing typed services

Read pack guide

Ship Spring services

Java API

Spring Boot with security, JPA, migrations, and test coverage for backend teams.

For Java teams shipping secure APIs

Read pack guide

Prefer systems-grade APIs

Rust Backend

Axum and SeaORM for a compact Rust backend with typed persistence and observability hooks.

For Systems-minded backend developers

Read pack guide

Start native

Mobile App

Expo with Uniwind for a native-first app shell before backend services are needed.

For Product teams starting native first

Read pack guide

Move fast with CRUD

Internal Tool

TanStack Router, Hono, Drizzle, auth, and tRPC for product dashboards and admin tools.

For Teams building dashboards and admin tools

Read pack guide

When to use a pack

Use a pack when you want a strong default and a working project quickly. After generation, the Stack Builder still lets you adjust framework, database, auth, API, deployment, and tooling choices.

If you already know the exact stack, use the Stack Builder or a stack-specific guide instead.

Pack selection notes

• Choose the SaaS pack when billing, auth, and email are part of the first product version.
• Choose the AI Agent App pack when agent instructions, MCP, and app code need to evolve together.
• Choose the REST API, Java API, or Rust Backend packs when the product starts as a service boundary.
• Choose the Mobile App pack when the device experience matters before backend architecture.
• Choose the Internal Tool pack when CRUD workflows, dashboards, and authenticated operations are the product.