Open Source 04 / 34
Wave
Wave is DevDojo's Laravel SaaS starter kit — authentication, subscription billing, user profiles, roles, and an admin, wired together so you start from a working product instead of an empty framework.
Wave is DevDojo's SaaS starter kit for Laravel. Instead of standing up authentication, billing, user settings, and an admin from scratch on every new product, you start from Wave with a running SaaS application: users can register, verify their email, subscribe to a plan, and manage their profile, while an administrator manages it all. It answers the "I have an idea, I don't want to rebuild the boring parts" problem.
Where Wave sits. Sites gives you a marketing page. The platform gives you a fresh Laravel codebase to build in. Wave gives you a complete, running SaaS product to start from — the same problem space as the Foundation packages, packaged as one opinionated app.
What you get out of the box
Wave bundles the features nearly every SaaS needs, already integrated:
| Area | What Wave provides |
|---|---|
| Authentication | Registration, login, email verification, and password reset — the full account lifecycle. |
| Subscription billing | Paid plans and recurring subscriptions, so you can charge customers on day one. |
| User profiles & settings | Editable profiles, avatars, and account settings for each user. |
| Roles & permissions | Role-based access control to separate customers, staff, and admins. |
| Admin area | A back office to manage users, plans, and content. |
| Content & pages | Blog/changelog-style content and themeable marketing pages. |
| API & tokens | An authenticated API surface for building on top of your app. |
| Themes | Swappable front-end themes so the look isn't locked in. |
The exact surface evolves across major versions of Wave; the throughline is that these pieces ship already wired together rather than as parts you assemble.
The philosophy: start from a product
Most starter kits give you a login screen and stop. Wave's premise is that the login screen is the easy 5% — the hard, repetitive part is everything that turns an app into a business: taking payment, gating features by plan, giving users a place to manage their account, and giving you a place to manage users. Wave ships those so your first commit is about your idea, not your plumbing.
That premise is exactly what the DevDojo Foundation packages generalize. Where Wave is a single, opinionated application, the Foundation breaks the same capabilities into individually installable packages — auth, billing, accounts, teams, blog, and changelog — that the platform dogfoods. Think of Wave as the "batteries included, one repo" expression of the same idea.
The stack
Wave is built on the mainstream Laravel stack the rest of the DevDojo toolbox shares, so if you know one project, you can read another:
- Laravel for the backend.
- Livewire, Volt, and Folio for reactive, page-based frontends in recent versions.
- Tailwind CSS for styling and theming.
- Alpine.js for interactivity — the same patterns standardized in Pines.
Getting the specifics right. Wave's concrete class names, routes, and configuration change between major releases. Always check the version you installed — the Wave repository and its docs are the source of truth for the APIs of your version.
When to reach for Wave
Choose Wave when:
- You're building a subscription product and want billing and accounts already working.
- You want a single, cohesive codebase rather than composing packages yourself.
- You value speed to a working MVP over maximum architectural control.
Reach for the Foundation packages instead when you want to add a single capability (say, billing) to an app you already have, or when you're building on the platform and want to pick features à la carte. For the full toolbox and how these projects relate, see the open source overview.