The right alert. To the right person.
An event-driven engine keeps traders and owners informed on the moments that matter, and gives staff the tools to reach the whole trader base when they need to.
Built for prop firms.
What you get. In detail.
Event-driven alerts
Challenge passed/failed, profit-target close, drawdown close, account assigned, new registration: fired from real state changes, never polled or batched.
Per-event configuration
Each firm decides per event: who receives it, over which channel, what threshold triggers it, and how often it may repeat.
Discord & Telegram delivery
Route alerts to Discord and Telegram channels alongside in-app and email, where your team and your traders actually live.
Anti-spam throttling
Proximity alerts respect a re-notify interval, so “close to drawdown” never floods an inbox during a volatile session.
Staff message center
Compose to all users or specific users, optionally anonymous, optionally also as email: announcements, warnings, outreach.
HTML campaigns with analytics
Bulk email with live preview and delivery stats (sent, reached, read rate, retries, errors, queue), so you know a campaign landed, not just that it left.
Hardened delivery
Rate limiting, XSS sanitization, header-injection prevention, and an audit trail on bulk sends.
Configurations firms actually run. Set once, trust after.
Risk Desk
Everything dangerous, one channel.
- Drawdown proximity → Discord #risk
- Failures → Discord + owner email
- Tight 1% thresholds
- 2h re-notify interval
Quiet Trader
Traders hear only what’s theirs.
- Pass/fail → trader, in-app + email
- Proximity warnings → trader only
- Welcome email on account assignment
- No owner noise in trader channels
Payout Watch
Money moments, witnessed.
- Payout requested → owners, Discord
- Approved → trader, email + in-app
- KYC needed → trader, email
- Every send in the audit trail
Sales Pulse
Growth events to the founders.
- New registration → Telegram
- First purchase → Telegram
- Daily volume worth watching
- Zero dashboard-checking required
Announcement Day
Reach the whole base, measurably.
- HTML campaign with live preview
- All traders or a targeted subset
- Read rate & delivery stats
- Automatic retries on errors
Hands-Off
Defaults that just work.
- Sensible per-event defaults
- Email as the universal fallback
- Change any routing anytime
- Throttling on by default
Fired, routed, throttled. In one second.
Fired by state, not by schedule
The event exists because account #4521’s equity actually crossed your 1.5% threshold, not because a nightly digest ran. By the time a daily summary would have mentioned it, this moment would already be a breach.
Routed by your rules
You decided this event’s audience once: the trader hears in-app and by email, the risk channel in Discord hears at the same instant. Another event (say, a new registration) goes somewhere else entirely. Audience, channel, and threshold are per event, per firm.
Then it shuts up
The re-notify interval mutes repeats for four hours, so an equity curve oscillating around the threshold sends one alert, not forty. That restraint is why your alerts keep getting read, and why traders act on them.
Why firms switch. And what changes.
Silence and spam cost the same
Miss the alert and a trader blows an account nobody warned them about; over-alert and everyone filters your messages to a folder they never open. Most notification setups fail in both directions at once: critical events lost in noise, routine events repeated endlessly. The value isn’t sending messages; it’s the right message reaching the right person exactly once.
How the engine routes
Notifications fire from real state changes (a pass, a fail, equity approaching a limit, an account assignment) and never from polling. Each firm configures every event independently: who receives it, over which mix of in-app, email, Discord, and Telegram, at what threshold, and how soon it may repeat. On top of that sits a staff message center for targeted or firm-wide outreach and HTML campaigns with delivery and read tracking.
What changes for your firm
Traders act on warnings because warnings are rare and real; your risk channel in Discord pings the moment something needs eyes; announcements reach the whole base with proof they landed. Communication becomes something you configure once and trust, with rate limiting, sanitization, and an audit trail keeping bulk sending safe.
Ad-hoc messaging vs. the event engine. Why alerts get ignored.
Trigger
Someone notices something and writes a message, sometimes, eventually.
State changes fire events the moment they happen, on every account.
Routing
Everyone gets everything; the critical and the trivial look identical.
Per-event audiences, channels, and thresholds: each firm’s own rules.
Volume
Feast or famine: silence for days, then a flood nobody reads.
Throttled repeats keep alerts rare enough to stay read and acted on.
Proof
Did the announcement reach anyone? Nobody can say.
Delivery and read stats per campaign, with an audit trail on every send.
Common questions. Straight answers.
Real account state changes: challenge passed or failed, approaching the profit target, approaching a drawdown limit, account assigned, new registration, and staff messages. Each event is configured per firm: who receives it, over which channels, at what threshold.