Also Read: Gaming and News
Introduction
Most Laravel apps eventually need comments, on a blog post, a product page, a course lesson, or a docs article. The usual forks in the road look like this:
1. Embed a third-party widget and accept their database, ads, and uptime.
2. Roll your own `comments` table for the third time this year.
3. Install a package that only works with one frontend stack.
Commentify is a self-hosted Laravel comments package built for the third option done properly: one polymorphic thread in your database, Livewire out of the box, and an optional Pro layer for JSON API, React/Vue SDKs, spam, and Filament moderation.
This article focuses on Commentify Pro, what it adds on top of the free MIT package, how install works, and when you should (and should not) buy it.
> Already using the free package? The Livewire happy path did not change. Pro layers features; it does not fork the core.
Also Read: Gaming: Lawmakers and Consumer
Free vs Pro (be honest with yourself)
| Need | MIT Commentify | Commentify Pro |
|---|---|---|
| Trait + livewire:comments | Yes | Yes (same core) |
| Nested threads, markdown, likes, reports | Yes | Yes |
| Guest name + email | Yes (opt-in) | Yes |
| Basic Filament resources | Yes | Yes |
| Versioned JSON API | - | Yes |
| React & Vue SDKs (UI parity with Livewire) | - | Yes |
| Spam pipeline (heuristic → Akismet / toxicity) | - | Yes |
| Filament queue, spam log, audit | - | Yes |
| Media, webhooks, Reverb, Disqus/WP import | - | Yes |
If you only need Blade/Livewire comments on a blog, start free: composer require usamamuneerchaudhary/commentify. Reach for Pro when headless access, JS stacks, or production spam become real problems.
The free happy path (unchanged)
Any Eloquent model:
use Usamamuneerchaudhary\Commentify\Traits\Commentable;
use Illuminate\Database\Eloquent\Model;
class Article extends Model
{
use Commentable;
}
Also Read: Tooling: 10 Stages Of
Any Blade view:
<livewire:comments :model="$article" />That is still the whole integration for Livewire apps. Guests, approval, themes, and pagination live in config/commentify.php.
What Commentify Pro adds
1. Headless JSON API
Pro exposes a versioned `commentify/api/v1` with rate limits and structured errors. Commentable models are registered by alias so clients never pass raw PHP class names:
// config/commentify-pro.php
'commentables' => [
'articles' => \App\Models\Article::class,
],Use Sanctum or session as the API guard. This is the path for Inertia apps, mobile clients, and custom frontends that still want one comments table.
Also Read: News: How QR Codes
2. React and Vue SDKs with UI parity
Pro’s React and Vue packages render the same thread as Livewire, same Tailwind classes, composer, sort dropdown, kebab menu, markdown preview, and dark mode. Parity is enforced with tests: Blade class strings live in `@commentify/core`; PHPUnit and Vitest fail the build if stacks drift.
There is nothing to buy from npm. The JS ships inside the Composer package and is linked as local `file:` dependencies after install.
3. Spam and Filament
Heuristic checks run first (link caps, blocked terms, duplicate windows, trust after N approved comments). Optional Akismet and Google Perspective toxicity sit behind that. Filament adds a moderation queue, spam log with “not spam” feedback, audit trail, and simple analytics widgets.
4. Production extras
Media uploads (GIF/JPEG/PNG/WebP), Slack/Discord-style webhooks, Laravel Reverb broadcasts, pinned comments, author/moderator badges, Disqus/WordPress XML import, and GDPR CLI helpers (export / erase / anonymize).
Also Read: Development: Exploring Application Security:
Installing Commentify Pro
After purchase you get Composer access to the private repository:
composer config repositories.commentify-pro \
composer https://commentify.composer.shcomposer require usamamuneerchaudhary/commentify-prophp artisan commentify-pro:installThe installer asks which frontends you use, which guard the API should use, which spam checkers to enable, and which models may receive comments. It publishes `config/commentify-pro.php`, scaffolds a starter component, and runs migrations. It is safe to re-run; values you customised are left alone.
Non-interactive example:
php artisan commentify-pro:install \
--frontend=react \
--guard=web \
--spam=heuristic \
--migrate \
--no-interactionLicense checks happen at install time via Composer, not as a runtime phone-home on every page request.
Purchase: https://checkout.anystack.sh/commentify-pro
Try before you buy
The marketing site is a real Laravel app running the package:
- Live threads on twelve models
Also Read: Apple Finally Folds: iPhone Duo, iPhone 18 Pro and More Headline "Surprise and Shine"
- Livewire / React / Vue parity
Conclusion
A serious Laravel comments package should live in your app, speak Eloquent, and not force you to pick between Livewire and React forever. Commentify’s MIT core covers the common case. Commentify Pro is the production layer for teams that need an API, stack parity, and a spam path that does not depend on hoping the captcha holds.
Start on the live demo, then upgrade when the feature table matches your roadmap.
Leave a comment
Your email address will not be published. Email is optional. Required fields are marked *
