Skip to content

Key takeaways

  1. The status change is real but quiet: it was posted in a GitHub issue titled as a user question and closed within two minutes, so most people running Dittofeed have not heard about it.

  2. Maintenance mode is not abandonment. The MIT core still runs, the hosted cloud is still sold, and nothing about your install stopped working the day the comment was posted.

  3. You are not locked in. The admin API returns journeys, segments, user properties, users, raw events, deliveries and subscription state, and ingestion was Segment-compatible — so the exit is an export, not a rebuild from memory.

  4. Mautic gives back the full Dittofeed shape in mature open source: self-hosted, bring-your-own sending provider, visual journeys and segments. Self-hosted fromHello keeps all four on a younger codebase; everything else asks you to give one of those up.

The shortlist

On 10 August 2026 a user asked whether Dittofeed was still active. The maintainer answered that the project is in maintenance mode, with infrequent bug fixes and no new features, and closed the issue a second later, 94 seconds after it was opened. That is the whole announcement, and it never left the issue tracker: the public changelog has not been updated since November 2024, and the pricing page carries no note either. So most people running Dittofeed do not know, and the directories ranking for this query are worse than silent: some still recommend Laudspeaker, whose website no longer loads and whose own README says it is no longer developed or supported. This page is what we would want to read in that position — what actually changed, why there is less urgency than it feels, what your data looks like on the way out, and the four places teams land.

How we chose

We sorted destinations by what you have to give up to get the Dittofeed shape back: self-hosting, bringing your own sending provider, event-triggered journeys, and dynamic segments. Two keep all four: Mautic, the mature one, and self-hosted fromHello. Every fact here was checked against each vendor's own docs, pricing pages and repository on 13 October 2026, and the Dittofeed facts come from its own issue tracker, docs and pricing page rather than from a directory. Prices on several of these sites render only in a real browser, so a plain fetch shows nothing — we checked them rendered. We build fromHello, so it never goes first, and it is held to the same standard, including where it falls short.

  1. Best for

    Teams that want everything Dittofeed gave them — self-hosted, own sending provider, visual journeys, segments — and will accept a PHP stack and cron timing to keep it.

    Strengths

    • The mature destination that keeps all four properties at once: you host it, you point it at your own provider, and you get a drag-and-drop campaign builder with conditions and decisions plus dynamic segments.
    • Actively developed, which is the whole point of the move: version 7.2.1 shipped on 23 September 2026, three weeks after 7.2, and commits land weekly.
    • GPLv3 with no paid core tier, community-governed, and a large plugin ecosystem — so the licence question that made you pick open source in the first place is settled the same way.

    Watch-outs

    • Campaigns lean on cron. Mautic's own docs require cron jobs for segments, campaign membership and mautic:campaigns:trigger, so segment-based entry, delays and the paths for contacts who did not act wait for the next run; only actions right after a contact's own action, such as an open or a form submit, run immediately. A real change if your Dittofeed journeys reacted to every event in real time.
    • Bring-your-own sending is genuine but uneven: Mautic notes that third-party Symfony transports do not support batch sending and do not handle bounce callbacks, so provider choice matters more than it did.
    • It is a heavier stack to operate — PHP, MySQL, cron, upgrades — which is the opposite of what most people want on the day they discover their current tool stopped shipping features.
  2. fromHello

    AGPL-3.0Cloud in early access

    Best for

    Dittofeed teams who want to stay open source and self-hosted, on a platform under active development with in-app and ad audiences built in — with fromHello Cloud in early access.

    Strengths

    • Journeys triggered by what people do: first-party tracking, segments recomputed on every event, and a visual builder with 14 node types across email, SMS, in-app banners and modals and ad audiences, with web push built into the platform. Replies land on the contact's profile and can start a journey.
    • Your own AI plugs in over MCP: 59 tools let Claude, Cursor or any MCP client create segments, journeys and templates and read analytics. No tool sends a message, and a journey your AI builds stays a draft until it is published.
    • Open source under AGPL-3.0: self-host it free on your own Postgres and Redis, or use fromHello Cloud, priced from €39 a month excluding VAT, with unlimited seats.

    Watch-outs

    • fromHello Cloud is in early access through the waitlist; Mautic, Customer.io, Loops and Novu are generally available.
    • No newsletters or one-off broadcasts — messages to many people go out through journeys — and no mobile push or WhatsApp. SMS always goes through your own provider.
  3. Customer.io

    Proprietary (SaaS)

    Best for

    Teams who decide they would rather not operate a messaging platform at all, and want the closest managed match to what they built.

    Strengths

    • The closest feature-for-feature landing spot: the visual workflow builder and segments are in the entry tier, not gated upstairs, so the journeys you modelled in Dittofeed have somewhere to go.
    • It still publishes a price when much of the category has stopped: Essentials starts at $100 a month for 5,000 profiles and a million emails, with published overage rates rather than a call.
    • Its startup programme offers up to twelve months free for up to 30,000 profiles if you have raised under $10 million and have never been a customer — which can make the first year of the move cost nothing.

    Watch-outs

    • You give up self-hosting: Customer.io keeps your data on its own cloud, in the US or the EU, so the data-ownership argument that led you to a self-hosted tool does not survive the move. You can still send email through your own provider over custom SMTP.
    • Pricing is per profile, so the bill grows with your list whether or not you message it — a different shape from a server you already pay for.
  4. Loops

    Proprietary (SaaS)

    Best for

    Small SaaS teams who want event-triggered journeys back quickly and cheaply, and whose Dittofeed install was email-only anyway.

    Strengths

    • It has the part people assume it lacks: workflows trigger on events, contact-property changes and new contacts, with branching, alongside saved segments.
    • The cheapest real journeys on this list — free up to 1,000 contacts, then $49 a month at 5,000, with sends not metered separately on paid plans.
    • A clean, modern developer experience and a fast setup, which is the opposite of the operational weight you are leaving behind.

    Watch-outs

    • No self-hosting and no bring-your-own provider — Loops is the sender, so this is the furthest step from where you started on ownership.
    • Pricing is published only through an on-page slider rather than a table, so budgeting past a few thousand contacts means moving the slider yourself.
    • It is built for SaaS lifecycle email; if your Dittofeed setup leaned on SMS or webhook channels, that does not come with you.
  5. Best for

    Teams who discover, on inspection, that they were using Dittofeed as notification plumbing rather than for marketing automation.

    Strengths

    • Free to start and genuinely bring-your-own: 10,000 workflow runs a month at no cost, with delivery through your own email, SMS and push providers.
    • Self-hostable under an MIT core and very actively developed, with a large community — the health signal you just learned to check.
    • Multi-step workflows with delay, digest and throttle steps, plus an embeddable in-app inbox that Dittofeed never shipped.

    Watch-outs

    • It is notification infrastructure, not marketing automation. Targeting is subscribers and topics, so the behavioural segments you built in Dittofeed have no direct equivalent.
    • Novu's own docs warn that the basic self-host compose file is not production-shaped — the database sits on the same machine and storage is faked — so plan for real infrastructure work.

