Runnel 2.8: replay any workflow from a failed step.Read the release

Skip to content
Runnel

Customers

Teams that stopped babysitting their queues

Travel bookings, clinic software, e-commerce, fintech. What they ran before, what they built on Runnel and what changed, in their own figures.

Some of the teams running on Runnel

In their words

  • “We build products for about a dozen clients a year. Runnel is now the default for anything that runs in the background, because handing over a dashboard is easier than handing over a cron tab.”

    Saoirse ByrneTechnical director, Brindle
  • “Our ingestion pipeline is 40 workflows and about 9 million runs a day. Concurrency keys per data source replaced a rate limiter we had rewritten three times.”

    Daniel OyelaranPrincipal engineer, Halyard
  • “Settlement runs at 02:00 London time every night, including the night the clocks change. That sounds like a low bar. Our old scheduler didn’t clear it.”

    Hannah LindqvistEngineering manager, Ledgerline

Want to talk to a team like these?

We can put you in touch with a customer on a similar stack, or walk through your current setup with one of our engineers.