Dittofeed
The open-source escape hatch from customer engagement vendor lock-in
Dittofeed is an MIT-licensed open-source customer engagement platform, from a Y Combinator-backed two-founder team, that provides journey automation, segmentation, and message templating across email, SMS, and webhook-driven channels, deployable self-hosted for free or as a managed cloud from $75/month, with white-label embedded components that let SaaS products ship messaging automation inside their own apps.
Overview
Dittofeed exists because its founders believe marketing automation should work like modern infrastructure: inspectable, self-hostable, and free of vendor lock-in. The project, launched out of Y Combinator's Summer 2022 batch by Maxwell Gurewitz (previously a senior engineer at Braze and OpenTable, where he helped scale automated messaging to billions of end users) and Chandler Craig (previously marketing at Sony Music and B2C startups), is an explicit open-source answer to Braze, Klaviyo, and Customer.io. The entire platform is MIT-licensed on GitHub, and the company describes its cloud product as having 'an escape hatch': if you outgrow or distrust the hosted version, you take your workloads home.
The feature set covers the category's core loop: a low-code drag-and-drop journey builder with multi-trigger automation and branch-based analytics, segments composed from unlimited AND/OR conditions, and templates written in Liquid with HTML or MJML editing for people who want real control of their markup. Dittofeed does not run its own delivery infrastructure; you connect your own providers, SendGrid, Amazon SES, Postmark, Resend, or raw SMTP for email, Twilio for SMS, and webhooks for everything else (Slack, WhatsApp, mobile push), with data arriving via REST API, Segment, or Polytomic reverse-ETL from your warehouse.
Two things distinguish it from simply being 'cheap Customer.io.' First, embedded components: white-labeled journey and segmentation UI that SaaS companies drop into their own products, turning Dittofeed into messaging infrastructure for other software vendors, a use case none of the closed competitors serve. Second, the deployment model: for healthtech, fintech, and other data-sensitive teams, self-hosting means customer data never leaves their infrastructure, which sidesteps entire categories of compliance review. The costs are equally real: a team of two founders, no managed sending, no built-in email channel defaults, and an operational burden that lands on your engineers if you self-host.
Best for
Engineering-led teams that want customer engagement automation on their own terms: self-hosted for data control, wired to their existing ESP and warehouse, or embedded white-label inside their own SaaS product.
Not the right fit for
- Marketing teams without engineering support; setup means connecting ESP credentials, wiring data via API or reverse-ETL, and possibly operating a deployment, none of which is a marketer-only task.
- Teams that want managed sending; Dittofeed brings orchestration only, and you supply and manage the delivery provider, sender reputation, and warm-up separately.
- Buyers who need a mature, deep feature surface today; a two-founder company iterates fast but cannot match the breadth, integrations catalog, or polish of a 14-year-old platform.
- Compliance processes that require vendor certifications; Dittofeed publishes no SOC 2 or ISO attestation, and its answer to data-security review is self-hosting rather than paperwork.
- Non-technical email marketers wanting drag-and-drop everything; templates lean on Liquid, HTML, and MJML, which is a feature for developers and a wall for everyone else.
How it works
- 1
You deploy Dittofeed self-hosted (free, MIT-licensed, deployable via Render among other paths) or sign up for Dittofeed Cloud, which starts at $75/month for 10,000 monthly unique users with a 14-day trial. Either way, you connect delivery credentials for your own providers: SendGrid, SES, Postmark, Resend, or SMTP for email, and Twilio for SMS.
- 2
User and event data arrives through the REST API, the Segment integration, or Polytomic reverse-ETL pulling from databases and warehouses. Segments are assembled from unlimited AND/OR conditions over traits and events, and update as data flows in.
- 3
Journeys are built on a low-code drag-and-drop canvas: entry triggers, delays, branches, and message nodes, with support for multiple triggers per journey and analytics reported per branch so you can see where a flow converts or leaks. Templates use Liquid personalization with HTML or MJML source editing, keeping email markup in a form developers can review like code.
- 4
For SaaS vendors, the embedded components product white-labels the journey builder, segment editor, and template UI inside your own application, so your customers configure their own messaging without you building an automation engine from scratch.
Feature breakdown
21 features in 5 modulesJourney automation
The orchestration core: low-code flows with engineering-grade transparency.- Drag-and-drop journey builder
- Low-code canvas with entry triggers, delays, branching, and message nodes, approachable enough for non-engineers once data is wired.
- Multi-trigger automation
- Journeys can start from multiple triggers rather than forcing one flow per entry condition.
- Branch-based analytics
- Performance reported per journey branch, exposing where flows convert or leak instead of one blended stat.
- Open-source engine
- The entire platform is MIT-licensed on GitHub, so behavior is inspectable and extensible at the source level.
Segmentation and data
Warehouse-native data plumbing instead of a proprietary CDP.- Unlimited AND/OR segment conditions
- Segments compose arbitrary boolean logic over traits and events with no condition caps.
- REST API ingestion
- First-party API for identifying users and streaming events from your product.
- Segment.com integration
- Plug into an existing Segment pipeline rather than instrumenting a second SDK.
- Polytomic reverse-ETL
- Pull user data directly from databases and warehouses, treating the warehouse as the source of truth.
- Self-hosted data control
- Run the full stack in your own infrastructure so customer data never transits a third party, the decisive feature for regulated verticals.
Messaging and templates
Bring-your-own-provider delivery with developer-grade templating.- Email via major ESPs
- Connect SendGrid, Amazon SES, Postmark, Resend, or generic SMTP; Dittofeed orchestrates, your provider delivers.
- SMS via Twilio
- Text messaging through Twilio and similar providers connected through integrations.
- Webhook channels
- Arbitrary channels (Slack, WhatsApp, mobile push) driven by webhook nodes, documented with video tutorials.
- Liquid personalization
- Standard Liquid templating over user traits and events for per-recipient content.
- HTML and MJML editing
- Email source editable as HTML or MJML, keeping templates reviewable and versionable like code.
Embedded and white-label
Messaging automation as a component of someone else's SaaS.- Embedded components
- White-labeled journey, segment, and template UI that SaaS vendors embed in their own products, launched publicly on Product Hunt and via YC.
- White-label deployments
- A dedicated white-label offering strips Dittofeed branding for agencies and platforms reselling messaging capability.
- Multi-tenant advanced auth
- Enterprise licenses add multi-tenancy and advanced authentication for platforms serving many end customers.
Deployment and operations
Run it yourself free, or pay for the hosted version.- Free self-hosting
- MIT license, deployable via Render or your own infrastructure, with no license fee at any scale.
- Managed cloud
- Cloud Pro at $75/month covers 10,000 monthly unique users with usage-based overage tiers above that.
- Support Pro
- A paid support add-on: dedicated Slack Connect, prioritized feature requests, faster responses, bi-monthly calls, and implementation help.
- Enterprise licenses
- Quoted self-hosted and cloud enterprise tiers add multi-tenant auth, white-labeling, embedded components, and priority support.
Use cases
4 documentedCTO at a healthtech startup
Patient engagement messaging (appointment reminders, care follow-ups) cannot flow through a third-party SaaS without triggering a bruising compliance review of the vendor.
Self-hosted Dittofeed keeps all patient data inside the company's own infrastructure while the care team gets a visual journey builder, collapsing the vendor-review problem into an internal deployment decision.
Engineering-led SaaS replacing ad-hoc email scripts
Lifecycle emails live in cron jobs and one-off scripts against SendGrid; marketing wants onboarding journeys but nobody wants to buy and re-instrument a proprietary platform.
Dittofeed sits on the existing SendGrid account and Segment pipeline, giving marketing a journey canvas while engineering keeps the delivery stack and data flow it already trusts.
B2B SaaS founder who needs messaging as a product feature
Customers keep asking for automated notifications and campaign features inside the product, and building an automation engine in-house would take quarters.
Embedded components put a white-labeled journey builder and segment editor inside the product in weeks, with Dittofeed as infrastructure rather than a visible vendor.
Cost-conscious startup priced out of engagement suites
Braze-class orchestration is the requirement, but the budget is a fraction of enterprise pricing and the team has DevOps capacity to spare.
Free self-hosting delivers journeys, segments, and templates at infrastructure cost only, with the $75/month cloud as a fallback when operating it stops being worth the savings.
Pricing
from $0 self-hosted; $75/mo Cloud ProOpen-core: free MIT-licensed self-hosting, a usage-based managed cloud, and quoted enterprise licenses for multi-tenant, white-label, and embedded use.
| Plan | Price | Includes |
|---|---|---|
| Self-hosted (open source) | $0 forever |
|
| Cloud Pro | $75 per month |
|
| Enterprise (self-hosted or cloud) | Custom quoted |
|
Add-ons
- Support Pro (Quoted): Dedicated Slack Connect, prioritized feature requests, faster responses, bi-monthly Zoom calls, implementation assistance.
Billing notes
- Delivery costs are always extra and always yours: SendGrid, SES, Postmark, Resend, or Twilio bills arrive separately, since Dittofeed orchestrates rather than sends.
- Cloud overage prices decline steeply with scale ($0.004 down to $0.001 per user), so large audiences stay cheap relative to profile-billed competitors.
- Self-hosting's real price is operational: engineer time for deployment, upgrades, and monitoring replaces the subscription fee.
- Enterprise, white-label, and Support Pro pricing are all quote-only, as of August 2026.
Value assessment: Priced as software, Dittofeed is nearly unbeatable: $0 self-hosted or $75/month managed for orchestration that structurally resembles what Braze and Customer.io charge hundreds to thousands for, with per-user overage rates an order of magnitude below Customer.io's $0.009 profile overage. Priced as a total system, the math is subtler: you are separately paying an ESP, possibly Twilio, and, if self-hosting, your own engineers' hours. For teams that already own those pieces, Dittofeed adds the missing orchestration layer at near-zero marginal cost; for teams that own none of them, an integrated platform can genuinely be cheaper in practice.
Strengths & limitations
Strengths
- Only credible open-source option in the category: MIT-licensed, self-hostable, inspectable, with vendor lock-in explicitly designed out.
- Self-hosting solves data-residency and compliance problems by construction, which no amount of certification paperwork from SaaS rivals fully matches for regulated teams.
- Embedded components and white-labeling serve a use case, messaging automation inside your own SaaS, that closed competitors do not address at all.
- Bring-your-own-ESP architecture means no forced migration of delivery infrastructure and no markup on sending; it composes with SendGrid, SES, Postmark, Resend, SMTP, and Twilio.
- Founder DNA fits the problem: one founder helped architect messaging infrastructure at Braze, and the product's data model shows it.
- Cloud pricing ($75/month for 10k users, declining overages) undercuts every proprietary competitor at comparable audience sizes.
Limitations
- Two-founder company: roadmap velocity, support depth, and long-term durability all carry early-stage risk that no license model removes.
- No delivery layer of its own; deliverability, warm-up, and sender reputation are entirely your problem via your chosen ESP.
- Feature surface trails mature rivals: no native push or in-app SDK channel (webhooks stand in), no lead scoring, no built-in forms, thin analytics beyond branch metrics.
- No published SOC 2 or ISO certification; the compliance story is 'self-host it,' which only helps buyers with infrastructure teams.
- Templating in Liquid, HTML, and MJML assumes developer comfort; pure marketing teams will find sharp edges throughout.
- Small integrations catalog (API, Segment, Polytomic, ESP connectors) next to the 50-plus-connector libraries of commercial competitors.
Head-to-head comparisons
3 alternativesDittofeed vs Customer.io
from $100/mo (Essentials)Customer.io is the finished commercial product: managed delivery, five native channels, compliance certifications, a CDP, and 14 years of polish from $100/month. Dittofeed is the open infrastructure version of the same idea: journeys and segments you can self-host free or run for $75/month on your own ESP. Regulated or engineering-led teams that need data control pick Dittofeed; teams that want outcomes without operations pick Customer.io.
Full Dittofeed vs Customer.io comparisonDittofeed vs Bento
from $29/mo (up to 5,000 active users, unlimited marketing sends)Both are lean-team products at disruptive prices, but they disrupt differently: Bento is a closed, bootstrapped, full-stack ESP with its own delivery and deliverability craft at $29/month, while Dittofeed is open-source orchestration that deliberately owns no delivery at all. Senders who want inbox placement handled for them choose Bento; teams that want source code, self-hosting, or embedded messaging choose Dittofeed.
Full Dittofeed vs Bento comparisonDittofeed vs Encharge
from $79/mo (Growth, 2,000 subscribers, billed annually)Encharge sells a marketer-operated experience: polished flow builder, CRM and billing integrations, lead scoring, live-chat support, from $79/month all-inclusive of sending. Dittofeed at a similar cloud price assumes engineers in the loop and an ESP on the side, repaying that burden with open source, warehouse-native data flow, and white-label embedding. Marketing-led teams pick Encharge; engineering-led teams pick Dittofeed.
Full Dittofeed vs Encharge comparisonImplementation & onboarding
- Setup time
- Cloud: an afternoon to connect an ESP and start a journey, then days to wire real data via API, Segment, or Polytomic. Self-hosted: add deployment and configuration time, realistic at days to a couple of weeks depending on your infrastructure standards.
- Learning curve
- Low for the journey canvas itself; moderate overall because data wiring, Liquid/MJML templating, and provider configuration are inherently technical.
- Onboarding
- Self-serve docs and community by default; Support Pro buys Slack Connect access, implementation assistance, and bi-monthly calls with the team.
- Migration notes
- Migrating in means re-pointing your event stream and rebuilding journeys, the same as any platform switch, but keeping your existing ESP removes the delivery-migration half entirely. Migrating out is the category's easiest: the software is open source, so the escape hatch is the product's stated design goal.
Platform, API & security
- Platforms
- Web app (cloud or self-hosted)REST APIDocker-based self-host deployment
- API
- REST API for users and events; Segment integration; Polytomic reverse-ETL from databases and warehouses; webhook nodes for arbitrary outbound channels.
- Compliance
- No published SOC 2 or ISO certification; self-hosting keeps data entirely within your own infrastructure and compliance boundary
- Data residency
- Wherever you deploy it, when self-hosted; cloud residency not publicly specified.
- SSO
- Multi-tenant advanced auth available on enterprise licenses; standard auth on Cloud Pro.
- Security notes
- The MIT-licensed codebase is publicly auditable, and the self-hosted path means Dittofeed the company never touches your customer data, a materially different trust model from every SaaS competitor in this category.
Support & resources
- Channels
- Community and documentationSupport Pro add-on (Slack Connect, priority responses, implementation help)Priority support on enterprise licenses
- Documentation
- Developer-oriented documentation covering deployment, API, integrations, and channel setup, including video tutorials for webhook channels like Slack and WhatsApp.
- Community
- Open-source community on GitHub with active releases (v0.23.0 era as of this review) and Docker images updated continuously.
Company
- Founded
- 2022
- Headquarters
- Los Angeles, California, US
- Ownership
- Venture-backed startup (Y Combinator)
- Founders
- Maxwell Gurewitz (co-founder; ex-Braze, ex-OpenTable engineering), Chandler Craig (co-founder; ex-Sony Music, B2C startup marketing)
- Employees
- 2 (founders; per Y Combinator profile)
- Funding
- Y Combinator backing (Summer 2022 batch); further rounds not disclosed.
Funding history
| Round | Amount | Year | Notes |
|---|---|---|---|
| Accelerator | Not disclosed | 2022 | Y Combinator, Summer 2022 batch. |
Timeline
- 2022Founded by Maxwell Gurewitz and Chandler Craig; joins Y Combinator's Summer 2022 batch with the goal of an open-source alternative to Braze, Klaviyo, and Customer.io.
- 2023Public Launch HN debut as an MIT-licensed customer engagement platform with journeys, segments, and bring-your-own-ESP delivery.
- 2024Warehouse-native data paths mature: Segment integration and Polytomic reverse-ETL position the warehouse as source of truth.
- 2025Embedded components launch on Product Hunt, adding white-labeled messaging automation for SaaS products.
- 2026Steady release cadence continues (v0.23.0 era, Docker images updated near-daily) with cloud, white-label, and enterprise licenses in market.
Integrations
- SendGrid
- Amazon SES
- Postmark
- Resend
- Generic SMTP
- Twilio (SMS)
- Segment
- Polytomic (reverse-ETL)
- Webhooks (Slack, WhatsApp, mobile push, custom channels)
- REST API
Frequently asked questions
10 questionsWhat is Dittofeed?
Dittofeed is an open-source customer engagement platform: a journey builder, segmentation engine, and template system that orchestrates messages across email, SMS, and webhook channels using your own delivery providers. It is MIT-licensed, self-hostable for free, and also offered as a managed cloud from $75/month.
Is Dittofeed really free?
The software is: the full platform is MIT-licensed on GitHub and self-hosting carries no license fee at any scale. Your real costs are infrastructure, engineer time to deploy and operate it, and your delivery providers' bills; the managed cloud at $75/month exists for teams that would rather pay than operate.
How much does Dittofeed Cloud cost?
Cloud Pro is $75/month including 10,000 monthly unique users, with overages at $0.004 per additional user up to 100,000, $0.002 to 500,000, and $0.001 beyond, plus a 14-day free trial. Enterprise cloud and self-hosted licenses with multi-tenant auth, white-labeling, and embedded components are quoted.
Does Dittofeed send email itself?
No. Dittofeed orchestrates; delivery goes through your connected provider, SendGrid, Amazon SES, Postmark, Resend, or generic SMTP for email, and Twilio for SMS. That means no markup on sending and no forced ESP migration, but also that deliverability and sender reputation remain entirely your responsibility.
What channels does Dittofeed support?
Email and SMS natively through connected providers, and effectively anything else through webhook nodes: the team documents Slack, WhatsApp, and mobile push patterns with video tutorials. There is no first-party mobile SDK channel comparable to Customer.io's in-app messaging.
What are Dittofeed's embedded components?
White-labeled versions of the journey builder, segment editor, and template UI that SaaS companies embed inside their own products. It turns messaging automation into a feature you ship to your customers, with Dittofeed as invisible infrastructure, a use case closed platforms in this category do not serve.
Who is behind Dittofeed?
Co-founders Maxwell Gurewitz, previously a senior engineer at Braze and OpenTable who helped scale messaging to billions of users, and Chandler Craig, previously in marketing at Sony Music and B2C startups. The company came through Y Combinator's Summer 2022 batch and remains a two-person team.
Is Dittofeed suitable for regulated industries?
That is one of its strongest fits, via self-hosting: healthtech, fintech, and similar teams run the platform inside their own compliance boundary so customer data never reaches a third party. Note the company itself publishes no SOC 2 or ISO certification, so the cloud product answers compliance questions less cleanly than the self-hosted one.
How does Dittofeed get user data?
Three paths: its REST API for direct identification and event streaming, a Segment.com integration for teams with an existing CDP pipeline, and Polytomic reverse-ETL for pulling users and traits straight from databases and warehouses. The warehouse-native path is a deliberate architectural bet.
What are the risks of choosing Dittofeed?
Vendor size and product maturity. Two founders means constrained support and roadmap bandwidth, and the feature surface (analytics, integrations, non-email channels, marketer ergonomics) trails platforms with a decade's head start. The open-source license is the mitigation: even in a worst case, the code and your deployment remain yours.
Editorial verdict
Dittofeed is the category's infrastructure option, and for the right buyer that is exactly the point: engineering-led teams get Braze-shaped orchestration as auditable open source, regulated companies get data control by construction, and SaaS vendors get an embeddable messaging engine nobody else offers. Judged as a marketer-facing SaaS it loses to everything else in this category on polish, channels, and hand-holding; judged as open infrastructure it has no direct competitor at all. Buy it for the license, the escape hatch, and the embedding story, and staff accordingly; if no engineer will own it, buy something finished instead.
Written by the SaaSTracker editorial team. Awards, when shown, are judged against the published criteria in our methodology.