See fromHello, open-source marketing automation.

FAQ

Common questions

  • Is Dittofeed dead?

    No, and the distinction matters. In August 2026 its maintainer said the project is in maintenance mode: feature development halted, bug fixes opportunistic. An install that worked in July still works, and the code is public under MIT. What stopped is the roadmap — so the honest read is that you have time to choose rather than a reason to panic. Set your expectations from the repository rather than the promise: the default branch went quiet from late March to October 2026, when the maintainer merged three small maintenance fixes, cut new pre-releases and, on 12 October, merged a community fix; the last stable release is still v0.23.0 from December 2025.

  • How would I even know the status changed?

    You would not, easily, which is the practical problem. The statement lives in one comment on an issue titled as a user question, opened and closed within two minutes. The public changelog has not been updated since November 2024 either. If you run Dittofeed, the repository is the honest signal: watch commit activity, releases and how open issues are moving, rather than the marketing pages.

  • Can I get my data out of Dittofeed?

    Yes, and more completely than most self-hosted tools allow. The admin API returns full journey definitions including the builder's nodes and edges, segment definitions, user-property definitions, a paginated user list with properties and segment membership, raw event history with traits and context, delivery records, and subscription-group state. There is also a CSV export, but it covers only segment assignments — the API is the real path.

  • Will I have to re-instrument my product?

    Probably not. Dittofeed's ingestion API is documented as Segment-compatible, with identify, track, page and screen endpoints in Segment's shape. If you fed it from Segment through its webhook source, moving is a destination change with no SDK work at all. If you used Dittofeed's own SDK, the method surface maps one-for-one onto any Segment-style client, so it is a swap rather than a rewrite.

  • What does not survive the move?

    Journey structure has to be rebuilt by hand wherever you land, because no two builders share a node vocabulary — the API gives you the definitions to read, not something another tool can import. Dittofeed's own channel docs list only email, SMS and webhooks and place mobile push and in-app messages in the future, so whatever exists for mobile push in the code, there is nothing configured to carry across. Anything you built against Dittofeed's own admin API stops working, and if you self-hosted, the ClickHouse and Temporal pieces of the stack go away rather than move.

  • We already run it. What should we actually do?

    For most teams, nothing this quarter. The install that worked in July still works, the licence is MIT so you can fix or fork it yourself, and the code is public and stable rather than disappearing. What changes is that you are now the maintainer of last resort: bug reports filed since the comment are still open, and of the community fixes submitted since mid-August, one was merged on 12 October 2026 while the rest are still waiting — so treat repairs as yours to make. The reasonable plan is to export your definitions now while everything is running, keep the install, and move on your own schedule rather than someone else's.

Keep reading

All comparisons

Early access

fromHello Cloud

You didn’t start this to stay small.

Early access to fromHello Cloud opens in stages. Onboarding is hands-on: we help you get set up and bring your contacts over.

We’ll email you when your spot opens. No spam.

Not ready to join? View on GitHub