Dittofeed: features, limits & comparisons
Event-triggered journeys across email, SMS and push with branching and segments; in-app messaging is the conspicuous hole.
functionality and fit
Recorded license: MIT.
- Self-hosted identity and configuration data lives in PostgreSQL and event/segment data in ClickHouse; optional blob data can use object storage.
- Dittofeed Cloud or Docker Compose/Kubernetes self-host
Costs and editions: A source license is separate from operating costs. Hosting, storage, external APIs and commercial support may require payment.
scope and migration checks
- Dittofeed offers richer event-driven journeys, but PostgreSQL, ClickHouse, event instrumentation, and delivery-provider setup make it vastly heavier to operate than Loops.
- Dittofeed can trigger journeys from cart and product events, but it lacks Drip's turnkey ecommerce integrations, store-aware reporting, and revenue attribution unless you build them.
- Dittofeed handles event-driven segments and journeys, but its Postgres-and-ClickHouse operating burden and narrower all-in-one analytics experience are worse than Bento's managed stack.
recorded catalogue description · recorded source check 2026-08-10 · suitability checks are editorial assessments, not hands-on tests
licenseMIT
runsyour machine or their cloud
installDittofeed Cloud or Docker Compose/Kubernetes self-host
dataSelf-hosted identity and configuration data lives in PostgreSQL and event/segment data in ClickHouse; optional blob data can use object storage.
setupDocker Compose brings Postgres and ClickHouse, but the harder first step is instrumenting product events and connecting an email provider.
recorded source check 2026-08-10 · installation not tested
compare these app workflows
These are scoped comparisons, not guarantees that Dittofeed reproduces every paid feature. Follow each build guide for the implementation boundary and the collection for other options.
Event-triggered journeys across email, SMS and push with branching and segments; in-app messaging is the conspicuous hole.
the verdict →Lifecycle journeys driven by product events, with richer branching and much heavier operations.
the catchDittofeed offers richer event-driven journeys, but PostgreSQL, ClickHouse, event instrumentation, and delivery-provider setup make it vastly heavier to operate than Loops.
the verdict →all Loops alternatives →Cart and product events can trigger branching email journeys; ecommerce integrations are yours to wire.
the catchDittofeed can trigger journeys from cart and product events, but it lacks Drip's turnkey ecommerce integrations, store-aware reporting, and revenue attribution unless you build them.
the verdict →all Drip alternatives →Event-driven segments and multichannel journeys with a marketer-facing UI; the infrastructure diagram is not decorative.
the catchDittofeed handles event-driven segments and journeys, but its Postgres-and-ClickHouse operating burden and narrower all-in-one analytics experience are worse than Bento's managed stack.
the verdict →all Bento alternatives →latest catalogue source check 2026-08-10 · recorded recurring plans: $2,256/yr (before operating costs) · no votes, no pay-to-list
sources and related categories
These are sources retained with the catalogue record. Their recorded check date is not a new verification of current terms.