Open-source project
thedevdojo/wave avatar
thedevdojo/wave

wave ships development defaults into your repo

Wave - The Software as a Service Starter Kit, designed to help you build the SAAS of your dreams 🚀 💰

6,553 stars910 forksCSSMIT

At a glance

What is it?
wave is a SaaS starter kit that lands in your own Laravel codebase rather than arriving as a dependency. Its bundled env file is a development configuration end to end, sqlite, file sessions, a sync queue, sandbox billing keys, and the npm manifest carries only two scripts.
Who is it for?
wave fits a developer who wants a billed, role-aware Laravel application as a starting point and accepts owning the resulting code. It does not fit a team expecting a Composer upgrade path, because what gets installed is a tree you maintain yourself.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly CSS, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • thedevdojo/wave6,553 ★ · +0
Star history
Repository2026-09-232026-11-15
thedevdojo/wave6.6k6.6k

0 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

There is no install command, and what you get is marked private

The installation section offers two routes, an automated installer or a manual one, and sends readers to a docs page for the steps. The README itself prints no install command. What you end up with is a Laravel application tree: app/, bootstrap/, config/, database/, lang/, public/, resources/, routes/, storage/, tests/, plus artisan, phpunit.xml, pint.json and a wave/ directory. The front-end manifest declares that arrangement in its first line:

json
{
  "private": true,
  "type": "module",
  "scripts": {
    "dev": "vite",
    "build": "vite build"
  },
  "devDependencies": {
    "@tailwindcss/forms": "^0.5.10",
    "@tailwindcss/typography": "^0.5.16",
    "@tailwindcss/vite": "^4.1.12",
    "alpinejs": "^3.4.2",
    "autoprefixer": "^10.4.19",
    "axios": "^1.15.2",
    "laravel-vite-plugin": "^1.0",
    "postcss": "^8.4.38",
    "postcss-nesting": "^12.1.1",
    "tailwindcss": "^4.1.12",
    "vite": "^6.4"
  },
  "dependencies": {
    "@tailwindcss/postcss": "^4.1.12"
  }
}

private: true is the marker that matters. The manifest is not published for consumption, because after installation the code is yours to edit and there is no upstream package to bump.

Two npm scripts, while the env file still defines Mix variables

The asset pipeline is Vite, and the script list is exactly two entries: dev runs vite and build runs vite build. Everything else is expected to come through the Laravel side. That is worth reading against the env example, which still defines MIX_PUSHER_APP_KEY and MIX_PUSHER_APP_CLUSTER, interpolated from the Pusher values above them. Those two variables belong to the older Mix-based build and have no consumer in a Vite setup. What remains in the manifest is a Tailwind 4 stack, with the Vite plugin and a PostCSS plugin listed separately, plus the forms and typography plugins, AlpineJS for behavior, axios for requests, autoprefixer, postcss-nesting and the Vite plugin that bridges to Laravel. Five config files sit at the root for this layer: tailwind.config.js, postcss.config.js, vite.config.js, theme.json and .editorconfig. Around them sit the PHP-side files: composer.json, phpunit.xml for the test configuration, and pint.json, which holds the code style settings rather than a script of your own. package-lock.json is committed next to the manifest, so the front-end dependency tree is pinned inside the repository even though the manifest itself is private. Nothing in the script list runs migrations, seeds, or clears caches, which means those stay on the artisan side of the project.

The bundled env file is a development configuration end to end

The header alone settles the tone:

code
APP_NAME=Wave
APP_ENV=local
APP_KEY=base64:8dQ7xw/kM9EYMV4cUkzKgET8jF4P0M0TOmmqN05RN2w=
APP_DEBUG=true
APP_URL=http://localhost

Note that a real application key is committed in the example file, and JWT_SECRET ships further down as the literal SeCrEtKeY. The runtime drivers are the part that matters operationally:

code
BROADCAST_CONNECTION=log
CACHE_STORE=file
QUEUE_CONNECTION=sync
SESSION_DRIVER=file
SESSION_LIFETIME=9999
SESSION_ENCRYPT=false
SESSION_PATH=/
SESSION_DOMAIN=null

QUEUE_CONNECTION=sync means queued jobs run inside the request that dispatched them, CACHE_STORE=file puts the cache on local disk, SESSION_DRIVER=file keeps sessions in files, SESSION_ENCRYPT is off, SESSION_LIFETIME is 9999, and BROADCAST_CONNECTION=log writes events to the log rather than to a socket. With APP_MAINTENANCE_DRIVER=file against APP_MAINTENANCE_STORE=database, APP_DEBUG on and LOG_LEVEL=debug, none of these defaults is meant to survive first contact with real traffic. The database block is sqlite with the server-style keys left commented out, DB_HOST=127.0.0.1, DB_PORT=3306, DB_DATABASE=database, DB_USERNAME=root, DB_PASSWORD= and DB_COLLATION=utf8mb4_unicode_ci, so moving to another engine means uncommenting and filling them in. Redis appears lower down at REDIS_HOST=127.0.0.1, REDIS_PORT=6379 and REDIS_PASSWORD=null, and yet nothing selects it.

Both billing providers are configured, and both are in test mode

Billing is the one area where the env file carries two complete credential sets behind a single selector:

code
# BILLING CREDENTIALS
BILLING_PROVIDER=stripe

PADDLE_VENDOR_ID=999
PADDLE_API_KEY=999
PADDLE_ENV=sandbox
PADDLE_PUBLIC_KEY=test_...
PADDLE_WEBHOOK_SECRET=pdl_...

