Dead-man's switch for Rails schedulers

Know when jobs stop running.
Before your customers do.

Your error tracker catches exceptions. Your queue monitor shows failures.
Neither catches the silent death — when a recurring job simply stops running. No error. No alert. Nothing.

JobTick monitors every scheduled job in your Rails app — Whenever, Solid Queue, Sidekiq — and alerts you the moment any job goes quiet. Zero configuration per job.

No credit card required. Cancel anytime.

3
Schedulers supported
Whenever · Solid Queue · Sidekiq
0
Config changes per job
2
Lines to install
14
Day free trial
no card required
Live dashboard

See every job. Get alerted on silence.

One place to see the health of your entire scheduling stack. Auto-synced from your config files on every deploy.

production · my-rails-app
updated just now
InvoiceJob hasn't run in 26 hours — expected every 24h. No exception raised. Scheduler process may have crashed.
NightlyReportJob solid_queue
2 hrs ago · 4.2s
healthy
InvoiceJob whenever
26 hrs ago
silent
SyncInventoryJob solid_queue
58 min ago · 1.1s
healthy
HourlyDigestWorker sidekiq
2 hrs ago
late
CleanupExpiredTokensJob whenever
6 hrs ago · 0.3s
healthy
Why this exists

The failure mode nobody talks about

Every Rails team hits this eventually. Usually discovered by a customer, not an engineer.

3 days of missed billing
"

Our billing job silently stopped on a Friday evening. We found out Monday morning when customers asked why their invoices hadn't arrived. Zero alerts the entire time.

Alex M. — Backend Engineer, B2B SaaS
11 days undetected
"

A kernel update stopped our cron daemon on boot. Solid Queue workers came up fine, but the Whenever jobs just stopped. We only noticed during a routine audit.

Priya K. — Platform Engineer, e-commerce
30 jobs, half still dark
"

I already ping our most critical jobs manually. But nobody wants to touch 30+ job files, so half our schedule has zero coverage.

James T. — Senior Developer, fintech startup

JobTick catches this before your customers do. Start monitoring free →

Zero configuration setup

Add the gem. That's it.

JobTick reads your existing scheduler config on deploy. No per-job changes. No wrapping. No curl pings.

 Gemfile
# Add to your Gemfile
gem 'jobtick'
 config/initializers/jobtick.rb
that's it
JobTick.configure do |config|
  config.api_key = ENV['JOBTICK_API_KEY']
end

# Deploy. JobTick reads your schedule
# config and registers every job.
# No job files touched.
 config/schedule.rb (Whenever)
auto-discovered
# Your existing file — unchanged
every 1.day, at: '2:00 am' do
  runner 'InvoiceJob.perform_later'
end

every :hour do
  runner 'SyncInventoryJob.perform_later'
end
 config/recurring.yml (Solid Queue)
auto-discovered
# Your existing file — unchanged
nightly_report:
  class: NightlyReportJob
  schedule: every day at 3am

sync_rates:
  class: ExchangeRateJob
  schedule: every hour
What you get

Everything you need.
Nothing you don't.

Silent failure detection

Alerts when a job stops running entirely — not just when it raises an exception. The failure mode every other monitor misses.

Auto-sync on deploy

Add a job to your schedule, it appears in your dashboard on next deploy. Remove one, its tracked job is removed automatically.

Run history & trends

Every execution logged: start time, duration, exit status. Spot when a job starts getting slower before it becomes an incident.

All three Rails schedulers

Whenever, Solid Queue recurring jobs, and Sidekiq periodic jobs. One tool, your entire Rails scheduling stack.

Maintenance windows

Deploying at 3am? Snooze any tracked job for a set period. No false alerts during expected downtime.

Email, Slack & PagerDuty

Get notified where your team already works. PagerDuty integration on Studio and Agency plans for on-call rotation support.
How JobTick compares

Built for Rails.
Zero instrumentation.

Every other solution requires manual instrumentation per job. JobTick reads your config and monitors everything automatically.

JobTick vs alternatives: feature comparison for Rails job monitoring tools
Tool Whenever auto-discovery Solid Queue auto-discovery Catches silence Zero config per job Price
JobTick ✓ yes ✓ yes ✓ yes ✓ yes from €14/mo
Healthchecks.io ✗ no ✗ no ✓ yes ✗ manual curl $5/mo
Cronitor ✗ no ✗ no ✓ yes ✗ wrap per job $29/mo
AppSignal ~ errors only ~ errors only ✗ no ✗ no $19/mo+
Mission Control ✗ no ~ local only ✗ no ✓ yes free
Pricing

Simple, transparent pricing.
No surprises.

Start free for 14 days. No credit card required. Upgrade or cancel anytime.

Monthly Yearly
Save 2 months

All prices in EUR, excl. VAT

Indie
14
per month

Perfect for solo developers and indie apps. Everything you need to monitor a single project.

Start free trial
  • 1 project
  • 30 tracked jobs
  • 1 seat
  • 60-day run history
  • Email alerts
  • Slack notifications
Agency
99
per month

For teams managing many client apps. Unlimited projects, maximum history, and a full team.

Start free trial
  • Unlimited projects
  • Unlimited tracked jobs
  • 10 seats
  • 2-year run history
  • Email & Slack alerts
  • PagerDuty integration
FAQ

Common questions.
Straight answers.

Does it require changes to my job files?

No. JobTick reads your existing scheduler config (schedule.rb, recurring.yml, sidekiq.yml) on deploy. Your job files stay exactly as they are.

What schedulers are supported?

Whenever, Solid Queue recurring jobs, and Sidekiq periodic jobs. All three are auto-discovered from config files.

How does silence detection work?

Your job pings JobTick when it completes. If the expected ping doesn't arrive within a configurable grace period, we alert you. The job doesn't need to raise an exception — we catch pure silence.

How is this different from error trackers?

Error trackers like Sentry or Bugsnag only fire when an exception is raised. Silent failures — where the job simply doesn't run — produce no exception. JobTick catches what they miss.

Can I monitor multiple environments?

Yes. A "project" maps to a Rails environment (production, staging, etc.). Each project has independent tracked jobs, alert channels, and notification settings.

What happens at the end of the trial?

Your account stays readable but alerting pauses until you subscribe. You choose a plan at any point during or after the trial. No surprise charges.

Is there a free plan?

There is no permanent free tier, but every account starts with a 14-day free trial — no credit card required. If you need something not covered by existing plans, get in touch.

Can I cancel any time?

Yes. Cancel from the billing page in one click. Your subscription stays active until the end of the billing period. No questions asked.

Stop finding out from
your users.

Start monitoring in minutes. 14-day free trial, no credit card required.