QQueue
qqueue.app
- Free plan
- Web
- API
- Self-hosted
What QQueue is
QQueue runs campaign, transactional, and manual email through one pipeline using your SMTP server. Campaigns support contact lists, dynamic segments, merge fields, A/B subject tests, and per-campaign open and click analytics. Applications can send transactional messages through a public HTTP endpoint, organization-scoped API keys, or the TypeScript SDK. Email Studio handles immediate sends, one-time scheduling, and recurring cron-based sends with timezone-aware scheduling. QQueue connects to standard SMTP services including Mailcow, Amazon SES, Postmark, Resend, and Brevo; provider-native APIs are not implemented. Tracking includes opens, clicks, signed outbound email-event webhooks, and an inbound endpoint for bounce and complaint events. Saved SMTP credentials are encrypted at rest, while links and webhook events use signed tokens or signatures. QQueue is self-hosted, keeping contacts, content, events, and API keys on infrastructure controlled by the operator. QQueue Core is AGPL-3.0-only and described as a feature-complete self-hosted beta for early technical users. It is free, excluding server and SMTP costs.
Who it suits
It suits developers, small teams, Mailcow operators, self-hosters, SaaS founders, indie hackers, and agencies. It is intended for technical users comfortable operating self-hosted email infrastructure.
Good to know, and what to watch
- Combines campaign and transactional email
- Supports recurring timezone-aware scheduling
- Provides API, SDK, and webhooks
- Encrypts saved SMTP credentials
- Keeps data on operator-controlled infrastructure
- Self-hosted operators pay server and SMTP costs
- Provider-native APIs are not implemented
- Automated multi-step drip sequences are unavailable
- Managed QQueue Cloud is not yet available
Plans
Every plan and priceQQueue Core
Free plan
The verdict
QQueue offers a self-hosted email pipeline with campaign tools, transactional APIs, scheduling, tracking, and signed events. Its beta status and infrastructure responsibilities make it a better fit for technical operators than teams seeking a managed service.
What the maker publishes
- Campaigns
- Campaigns support contact lists and dynamic segments, merge fields, A/B subject tests, and per-campaign open and click analytics. source
- Cloud availability
- Managed QQueue Cloud is planned and not yet available. source
- Data control
- QQueue is self-hosted, and its site says contacts, content, events, and API keys stay on infrastructure the operator controls. source
- Delivery methods
- both source
- Event webhooks
- Yes source
- Free plan
- Yes source
- Intended users
- The documentation identifies developers, small teams, Mailcow operators, self-hosters, SaaS founders, indie hackers, and agencies as intended users. source
- License and status
- QQueue Core is AGPL-3.0-only and described as a feature-complete self-hosted beta for early technical users. source
- Maker
- The licensing page names Nana Aboagye as the copyright holder of QQueue Cloud and Nana Aboagye Boateng as the owner of QQueue trademarks. source
- Notable limits
- Recurring sends are supported, but automated multi-step drip sequences are not. source
- Scheduling
- Email Studio supports immediate, one-time scheduled, and recurring cron-based sends with timezone-aware scheduling. source
- Security
- Saved SMTP credentials are encrypted at rest, and tracking links and webhook events use signed tokens or signatures. source
- SMTP integrations
- QQueue connects to standard SMTP servers, including Mailcow, Amazon SES, Postmark, Resend, and Brevo; provider-native APIs are not implemented. source
- Template options
- both source
- Tracking and webhooks
- It supports open and click tracking, signed outbound email-event webhooks, and a normalized inbound endpoint for provider bounce and complaint events. source
- Transactional email
- Applications can send transactional email through a public HTTP endpoint, organization-scoped API keys, or the TypeScript SDK. source
- What it does
- QQueue runs campaign, transactional, and manual email through one delivery pipeline using your SMTP server. source
Checked against the maker's pages on 9 Oct 2026.