PillDrops Notification Cost Calculator

Models the real monthly cost of your Supabase → FCM push pipeline. Local alarms (AlarmManager / UNNotification) are free and not shown.
Event flow (from supabase/functions/notify/index.ts):
DB row change → Supabase webhook → Edge Function (notify) → FCM HTTP v1 API (free) → device banner
● Paid surface: Supabase invocations + egress    ● Free: FCM pushes, APNs, on-device banner render

Usage Assumptions

Supabase Tier

Monthly Cost

Total estimated monthly cost
$0.00
— per month
Recommended tierFree
Cost per notification$0.0000
Cost per senior / month$0.0000
Cost per senior / year$0.0000

Volume Breakdown

Event typeDirectionPushes/moInvocations/mo
Total 0 0

Cost Components

Supabase plan (base fee)$0.00
Extra Edge Function invocations$0.00
Egress (est. ~2KB/push)$0.00
FCM (Firebase Cloud Messaging)Free ∞
APNs (Apple Push)Free ∞
Local AlarmManager / UNNotifFree ∞
How the math works. One DB row change (dose_event, shared_medication, shared_appointment) triggers exactly 1 Edge Function invocation. Inside the function, it fetches the target push_tokens and calls FCM once per token. Dose events fan out to all caregivers of a senior; med/appt/reminder events target the single senior. FCM and APNs are free at any volume — the only paid axes are Supabase invocations and egress.

Pricing baselines (2026): Free tier = 500K invocations/mo + 5GB egress, $0. Pro = 2M invocations + 250GB egress, $25/mo, then $2/extra million invocations and $0.09/extra GB egress. Team = 10M invocations + 500GB egress, $599/mo. Adjust inputs to model your actual usage — this file is the source of truth.