
• The original concept made sense for technical teams: own the stack, control IPs and domains, and avoid per‑message fees with a self‑hosted sending pipeline that promised flexibility and brand control.
• Early on, the positioning around privacy, white‑labeling, and integration with external SMTP/API providers sounded practical for agencies and high‑volume senders who want autonomy.
• The architecture idea, on paper, fit advanced deliverability workflows like domain segregation, sending warmup, and routing options without being tied to a single SaaS vendor. Review collected by and hosted on G2.com.
The moment the team stopped being present, support essentially disappeared, and the product experience collapsed with it; We were left with issues in production and no meaningful response path.
Communication became a dead end: tickets lingered, guidance stalled, and critical fixes never materialized, turning day‑to‑day operations into a guessing game.
The supposed cost advantage flipped as maintenance, troubleshooting, and downtime accrued; without a responsive vendor, the total cost of ownership grew instead of shrinking. Review collected by and hosted on G2.com.
Our network of Icons are G2 members who are recognized for their outstanding contributions and commitment to helping others through their expertise.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through LinkedIn
The reviewer received either a gift card or a donation made to a charity of their choice in exchange for writing this review.
G2 Gives Campaign. The reviewer received either a gift card or a donation made to a charity of their choice in exchange for writing this review.


