Who you should pick, including when it is not us.
An objective comparison, one alternative at a time. Each page sets out the differences that decide the choice (including the ones where the other product is ahead), so you can tell whether Palumb fits what you are building. The facts come from each vendor's own documentation, privacy policy or repository (never from an aggregator, and never from one of their competitors), each with the date it was checked.
If you find one that is wrong or out of date, tell us and the page will be corrected.
-
Palumb vs Novu
The other self-hostable one, and the closest thing we have to a mirror. Bigger product, EU regions, and a company outside the Union.
Read the comparison →
-
Palumb vs Knock
Richer workflow functions and an in-app feed. A New York company, and no self-hosting path at all.
Read the comparison →
-
Palumb vs Courier
More channels and real certifications. The only vendor here who publishes whose infrastructure runs its EU region, which is worth saying out loud.
Read the comparison →
-
Palumb vs SuprSend
Multi-tenancy done properly, which is our own gap. Also a Delaware company processing data in the United States.
Read the comparison →
-
Palumb vs MagicBell
An in-app inbox first, with a workflow engine of four commands and none of them waiting for an event. A San Francisco company that counts a delivery per channel.
Read the comparison →
-
Palumb vs Building it yourself
The competitor almost everyone actually picks, and for most teams the right answer. Here is where that stops being true.
Read the comparison →
Everyone who joins gets in, and it costs nothing. Your invite goes out when the beta opens.
Join the beta