Show HN: Laudspeaker – Open-source mobile push, SMS and email automation (github.com)
Laudspeaker (https://laudspeaker.com/) is an open source customer engagement suite (also called marketing automation software). If you've used tools like Braze, One Signal, Airship, Iterable, Customer.io or some others, Laudspeaker is an alternative to these. Here is a quick demo: https://www.loom.com/share/4b309390ee274ea491981e1394e9abc4. And here is a link to sign up and try free (no cc needed): https://app.laudspeaker.com/signup.
Or if you prefer to just jump in, go to https://app.laudspeaker.com/login and use this test account:
email: test94@laudspeaker.com
pw: test93@laudspeaker.com
The main things Laudspeaker lets you do are:1. Define 'segments': which of your users should receive messages.
2. Define 'messaging journeys': when, where and with which channels you want to reach users. Right now we support push, email, SMS, and soon we'll also include in-app messages and WhatsApp.
For example, one customer of ours runs a journey like this: "Wait for a user to complete onboarding on our mobile app, then send a welcome push. If they complete an action the next day on the app, stop sending messages, otherwise send a followup email."
There are quite a few big updates since our last Show HN (https://news.ycombinator.com/item?id=34835559):
We now have a mobile SDK for sending and receiving push notifications. We have revamped the journey builder, and made our segment builder much more comprehensive. Our application is also a lot more battle tested - we are deployed with a major fintech in Asia and are sending XX million messages a week to more than x million users.
We've seen a lot of demand from consumer focused apps and websites who find most of the existing solutions' pricing models prohibitively expensive so please reach out if that sounds like you. We have successfully migrated people over from Braze, customer io and others.
If you're interested in the mobile SdK, see our tutorial: https://laudspeaker.com/docs/getting-started/setting-up-mobi...,
and sample apps: https://github.com/laudspeaker/android-sample-app, https://github.com/laudspeaker/ios-sample-app.
Our Github is https://github.com/laudspeaker/laudspeaker. Try it out for free at https://app.laudspeaker.com/signup.
We'd love to hear your feedback and comments!
35 comments
[ 4.5 ms ] story [ 86.9 ms ] threadChatwoot is a great tool, but is more in the customer support space. It offers a chat widget in your saas app / website and a shared interface to respond, which can then get routed via email, sms etc to the person who asked the question.
Laudspeaker is more of tool to send 1) one off messages (informational, promotional) to segments of users you define, 2) automate message sends like a drip campaign, 3) trigger automatic real-time messages based on specific activity users take in your app or site, eg on add to cart, or on sign up
The users of chatwoot would be customer support / success, the users of Laudspeaker would be growth, marketing, product
The architecture of both applications are quite different. Laudspeaker needs to be able to quickly message millions of users, ingest real time events, and create references to large sets (millions) of users.
We actually used chatwoot for support a while back, and have a customer who uses both Laudspeaker and chatwoot in production!
We offer enterprise level support for self-hosting users in the paid plan, and they can use future features in our ee (enterprise) folder (which is empty right now)
Well done and good luck!
If I want to send SMS to a bunch of people, can I hook this into a self-hosted Asterisk server or something? Or does this have its own SMS gateway? Or am I forced to use a third party dealio like Twilio?
We are trying to find a pricing model that can work for consumer facing apps/sites and companies, as well as B2B!
If you want to self host for free, the easiest way would be to run our docker compose on a compute instance-we're in the process of updating our docs for self hosting and I can email you with more info if you'd like.
They suffer from the same "cold start" problem that social apps do. For the project to thrive, there needs to be an existing fanbase to improve and support it.
Is what makes Wordpress great the fact that it's open source? No. It's the community of builders that surround it.
Would anyone realistically be willing to spin this stack up in their existing company (and sign up for maintaining it)?
I expect you'll get a few git clones from engineers to poke around to see how it was built, out of curiosity, but not much more.
Of course the natural response would be "who cares? They opened the source so you can if you want to!"
That's fair. I guess I just get stuck on the "why"
And still, people do get that done, and it is great that you have the self hosting option if you don't like their pricing (or if they ever go suddenly bankrupt, compromising your business).
Not sure if there's enough free performance to run Loudspeaker, but I'm definitely considering it.
- Operating in a regulated industry, we have customers who cannot send customer data to 3rd party services (in financial services, healthcare) and need to self host for that reason
- Existing solutions are too expensive for their business model, we have Kenyan, Brazilian and Mexican consumer focused companies from other countries spin up and use the self-hosted solution
- Cost savings and Philosophy, believe it or not there are some companies which like to self host software if possible, and have dedicated dev ops resources already maintaining software and spinning up another solution is not that much incremental work.
Beyond that there are other reasons to want to open source a solution like this. Anyone can add communication channels and integrations for example. And lastly its fun to work on an open code base!
Our software and competitors like Braze are typically used in situations where you can’t have a personal connection, but still need to message users, often when they complete specific actions in your application, or if you want to send one-off promotions for example. E-commerce brands or a banking app might use us for example.
We do support replacement variables like you mentioned and are adding integrations actively.
Just wondering though, the last release is from September last year. Any specific focus of the activities outside of the core product?