SaaSykit is a complete SaaS starter kit built on Laravel 12 that includes everything you need to launch your SaaS business quickly. It comes with built-in subscription management, payment processing, user authentication, and a beautiful admin panel.
Key Features
Subscription & Payment Management: Support for subscription-based and one-time purchase products with webhook handling and billing setup
Multiple Payment Providers: Integrated support for Stripe, Paddle, and Lemon Squeezy
Customizable UI: Easy customization of colors, fonts, email templates, and more using TailwindCSS
Admin Panel: Beautiful admin dashboard powered by FilamentPHP
User Dashboard: Allows users to manage subscriptions, change payment methods, and upgrade plans
Multi-tenancy Option: Available with SaaSykit Tenancy for building team-based SaaS applications with user invitations and seat-based subscriptions
Authentication: Built-in user authentication with social login options
Blog System: Ready-to-use blog for content marketing and SEO
Email Integration: Support for multiple email providers with beautiful customizable templates
SaaS Metrics: Built-in analytics for MRR, churn rates, ARPU, and other key metrics
Roadmap Feature: Collect and manage user feedback and feature requests
One-command Deployment: Easy deployment powered by PHP Deployer and Laravel Forge
The Laravel SaaS starter kit that gives you the tools to launch your next SaaS today
PHP
Tailwind CSS
Turbine UI
MySQL
Lemon Squeezy
Laravel
Features:
Access Control
Auth
Billing
Blog
Emails
Landing Page
Payments
+7 more
Frequently Asked Questions
PHP
What makes PHP ideal for SaaS development?
PHP excels in SaaS development due to its robust ecosystem, strong typing capabilities, and excellent library support. PHP boilerplates leverage language-specific features to provide type-safe database queries, efficient API routing, and optimized runtime performance. The language's maturity means you get battle-tested packages for authentication, payment processing, and background jobs that integrate seamlessly.
FilamentPHP
What FilamentPHP-specific architecture patterns are implemented?
FilamentPHP boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement FilamentPHP's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows FilamentPHP's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
Laravel
What Laravel-specific architecture patterns are implemented?
Laravel boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement Laravel's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows Laravel's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
Livewire
What Livewire-specific architecture patterns are implemented?
Livewire boilerplates leverage the framework's native architecture patterns including its routing system, middleware pipeline, and controller/handler structure. They implement Livewire's conventions for separating concerns, dependency injection, and service layer patterns. The codebase follows Livewire's best practices for organizing models, views/components, and business logic to ensure maintainability as your application grows.
Alpine.js
What Alpine.js-specific component architecture is used?
Alpine.js boilerplates follow the framework's component composition patterns with reusable, atomic design components. They implement Alpine.js's best practices for component structure, props handling, event management, and lifecycle methods. The component library includes authentication flows, dashboards, data tables, forms with validation, and navigation—all built with Alpine.js's native features like hooks (React), composition API (Vue), or directives (Angular).
Tailwind CSS
What Tailwind CSS-specific component architecture is used?
Tailwind CSS boilerplates follow the framework's component composition patterns with reusable, atomic design components. They implement Tailwind CSS's best practices for component structure, props handling, event management, and lifecycle methods. The component library includes authentication flows, dashboards, data tables, forms with validation, and navigation—all built with Tailwind CSS's native features like hooks (React), composition API (Vue), or directives (Angular).
Lemon Squeezy
What Lemon Squeezy API features are implemented?
Lemon Squeezy boilerplates implement the provider's complete API suite including checkout sessions, subscription lifecycle management, customer portal, webhook event handling, and invoice generation. They use Lemon Squeezy's latest API version with proper error handling, idempotency keys, and retry logic. The integration includes Lemon Squeezy-specific features like payment intents, setup intents, subscription schedules, and tax calculation APIs.
Paddle
What Paddle API features are implemented?
Paddle boilerplates implement the provider's complete API suite including checkout sessions, subscription lifecycle management, customer portal, webhook event handling, and invoice generation. They use Paddle's latest API version with proper error handling, idempotency keys, and retry logic. The integration includes Paddle-specific features like payment intents, setup intents, subscription schedules, and tax calculation APIs.
Stripe
What Stripe API features are implemented?
Stripe boilerplates implement the provider's complete API suite including checkout sessions, subscription lifecycle management, customer portal, webhook event handling, and invoice generation. They use Stripe's latest API version with proper error handling, idempotency keys, and retry logic. The integration includes Stripe-specific features like payment intents, setup intents, subscription schedules, and tax calculation APIs.
PHP
What PHP-specific tools and libraries are included?
PHP boilerplates include the language's most popular and production-proven tools. This typically includes testing frameworks, linters, formatters, build tools, and package managers specific to PHP. You'll get pre-configured toolchains that enforce best practices, automated testing pipelines, and development environments optimized for PHP development workflows.
FilamentPHP
How does FilamentPHP's ORM/database layer work in these boilerplates?
FilamentPHP boilerplates use the framework's native ORM or query builder (Prisma, Eloquent, Active Record, SQLAlchemy, etc.) with pre-configured models for users, subscriptions, teams, and common SaaS entities. They include optimized queries, relationships, migrations, seeders, and database connection pooling. The implementation leverages FilamentPHP's specific features like eager loading, query scopes, and transaction handling for performance.
Laravel
How does Laravel's ORM/database layer work in these boilerplates?
Laravel boilerplates use the framework's native ORM or query builder (Prisma, Eloquent, Active Record, SQLAlchemy, etc.) with pre-configured models for users, subscriptions, teams, and common SaaS entities. They include optimized queries, relationships, migrations, seeders, and database connection pooling. The implementation leverages Laravel's specific features like eager loading, query scopes, and transaction handling for performance.
Livewire
How does Livewire's ORM/database layer work in these boilerplates?
Livewire boilerplates use the framework's native ORM or query builder (Prisma, Eloquent, Active Record, SQLAlchemy, etc.) with pre-configured models for users, subscriptions, teams, and common SaaS entities. They include optimized queries, relationships, migrations, seeders, and database connection pooling. The implementation leverages Livewire's specific features like eager loading, query scopes, and transaction handling for performance.
Alpine.js
How is state management handled in Alpine.js boilerplates?
Alpine.js boilerplates use the framework's recommended state management approach—whether that's React Context + hooks, Redux Toolkit, Zustand, Pinia (Vue), NgRx (Angular), or Svelte stores. They include pre-configured state slices for authentication, user data, subscriptions, and UI state with proper TypeScript typing. The implementation follows Alpine.js's patterns for global state, local component state, and server state synchronization.
Tailwind CSS
How is state management handled in Tailwind CSS boilerplates?
Tailwind CSS boilerplates use the framework's recommended state management approach—whether that's React Context + hooks, Redux Toolkit, Zustand, Pinia (Vue), NgRx (Angular), or Svelte stores. They include pre-configured state slices for authentication, user data, subscriptions, and UI state with proper TypeScript typing. The implementation follows Tailwind CSS's patterns for global state, local component state, and server state synchronization.
