// the take
Caffeinate is a Rails engine that moves scheduled message sequences (onboarding emails, drip campaigns, periodicals) out of ad-hoc ActionMailer/Sidekiq callbacks into a dedicated Dripper DSL with its own subscription and scheduling models. It's for Rails teams who've already felt the pain of unsubscribe logic and delay math scattered across mailers and background jobs.
Forces a real separation of concerns: mailers just build a `mail` object from a `Caffeinate::Mailing`, while the Dripper owns scheduling, unsubscribe state, and before/after callbacks (including `throw(:abort)` to halt a mailing mid-chain). Scheduling supports per-subscriber timezones and business-day-only delays, which is genuinely fiddly to get right by hand. It's job-queue agnostic (no hard Sidekiq/ActiveJob dependency), ships RSpec matchers and test helpers (`lib/caffeinate/rspec`) for testing subscriptions/unsubscribes, and supports polymorphic and multiple associations so a subscriber isn't locked to a single `User` model.
There's no built-in scheduler — `Dripper.perform!` has to be wired into your own cron or sidekiq-cron setup, which is an easy step to get wrong (miss a run and delays silently drift). The admin web UI is a separate gem (caffeinate-webui) rather than bundled, so out-of-the-box you're managing campaigns through the console or custom views. The maintainer openly describes activity as low ('not a lot of activity here') with effectively one person behind it, which matters for a library sitting in your email-delivery critical path. The README's performance claim ('tested against large databases at AngelList') is asserted with no numbers or benchmarks attached, so it's not something to plan capacity around.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →