Pricing page still shows old prices hours after I change them in Supabase

Yes, that line means "serve the cached page and rebuild at most once per hour". For a pricing page with a handful of rows, simply rendering it on every request is fine, a single indexed query is milliseconds. Remove revalidate and see if you even notice.

If you want to keep caching, do on-demand revalidation instead of a timer: a route handler that calls revalidatePath('/pricing'), and call it after you change a price.

A Database Webhook in Supabase (Database → Webhooks) on UPDATE of your prices table, posting to https://yourapp.com/api/revalidate. Add a secret header and check it in the route, otherwise anyone can purge your cache. Then prices update within a second and you keep the caching.

Middle ground: keep revalidate = 3600 but also call revalidatePath from the admin screen where you edit prices, if you build one later. Timer as a fallback, on-demand for the changes you know about.

Honestly for a pricing page with 3 rows, dynamic rendering is the answer. Caching is for when you have a measured problem.