I wonder if the "Connect to Supabase" option surfaces the rate limits shown in the manual SMTP config. Those are pretty useful, but if the defaults are actually 3 emails per hour and 60s between emails, I'd say it's important to show them to the user upfront to avoid confusion.<p>The sliders on the pricing page are weird. It shows me $200 per month for 300k email or 650k emails. Why have all the 50k increments in between with the same price?<p>This isn't specific to the one here, but I hate the way these services are priced. I don't want a bucket of use-it-or-lose-it service. That's just opaque way of overcharging while making the customer feel like they're getting good value at the top end IMO.<p>Charge me a base rate, then per-email, and adjust the discount according to my volume.<p>> If you exceed your plan limits, you will be notified and given the option to upgrade to a higher plan. If you don’t upgrade and repeatedly exceed your plan, your account may be temporarily deactivated.<p>Why? I realize it's the way everyone does it, but it's dumb. Why should I come back and beg to use the service more? Let me put up a bond (ex: $2500) that determines my monthly rate limit (ex: 1,000,000) to prevent abuse, then stop bugging me and charge my credit card for my consumption every month.<p>I also wonder if Supabase has configurable fallback SMTP providers. I'd love to use AWS SES for volume and a managed provider like this one as a fallback.