Scheduling and meetings decision

Roster for Slack

A competent technical user can build and run a minimal Rosters-for-Slack replacement in about a week and low monthly hosting cost; there are no evident durable moats on the product pages that prevent DIY.

Visit website

Built by Justin Butlion, who ships 3 products in this index

You pay

$8/mo

$96/yr

Read off the official pricing page.

You’d pay instead

$50one-off30 h to build

$35/mo3 h/mo upkeep

On cash alone, building overtakes the subscription at 5 seats.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Roster for Slack alternatives, with the arithmetic →

What a replacement has to do

  • Create and store rosters (date/time + assignee), assign people to shifts, and send scheduled Slack notifications/messages to assignees.

What it still won’t have

  • Marketplace listing and distribution handled for you (Slack App Store onboarding and updates)
  • Commercial support SLAs (48hr/24hr/priority) and customer support
  • Polished multi-tier pricing, billing, and account management flows
  • Any monday.com integrations or prebuilt templates referenced on the site

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 5 seats.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a self-hosted Slack roster service using Node.js (Express) + Postgres + a background worker (BullMQ) deployed to a single VPS. Core features: Slack OAuth install and bot user; REST CRUD for rosters (date, time, assignee); scheduled worker that posts reminders to Slack using chat.postMessage; slash command and interactive message handlers for assigning/swapping shifts; a minimal web admin UI to list/manage rosters and users. Out of scope: multi-tenant billing, advanced analytics, monday.com integrations, and enterprise SLA. Include input validation, retries for failed Slack API calls, logging, basic tests for API and scheduling logic, and an automated deploy script (Docker + docker-compose).
How we checked3 sources · 2/3 runs agreed · evidence score 89

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 3 cited sources+3
  • Price verified on pricing page+3
  • Evidence score89

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded