openOpen. no one's helping yet. Jump in!

Tiny SaaS: Stripe works but gating pro features is a mess

Stuck point

payments go through and the subscription lands in my DB, but my is-this-user-pro checks are copy-pasted everywhere and already contradicting each other.

for real, it's

68%−22

progress status — how done is it, really?

User thinks it's90% complete

AI diagnosis68% complete

that 22-pt gap is probably exactly where the last step is hiding.

Built with

Supabase · Backend & DB

Vercel · Hosting & Deploy

What I need help with

a single clean pattern to gate features by plan without spaghetti.

Your first move

Write one isPro(userId) helper that reads the subscription row once, and gate every pro feature through it instead of scattered checks.

the road everyone walks

every shipped app walked this exact road. being stuck partway isn't failing, it's the middle of the climb — and the AI read (68%) puts this project roughly here.

runs on your machine

code backed up

live on the internet

people can sign in

roughly herethe core feature works

real people use it

next stop: real people use it · they find it and come back.

want YOUR whole road plotted. every step, tool & why? plan your build

know the missing piece? drop it in the room below.

help out

Project story›

What's already working

Stripe checkout + webhook + subscription row all working.

The goal

a clean paywall so pro features unlock reliably the second someone subscribes.