Skip to content
fromHello
Best · Alternatives

Dittofeed alternatives (2026)

Dittofeed's maintainer said in August 2026 that the project is in maintenance mode and feature development has stopped. The software still runs and the cloud is still sold, so most teams are not in a hurry. When you do move, Mautic is the like-for-like open-source option, Customer.io the like-for-like managed one, Loops the cheapest with real journeys, and Novu only if you needed notification plumbing.

Updated 6 Sept 20269 min readBy fromHello
Join the waitlistStar on GitHub
Key takeaways
  • 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.
  • 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.
  • 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.
  • Only Mautic gives back the full Dittofeed shape in open source: self-hosted, bring-your-own sending provider, visual journeys and segments. Everything else asks you to give one of those up.

On 10 August 2026 a user asked whether Dittofeed was still active. The maintainer answered that the project is in maintenance mode, promising occasional bug fixes but halting feature development, and closed the issue 94 seconds later. 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: the most-linked one was last updated in 2023 and still recommends Laudspeaker, a project whose website has been offline for months. 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. Only one option keeps all four. Every fact here was checked against each vendor's own docs, pricing pages and repository in the first week of September 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 is listed last and held to the same standard, including where it is not ready.

The shortlist
  1. 01
    MauticGPLv3

    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 only destination here 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 shipped on 2 September 2026, on a steady release line, 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
    • Campaign steps do not fire on their own. Mautic's own docs require a cron job running mautic:campaigns:trigger, so event-triggered journeys run at cron latency rather than in real time — a real change if your Dittofeed journeys reacted immediately.
    • 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.
    Compare in depthVisit site
  2. 02
    Customer.ioProprietary (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 both self-hosting and your own sending provider: Customer.io is the infrastructure, so the data-ownership argument that led you to a self-hosted tool does not survive the move.
    • 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.
    Compare in depthVisit site
  3. 03
    LoopsProprietary (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.
    Compare in depthVisit site
  4. 04
    NovuMIT

    Best for: Teams who discover, on inspection, that they were using Dittofeed as notification plumbing rather than as a growth tool.

    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 a growth platform. 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.
    Compare in depthVisit site
  5. 05
    fromHelloAGPLEarly access · waitlist

    Best for: Small teams that want the open-source platform and an AI growth team to run it — once early access opens.

    Strengths
    • The only option here that pairs the open-source platform with eight AI specialists who set strategy, build journeys, write copy, and run experiments — you approve, edit, or auto-ship.
    • A complete platform underneath rather than a chat layer over one: email, SMS, in-app, web push, ad audiences, a 16-node visual journey builder, real-time segments, GDPR consent tracking, and a first-party JS/TS SDK.
    • AGPL-licensed and self-hostable on Postgres + Redis, so your customer data stays on your own infrastructure.
    Watch-outs
    • The hosted product and the agents are in early access behind a waitlist — Mautic, Customer.io, Loops and Novu you can adopt today.
    • Hosted pricing is announced at general availability; self-hosting the open-source platform is free.
    Join the waitlist
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 has had no new commits since March 2026.

  • 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: the one bug report filed since the comment is still open and a community fix has sat unmerged since mid-August, 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.

Sources

See the platform the team runs.

Join the waitlistStar on GitHub
Related comparisons
Related guides
Best-of & alternatives
Switching tools
How to switch email platforms without losing deliverability
Early access

Put your growth teamon autopilot.

Early access opens gradually, so the team tunes to real use cases. Small teams with big ambitions go first.

Not ready to share an email? It's open source. Run it yourself today. View on GitHub

No spam. One email when your spot opens. Unsubscribe at any time.