Customer.io is a hosted messaging platform for event-driven email, push, SMS and in-app journeys priced by profiles; pages here cover self-hosted Dittofeed as the replacement.
Comparing Customer.io with self-hosted Dittofeed for event-driven messaging: segments, journeys, channels, templates in HTML or MJML, data in through Segment, reverse ETL or API, git-based workflows, and what an alpha-stage open-source project means for support.
Moving from Customer.io to Dittofeed: exporting people and attributes to CSV, repointing event tracking through Segment or the Dittofeed API, rebuilding segments and journeys, connecting SendGrid or Amazon SES, and running both until messages match.
Cost of ownership by component: Customer.io plans priced by profiles and email volume, with HIPAA on Premium, against Dittofeed's free license, servers and databases, email and SMS provider fees, migration and the engineers who run it.
What Customer.io lets you take out: people and attributes as CSV, filtered by segment, plus segment membership exports and relationships. Covers what does not come with it, such as journeys and templates, and how to clear sensitive fields before sharing.
Customer.io fixes the data region at account setup and does not migrate accounts between regions. This page compares its EU region in Belgium with running Dittofeed in your own EU infrastructure, and where email and SMS providers still process data.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.