laudspeaker VS dittofeed

https://news.ycombinator.com/item?id=39836316

Laudspeaker | Remote| Full Time | Senior Software Eng / Founding Eng

We posted on hacker news a few days ago - you can see the whole post here (https://news.ycombinator.com/item?id=39836316)

Summary below:

We are building a new, open source suite of software tools to completely handle the "customer journey". You can see our repo here: https://github.com/laudspeaker/laudspeaker

We are a small team of 3, had a successful launch on HN a year ago, are backed by YC, and and are now starting to close large companies deploying our software to touch millions of users.

Who You Are:

Our mission is to build a new, open source suite of software tools to completely handle the "customer journey". You can see our repo here: https://github.com/laudspeaker/laudspeaker and our site here: https://app.laudspeaker.com/login

We had a successful launch on HN a year ago, and have moved quickly since and are now starting to close large companies deploying our software to touch millions of users.

We continue to have an ambitious roadmap and are looking for a founding senior engineer to radically improve the product (take it from a 1->10, we have already built the 0->1) and help "level-up" the founders. We need our product to scale to tens of millions of messages sent an hour, handle millions of incoming api requests, add introduce engineering best practices, and tooling for our product to maintain SLAs

The right engineer will be excited to join a small team, excited to work on open source software, works well autonomously, can deal with ambiguity, and wants to work remotely (with minimum 4 hours of overlap sometime between 8am - 8pm pst)

Some more details:

- We work in Typescript with Nest.js for the backend and react for the frontend

laudspeaker: https://github.com/laudspeaker/laudspeaker

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

Play around with our cloud option : https://laudspeaker.com/ / https://app.laudspeaker.com/

Check out our GitHub (Licensed MIT + Apache 2.0): https://github.com/laudspeaker/laudspeaker

Hey HN, we just released Dittofeed v0.13.1! Dittofeed is an open-source, MIT-licensed alternative to customer engagement platforms like Customer.io and Braze. This release introduces several features that really expand how you can use Dittofeed:

- *New Webhook Channel*: This channel lets you make API requests directly from user journeys. It's useful for:

1. Use cases include sending Slack messages, triggering native mobile push notifications.

2. Sending messages with your internal APIs.

3. Integrating messaging channels that Dittofeed doesn't yet support natively.

- *Admin API*: The Admin API allows you to programmatically manage your Dittofeed workspace. This release includes endpoints for managing users, searching user events, and more.

- *Improved Template Publishing UX*: Our template editor now allows you to visually compare your drafts against published templates, simplifying the publication process and ensuring you don’t lose track of your changes.

For a more detailed breakdown of what’s included in v0.13.1, check out our blog post:

https://dittofeed.com/blog/release-0-13-1

And for those self-hosting Dittofeed, make sure to consult our latest upgrade guide:

https://docs.dittofeed.com/deployment/self-hosted/upgrade-guide/v0-13-0

We'd really appreciate it if you visited and starred our repo to help support the project:

https://github.com/dittofeed/dittofeed

Thanks all!

Hey HN, Dittofeed v0.12.1 is out! For those unfamiliar, Dittofeed is an MIT-licensed, open-source platform for omnichannel customer engagement, offering an alternative to tools like Customer.io and Braze. This release focuses on key optimizations and fixes, enhancing performance and compliance:

- New "NotEquals" Segment Operator: Now, you can exclude users based on the absence of specific traits, enabling more precise targeting in your Journeys.

- Optimized Query Memory Efficiency: We've significantly improved the memory efficiency of our computed property engine, powered by ClickHouse. This is helpful for teams self-hosting Dittofeed.

- Subscription Email Headers: We've updated our email headers for subscription-related emails to comply with Bulk email sender guidelines, improving deliverability.

- Improved Messaging Stats: Addressed an edge case with Sendgrid webhook events that could lead to inaccurate messaging stats.

For a detailed look at the contents of v0.12.1 you can read our blog post.

https://dittofeed.com/blog/release-0-12-1

For self-hosting users, see our upgrade guide:

https://docs.dittofeed.com/deployment/self-hosted/upgrade-guide/v0-12-0

We’d really appreciate it if you visited and starred our repo.

https://github.com/dittofeed/dittofeed

Thanks!

- You can now send test messages to yourself to ensure proper rendering in different email clients, validate ESP credentials, etc.

Release blog post with all updates [here](https://dittofeed.com/blog/release-0-6-0). Hope to hear your thoughts!

Github Repo - https://github.com/dittofeed/dittofeed

Demo - https://demo.dittofeed.com/dashboard/journeys

Docs - https://docs.dittofeed.com/getting-started

Polytomic Docs - https://docs.polytomic.com/docs/getting-started

Dittofeed Polytomic Docs - https://docs.dittofeed.com/integrations/sources/polytomic

Hey HN, we’ve just released Dittofeed v0.5.0, with the primary change being the addition of SMS as a messaging channel. Dittofeed is an open source (MIT licensed) omnichannel customer engagement platform, similar to Customer.io and Iterable. We added:

- Twilio-based SMS messaging. You can create SMS templates and customer journeys within Dittofeed.

SMS is a great channel for B2C software companies, looking to engage with their users. For example, e-commerce businesses commonly use SMS to support checkout flows.

We'll be making further enhancements to Dittofeed's SMS support in the coming weeks!

- We added a new "Trait Exists" segmentation option, which can be used to create a segment of all users with phone numbers, for example.

- We made some fairly large improvements to our settings UI. Big shout out to our contributor! https://github.com/promisetochi

The full feature release blog post can be found here: https://dittofeed.com/blog/release-0-5-0.

Looking forward to your thoughts and feedback!

Github Repo - https://github.com/dittofeed/dittofeed

Demo - https://demo.dittofeed.com/dashboard/journeys

Docs - https://docs.dittofeed.com/getting-started

GitHub Repo: https://github.com/dittofeed/dittofeed

Hi HN - we’re Max and Chandler, and we’re building Dittofeed https://dittofeed.com. We make it easy for growth and marketing teams to message their customers across multiple channels. We're an open source alternative to platforms like Iterable, http://customer.io/, Braze, and OneSignal. Here’s a short demo video showing how to run the platform locally, and use it to automate a customer onboarding journey:

https://www.loom.com/share/0f7b67170b3a4205add00c22844ca06f

We created Dittofeed to tackle some commonly felt pains with customer engagement platforms.

Firstly, existing platforms make it difficult to keep imported user data accurate and up to date with your primary user datastore. To solve this, we’re building first-class support for importing data from your data warehouse, for better data consistency.

Secondly, graphical “journey builders” are fragile, and difficult to debug at scale, so we’re building git-based workflows to check your messaging automation into git as configuration, as well the ability to run Dittofeed locally in development, or in CI with our testing sdk, for improved ease of debugging.

Lastly, companies in industries like finance and healthcare are often forced to implement their own solutions in-house to avoid sharing sensitive PII with third parties. As an open source platform, companies can now self-host us to keep their PII in their network.

Chandler, having worked in marketing for startups, experienced these challenges first hand. Max, on the other hand, was a senior platform infrastructure engineer at Braze, where he witnessed similar challenges from a technical perspective. Our combined experiences sparked the idea for Dittofeed.

We decided to create an open source, developer-focused customer engagement platform, because the often unspoken truth is that maximizing the effectiveness of these tools requires ongoing engineering involvement.

Dittofeed is built on Clickhouse (OLAP store used for storing user events, performing user segmentation, and aggregations) and Postgres (OLTP store for persisting application configuration, and serving user aggregations for efficient single-row reads).

If you can use the following, we’d love it if you checked us out:

Email support via sendgrid (other channels coming soon).

User data import via Segment integration.

We have a cloud offering, and offer paid support. You can find our pricing on our site https://dittofeed.com/pricing.

How to try Dittofeed out:

Check out our demo site to play around with the app https://demo.dittofeed.com/dashboard

Run the app locally via docker compose (https://docs.dittofeed.com/deployment/self-hosted/docker-com...).

Join our slack and we’ll set you up with cloud hosting (https://join.slack.com/t/dittofeed-community/shared_invite/z...)

We’d love to hear your thoughts, opinions, and experiences with these tools. What’s been your experience working with this kind of tech?