STRIPE_PUBLISHABLE_KEY=pk_test_...
STRIPE_SECRET_KEY=sk_test_...
STRIPE_WEBHOOK_SECRET=whsec_...

BILLING_PROVIDER names the active one, so supporting both means maintaining both sets of variables even though only one is live. Nothing here can take a payment: the Stripe keys carry the pk_test_ and sk_test_ prefixes, the webhook secret is a placeholder, and Paddle is explicitly in sandbox with placeholder vendor and API values. Each provider also has its own webhook secret listed next to its keys. Storage and mail have the same shape, with FILESYSTEM_DISK=public and an SMTP host of smtp.mailtrap.io on port 2525.

The feature list is fourteen documentation pages, not an inventory you can read

The feature list is fourteen entries: Authentication, User Profiles, User Impersonations, Billing, Subscription Plans, Roles and Permissions, User Notifications, a Changelog, a Blog, Pages, an API, an Admin area, Themes, and Plugins. Each one is a documentation URL rather than a code pointer, and the entry that closes the list is itself a link to the full feature list. So the feature surface is something you discover by reading, not by reading the repository. The repository listing gives no breakdown of what lives inside wave/ or app/, which is where a SaaS starter kit of this size would normally put its models, its billing glue and its admin screens. Several entries carry hidden operational weight. User Impersonations and Roles and Permissions are the kind of features that usually need an audit trail. User Notifications and the Changelog imply stored history plus a read state per user, while Pages and Blog imply two overlapping content models unless you merge them. The API entry raises the other question: authentication for a public endpoint is not described anywhere in the list.

Appearance is a first-class surface, which is why CSS is the main language

The repository's detected primary language is CSS, which tells you something about where the effort sits in a Laravel product. There is a theme.json at the root next to tailwind.config.js, and the feature list treats Themes and Plugins as capabilities in their own right rather than as afterthoughts. Previewing them is part of the demo rather than something you set up locally: the demo doubles as a way to preview all the available themes. The styling stack is Tailwind 4 with the official Vite and PostCSS plugins, the forms and typography plugins for component defaults, AlpineJS for the interactive layer, and axios for requests. So front-end work happens in resources/, public/ and the theme token file, while the SaaS mechanics live in the Laravel tree beside it.

Part of the guidance sits behind one subscription

The support section names the funding route before anything else: subscribing to a DevDojo Pro account gives access to premium content intended to help you build your SaaS more quickly, and a full video series on setting up, building and configuring Wave sits behind the same subscription. The first few videos are free and the rest require it. The same section invites pull requests, and the sponsors section thanks sponsors with a referral link. So the documentation split is deliberate: the docs pages and the feature list are public, the walkthrough content is not. The repository itself carries the governance files you would expect, with CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, CLAUDE.md and LICENSE.md at the root, so contribution rules do not require the subscription.

Tag 3.1.5 is seven months behind the last push

The release record is three patch versions inside two weeks: 3.1.3 on December 31, 2025, 3.1.4 on January 2, 2026, and 3.1.5 on January 10, 2026. The repository is not archived and its last push is dated July 31, 2026. That leaves roughly seven months of commits with no tag above them, so the code on the default branch and the code in the newest release are not the same thing, and nothing in the README states a required PHP or Laravel version to help you choose between them. For a starter kit the practical advice is to treat the installed tree as a starting point to be read rather than a version to be tracked, and to compare your own copy against the current branch before assuming it is current. The three releases sit close together, which reads as a burst of fixes rather than a published cadence.

Editorial conclusion

wave fits a developer who wants a billed, role-aware Laravel application as a starting point and accepts owning the resulting code. It does not fit a team expecting a Composer upgrade path, because what gets installed is a tree you maintain yourself. Before going live, replace the sqlite, file and sync defaults, swap the sandbox billing keys, decide whether the paid video course is worth it, and confirm that whatever is on your main branch is ahead of tag 3.1.5.

Frequently asked questions

How do I install wave?

There are two routes, an automated installer or a manual installation, and the full instructions live on the documentation site rather than in the repository.

What does wave give me out of the box?

Authentication, user profiles, user impersonations, billing, subscription plans, roles and permissions, notifications, a changelog, a blog, pages, an API, an admin area, themes, and plugins. Each is documented on its own docs page.

Why is my wave application not processing queued jobs?

The shipped env file sets QUEUE_CONNECTION=sync, so jobs run inside the request that dispatched them instead of on a worker. It also sets CACHE_STORE=file and SESSION_DRIVER=file.

Can wave take real payments as installed?

No. BILLING_PROVIDER selects the provider, but the shipped Stripe keys carry pk_test_ and sk_test_ prefixes and Paddle is set to sandbox with placeholder vendor and API values, so real credentials have to replace them.

What build tooling does wave use for assets?

Vite with Tailwind 4. The manifest exposes only dev, which runs vite, and build, which runs vite build, with the Laravel Vite plugin, a PostCSS plugin, AlpineJS, axios, autoprefixer and postcss-nesting as dev dependencies.

Is the wave video course free?

The first few videos are free, and the rest require a DevDojo Pro subscription. That subscription is also how the project describes its own funding, alongside sponsors.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. thedevdojo/wave on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/thedevdojo-wave.svg)](https://hysenlabs.com/projects/thedevdojo-wave)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/thedevdojo-wave.svg)](https://hysenlabs.com/projects/thedevdojo-wave)

Was this useful?