Title: Hi HN - we’re Max and Chandler, and we’re building Dittofeed <a href="https:&#x2F;&#x2F;dittofeed.com">https:&#x2F;&#x2F;dittofeed.com</a>. We make it easy for growth and marketing teams to message their customers across multiple channels. We&#x27;re an open source alternative to platforms like Iterable, <a href="http:&#x2F;&#x2F;customer.io&#x2F;" rel="nofollow">http:&#x2F;&#x2F;customer.io&#x2F;</a>, 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:<p><a href="https:&#x2F;&#x2F;www.loom.com&#x2F;share&#x2F;0f7b67170b3a4205add00c22844ca06f" rel="nofollow">https:&#x2F;&#x2F;www.loom.com&#x2F;share&#x2F;0f7b67170b3a4205add00c22844ca06f</a><p>We created Dittofeed to tackle some commonly felt pains with customer engagement platforms:<p>First, 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.<p>Second, 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.<p>Third, 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.<p>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.<p>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.<p>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).<p>If you can use the following, we’d love it if you checked us out:<p>Email support via sendgrid (other channels coming soon).<p>User data import via Segment integration.<p>We have a cloud offering, and offer paid support. You can find our pricing on our site <a href="https:&#x2F;&#x2F;dittofeed.com&#x2F;pricing">https:&#x2F;&#x2F;dittofeed.com&#x2F;pricing</a>.<p>How to try Dittofeed out:<p>Check out our demo site to play around with the app <a href="https:&#x2F;&#x2F;demo.dittofeed.com&#x2F;dashboard">https:&#x2F;&#x2F;demo.dittofeed.com&#x2F;dashboard</a><p>Run the app locally via docker compose (<a href="https:&#x2F;&#x2F;docs.dittofeed.com&#x2F;deployment&#x2F;self-hosted&#x2F;docker-compose">https:&#x2F;&#x2F;docs.dittofeed.com&#x2F;deployment&#x2F;self-hosted&#x2F;docker-com...</a>).<p>Join our slack and we’ll set you up with cloud hosting (<a href="https:&#x2F;&#x2F;join.slack.com&#x2F;t&#x2F;dittofeed-community&#x2F;shared_invite&#x2F;zt-1u3lyts83-P6npff1AbjniNRLVlrlM5A" rel="nofollow">https:&#x2F;&#x2F;join.slack.com&#x2F;t&#x2F;dittofeed-community&#x2F;shared_invite&#x2F;z...</a>)<p>We’d love to hear your thoughts, opinions, and experiences with these tools. What’s been your experience working with this kind of tech?
Upvote: