Overview:
Dittofeed is an open-source, omni-channel customer engagement platform designed as a developer-friendly alternative to services like OneSignal, Customer.io, and Segment Engage. It allows users to send broadcasts or create automated user journeys across channels including email, SMS, WhatsApp, and Slack. The platform integrates user data from sources like Segment or via its own API, supports highly customizable user segmentation, and offers both low-code and code-based template editors. It is built for teams that need a self-hosted or API-first solution for managing customer messaging workflows.
Core Features:
Omni-channel messaging: Send broadcasts and automated journeys across email, SMS, WhatsApp, Slack, push notifications, and more.
User segmentation: Create highly customizable user segments using multiple operators.
Template editing: Design messaging templates using HTML/MJML or the platform's low-code editor.
Developer-centric workflow: Supports branch-based git workflows for campaign version control and includes a testing SDK for CI-based campaign testing.
Self-hostable deployment: Deploy via Docker Compose or Render to run inside your own VPC and protect sensitive PII.
Journey monitoring and alerting: Monitor automated user journeys and receive alerts on performance or failures.
Use Cases:
Developers building automated, event-based customer messaging journeys with version control and CI testing.
Teams needing to send one-off broadcasts or recurring campaigns across email, SMS, and chat apps.
Self-hosters who want to keep sensitive user data (PII) within their own infrastructure and avoid volume-based pricing.
Why It Matters:
Dittofeed provides an open-source alternative to proprietary customer engagement platforms, offering full control over deployment and data. Its developer-focused features—like git-based campaign version control and a CI testing SDK—make it suitable for engineering teams who want to manage messaging campaigns as code. The platform supports self-hosting, allowing organizations to run it inside their own VPC and protect sensitive user data. This makes it a practical choice for teams that need flexibility, data privacy, and a workflow that integrates with existing development practices.
