What Features and Integrations Does TurboStarter Include Out of the Box?
TurboStarter is a production-ready SaaS starter kit built around a single codebase that targets three platforms at once: web, mobile (React Native/Expo), and browser extension (WXT/Vite). According to its site, it ships with authentication, billing, teams, admin, i18n, AI, analytics, CMS, email, and monitoring modules already wired up, so the practical question is whether that set covers what your project needs before you write your own. The list below reflects what the site and its documentation describe; treat it as a feature inventory to check against your own requirements, not a guarantee that every integration works identically across all three platforms.
Cross-platform development
The core differentiator is a unified codebase. The repository structure shown on the site separates apps into web, mobile, and extension, with shared logic in packages (ai, analytics, api, auth, billing, cms, db, email, i18n, monitoring, shared, storage, ui, tooling).
| Target | Stack indicated |
|---|---|
| Web | Next.js |
| Mobile | React Native (Expo) |
| Browser extension | WXT (Vite) |
If your product only needs a web app, the multi-platform scaffolding is overhead you may not use. If you plan to ship a mobile app or extension later, building on one codebase avoids a second setup pass.
Authentication
The site describes a "comprehensive auth flow" covering:
- Email/password
- Magic link
- Social login (Apple, Google, GitHub shown in the UI)
- Two-factor authentication
- Passkey login
- OTP
- Guest sign-in
This is broader than the typical email/password-only starter. Check whether your required identity providers are among the supported social logins before committing.
Billing and payments
Billing is the most detailed area in the documentation, with separate docs pages per provider:
- Web: Stripe, Lemon Squeezy, Polar, Dodo Payments
- Mobile: RevenueCat, Superwall
Supported billing models listed on the site: subscriptions, one-time payments, metered usage, per-seat, and credits, plus organization-level billing. The site also shows a code sample of a Hono billing router handling /checkout and /webhook, including order insertion, invoice email, and event tracking — useful as a reference for how checkout and webhooks are expected to be wired.
If your monetization model is something outside these five (for example, complex usage tiers with custom contracts), verify against the billing docs rather than assuming coverage.
Other modules
Beyond the headline features, the site lists these as included:
- Teams — organization/multi-user support
- Admin — admin surface
- CLI — command-line tooling
- i18n — internationalization
- AI — AI integration package
- Analytics — product analytics
- CMS — content management
- Email — transactional email (used in the billing sample for invoices)
- Monitoring — error/performance monitoring
- Storage, DB, UI, shared utilities — supporting packages
The repo also includes agent-oriented files (AGENTS.md, CLAUDE.md) and an .agents directory with commands and skills, reflecting the "AI-first" positioning.
How to decide if it fits
Work through this checklist against your own spec:
- Platforms — Do you need web only, or web + mobile + extension? The value of the unified codebase scales with how many targets you actually ship.
- Auth methods — Are your required login methods (specific social providers, SSO, etc.) in the supported list?
- Billing model and provider — Does your pricing model (subscription, credits, per-seat, metered) and your payment provider appear in the docs?
- Adjacent modules — Do you need teams, admin, i18n, CMS, or monitoring? If yes, having them pre-wired saves setup time; if no, they are extra surface area.
- Stack fit — Are you already committed to Next.js, Expo, and WXT/Vite? Adopting the kit means adopting those choices.
The site notes "Only 5 licenses left before price increase" and references 365+ founders, and pricing is handled through Lemon Squeezy checkout links. Confirm current pricing and license terms directly on the site, since these change.