Embed template editors, journeys/workflows, user segmentation, broadcasts, and more inside of your app with Dittofeed's iframes and headless react components.
Hi PH, I’m Chandler from Dittofeed.
Today we’re launching something that started as a strong, semi-data-driven hunch a year ago when many of people came to our open source project thinking we did something we didn’t do.
For context, our open-source offering is an alternative to MailChimp, Klaviyo, etc. But these people were asking for a way to embed our messaging tools in their own applications. After the 20th person asked (with literally no marketing material from us indicating we offered what they were searching for), we decided we had enough data points to move forward with making it. Give the people what they want as they say!
Without further ado, we’re happy to introduce Dittofeed’s Embedded Components!
https://docs.dittofeed.com/embed...
What they are:
-iframes currently, and headless react components soon (this summer).
-A simple way to add features like template editors, journeys/workflows, broadcasts, segmentation, and anything else your users need to send and automate messages across any channel.
Why they’re useful:
-SaaS, and especially vertical SaaS, often end up reimplementing these features over and over. Embedded Components lets the whole SaaS industry stop reinventing the wheel.
-Engineering teams take 6-12 months on average to implement messaging features. Embedded Components take seconds to implement.
-Say you’re a healthcare SaaS for providers, and you want to allow them to message their patients. You’re compliance constrained and wary of cloud offerings. With Embedded Components, you have the option to self-host!
Where we’re at:
-A range of early adopters are successfully using Embedded Components in production (both self-hosted and in our cloud). Their users are loving them.
-Engineering managers are very happy with us.
Where we’re going:
-Headless react components for 100% styling control.
-All resources (templates, user segments, etc.) represented as config files that llms can easily manipulate.
-First party support for reverse ETL
Although we’re an open-source company and our base product is free, Embedded Components are a paid feature. Reach out to support@dittofeed.com for an admin API key if interested, or dm me on PH.
If you just want to use our MIT-licensed base product as an alternative to Klaviyo, Iterable, MailChimp, etc. you can find it here:
https://github.com/dittofeed/dit...
Would love any feedback you have!
@chandler_craig@max_gurewitz Curious: how are you managing schema migrations and data consistency during transitions, especially with temporal and multi‑tenant compute pipelines?
Hi Reid! Schema migrations are written in a way that involve no downtime, and are run from our admin-cli project. We have two categories of migrations - postgres migrations, and clickhouse migrations. Postgres migrations are managed with drizzle. I hope that answers your question, but if you meant something else, feel free to reach out by email or on our discord help channel!
Replies
Dittofeed
@chandler_craig I hope this will a victory for you. Best of luck!
50+ Contract Templates by Clientjoy
All the best for the launch @chandler_craig & team!
Congrats on the launch! What are the dependencies for self-hosting?
Dittofeed
@michael_egan thanks! Dependencies are @ClickHouse , @Temporal , and Postgres 🙂
Dittofeed
@chandler_craig @reid_crooks
Hi Reid! Schema migrations are written in a way that involve no downtime, and are run from our admin-cli project. We have two categories of migrations - postgres migrations, and clickhouse migrations. Postgres migrations are managed with drizzle. I hope that answers your question, but if you meant something else, feel free to reach out by email or on our discord help channel!
Congrats on the launch!! This sounds awesome!
@chandler_craig great to see the new launch and a client-led approach, the embedded aspect will help to unlock even more value for founders with apps.
Dittofeed
@gus_d thanks so much!