FAQ

A self-hosted notification platform for crypto exchanges — templates, SMTP routing, queues, and audit logs in one stack.

Exchange operators and fintech teams who need reliable transactional email without per-send SaaS fees.

Self-hosted — your data, SMTP credentials, and logs stay on your infrastructure.

Withdrawal confirmations, deposit alerts, security warnings, KYC updates, and compliance notices.

No — the admin UI covers everything; the REST API is there for teams that want programmatic control.

Every notification is queued via Laravel jobs — slow SMTP never blocks your app.

Yes — unlimited SMTP profiles with per-exchange or per-type routing.

The queue retries automatically; each attempt is logged and can be manually retried.

Database (works everywhere) and Redis (high throughput) — switch with one env variable.

Yes — BulkSendJob dispatches to groups or segments in configurable batches.

Binance (12), Coinbase (10), Kraken (10), OKX (12), Bybit (10) — 54 templates total.

Yes — subject lines, body, variables, and layout are all editable from the admin panel.

Yes — create templates with any key and package them as a reusable addon.

Yes — all templates use the EmailLayoutBuilder tested across Gmail, Outlook, and mobile.

AES-256 encrypted — never in logs, API responses, or the admin UI after entry.

Bearer token auth with rotating keys, per-key revocation, and request-ID tracing.

Every notification creates a full delivery log — recipient, template, status, and rendered content.

Yes — full contact deletion including notification history; you control all retention.

Yes — public endpoint, automatic suppression, and audit-logged suppression events.

PHP 8.2+, MySQL 5.7+, Composer, and Apache or Nginx.

Yes — designed for cPanel; the installer wizard handles queue and cron setup.

Yes — 12 REST endpoints for dispatch, contacts, templates, and delivery status.

No — optional for high volume; the database queue works out of the box.

Docs, installation guides, and email support; priority SLAs on higher tiers.

Most teams finish in an afternoon; SMTP and template config takes one to three days.

One year of versioned updates with migration notes; customisations are never overwritten.

No — templates, addons, and config live outside the update path.