Selfcommit.dev VS Oncallizer

Oncallizer's answer:

Next.js, React, and TypeScript, with Supabase for accounts and storage. The schedule generator runs entirely in the browser — no data leaves your device unless you save to an account.

Oncallizer's answer:

Most on-call tools (Amion, QGenda) are enterprise systems with sales calls, contracts, and per-seat pricing. Oncallizer is the opposite: open the site, build a fair schedule in minutes, export it to Excel — And where most tools stop at “filled slots”, Oncallizer shows you a fairness score you can defend when someone asks why they got three weekends.

Oncallizer's answer:

Oncallizer doesn’t just fill a calendar — it generates hundreds of candidate schedules and scores each one with Jain’s fairness index, so the schedule you get is measurably the fairest one. Weekend load, heavy days, and per-person caps are all enforced rather than silently broken, and roles (juniors vs seniors) are each balanced against their own fair share. It’s also free to use for now with no signup — the full builder runs in the browser.

Oncallizer's answer:

Oncallizer was born from watching schedulers spend hours in spreadsheets trying to balance weekend calls by hand — and still getting accused of unfairness. The fix: encode the rules people actually argue about (weekends, heavy days, caps, seniority), let an algorithm find the fairest arrangement, and show the fairness score so nobody has to take it on faith.

Oncallizer's answer:

Whoever owns the on-call schedule: chief residents and program coordinators at residency and training programs, ward and unit schedulers, and team leads at any organization that shares call duty and argues about weekends.