One of the founders / maintainers of Laudspeaker [1] here! We think its great that there are more open source options in the space and really nice design guys!
Some differences:
a) We have explicitly decided against a DAG approach [2] for our visual editor and use state machines as our model, so you can explicitly create things like loops, and customize journey logic more.
b) Our cloud pricing is not user based, but right now follows a pay as you go model for usage with sliding discounts for larger message volumes [3]. While the mechanics may change we are most likely going to avoid user based pricing models.
c) We support different channels at the moment (email, sms, firebase push, slack, in app modals) and we integrate with databases/ warehouses as well as product analytics services like posthog [4] and CDPs like rudderstack. I'm sure with time we will converge on the same channels/integrations.
d) We think journey versioning / testing is a great idea, and don't yet have that but are rolling out our own.
Some similarities:
a) We also use clickhouse, and at some point will use temporal (our project is supported by one of their executives)
b) We also have a visual editor, segments and templates
c) We can be self-hosted (A few users are self hosting today)
For others checking this out there are also older projects like Mautic [5]. And customer engagement is a large enough category that it includes projects like Chatwoot [6] that focuses more on customer support.
Some differences:
a) We have explicitly decided against a DAG approach [2] for our visual editor and use state machines as our model, so you can explicitly create things like loops, and customize journey logic more.
b) Our cloud pricing is not user based, but right now follows a pay as you go model for usage with sliding discounts for larger message volumes [3]. While the mechanics may change we are most likely going to avoid user based pricing models.
c) We support different channels at the moment (email, sms, firebase push, slack, in app modals) and we integrate with databases/ warehouses as well as product analytics services like posthog [4] and CDPs like rudderstack. I'm sure with time we will converge on the same channels/integrations.
d) We think journey versioning / testing is a great idea, and don't yet have that but are rolling out our own.
Some similarities:
a) We also use clickhouse, and at some point will use temporal (our project is supported by one of their executives)
b) We also have a visual editor, segments and templates
c) We can be self-hosted (A few users are self hosting today)
For others checking this out there are also older projects like Mautic [5]. And customer engagement is a large enough category that it includes projects like Chatwoot [6] that focuses more on customer support.
[1] https://github.com/laudspeaker/laudspeaker
[2] https://laudspeaker.com/docs/engineering-blog/finite-state-m...
[3] https://laudspeaker.com/pricing
[4] https://posthog.com/tutorials/laudspeaker-posthog
[5] https://www.mautic.org/
[6] https://www.chatwoot.com/