Automated email, SMS & push.
No per-user bill.
Send messages based on what people do. Build the flow by dragging boxes. Run it on your own servers, or right inside your Laravel app.
You shouldn't pay per user
to message your users.
Most tools charge you for every person in your database — every month, forever. Trigger Engage does the same job on servers you already pay for.
Keep your data. Keep your sending reputation. Drop the monthly bill.
Everything you need to message users
The automation engine, the audiences, the tests, the charts — all included, and all yours.
Visual journeys
Drag boxes to build a flow: wait, branch, split, send. Change it anytime — people already in it aren't disrupted.
Smart segments
Group people by what they did — like “booked but didn't show up in 30 days.” The list keeps itself up to date.
A/B testing
Send a few versions of a message, split who gets which, and see which one wins — right there on the flow.
Built-in analytics
See how many messages were sent, delivered, opened, and clicked — over time and by channel. No add-on to buy.
Track before signup
Follow visitors before they sign up. When they do, everything they did earlier joins their profile — automatically.
Three channels, one profile
Email (SMTP, SES, Mailgun, Postmark, and more), SMS (Termii), and push (OneSignal) — all from the same person's profile.
Never breaks your app
If messaging goes down, it quietly logs the problem and moves on. Your signup and checkout keep working, no matter what.
Build the flow by dragging boxes
Add triggers, waits, branches, A/B splits, and sends by dragging them onto the page. Publish it, then watch people move through it live.
- Wait minutes, days, or until a set time
- Pause until the next thing happens
- Stop the flow the moment someone converts
Lists that update themselves
Set a rule once — based on who people are and what they've done — and the list updates itself as people act and time passes.
- Match on details and on actions
- Time-based rules like “inactive 14 days”
- Send a one-off blast to any list
See what's working
One dashboard for how many messages went out, how many landed, and how your flows are doing — all compared to last period.
- Sent vs delivered, over 7 to 90 days
- Delivery funnel and health by channel
- Kept up to date by your providers
Three simple parts
Your app does two things: say who someone is, and what they did. Everything else happens here.
Send events
Add the SDK and call identify() and event() from your app. Send them and forget them.
Build flows
Set up lists, messages, and drag-and-drop flows with A/B splits and goals. Hit publish — no deploy, no engineer needed.
Send & measure
The engine runs your flows and sends the email, SMS, and push through your providers — then shows you how they did.
Safe to run in production
If messaging fails, it logs the problem and moves on. Your signup and checkout never notice.
Every call has a key, so a retry can never send the same message twice.
Use TriggerEngage::fake() and assertEventSent() — no network calls in your tests.
// composer require trigger-engage/laravel use TriggerEngage\Laravel\Facades\TriggerEngage; // who to message TriggerEngage::identify('user-42', [ 'email' => $user->email, 'first_name' => 'Ada', 'plan' => 'free', ]); // what they did — this starts your flows TriggerEngage::event('customer_sign_up', [ 'plan' => 'free', ], person: 'user-42');
Trigger Engage vs a hosted tool
Hosted tools are great. Here's the trade-off for owning your data instead of renting it.
| Trigger Engage | Hosted (e.g. Customer.io) | |
|---|---|---|
| Pricing model | Free & open source | Per profile, monthly |
| Cost for ~30,000 people | $0 in fees | $100+/mo, and rising |
| Self-host on your infra | Yes | No |
| Embed inside your Laravel app | One Composer command | Hosted only |
| Own your data & sending reputation | Fully | On their servers |
| Email · SMS · Push | All three | All three |
| Journeys · Segments · A/B · Analytics | Included | Included |
| Runs without you managing it | You run it | Managed for you |
Not affiliated with or endorsed by Customer.io. Comparison reflects public pricing at the time of writing.
It's open source under the MIT license. No seat limits, no user caps, no upsells. You just pay for the servers you already run.
Good to know
Is it really free?
How is this different from Mailchimp or a newsletter tool?
Can I run it inside my existing Laravel app?
composer require trigger-engage/server — installs the whole thing into your app, using your database and login. No second service to run. Or deploy it on its own and connect over the API.What do I need to run it?
Which providers does it send through?
Is my customer data private?
Own your messaging.
Build your first flow today. On your own servers or inside your app — free for good.