Flowripple

Shiv Sarthak, Emad Ibrahim, and Lincoln Stewart looked at how SaaS teams handle backend workflows and saw a mess—cron jobs held together with duct tape, spaghetti code, and email templates hardcoded everywhere. So they built Flowripple, a durable execution engine that triggers stateful, multi-step workflows from your code with a single line. One HTTP call. That's it.

Most automation tools were built for marketers clicking buttons in a browser. Flowripple was built for developers who actually ship code. You send events via simple HTTP requests or their SDK, map out your logic in a visual builder—triggers, actions, conditions, delays—and then just ship. Their execution tracing lets you inspect exactly what happened at every step, so when something breaks you don't have to play detective with your logs. The stateful logic engine handles complex timing and branching without you managing state machines or database crons. Built-in retries are included—none of that "pay extra for reliability" nonsense.

Compared to Zapier, Flowripple won't bankrupt you at scale. Compared to n8n, you won't need a DevOps team to keep it running. It's predictable flat monthly pricing, zero DevOps, fully managed. Purpose-built for SaaS, not some generic tool they bolted onto your industry. If your backend is held together by prayers and cron jobs, Flowripple might be the upgrade you've been putting off.

They're building in public and open to anyone who wants to stop hardcoding their user journey.