I hate to be that guy but I was curious if eventually supabase will consider a "hobbiest" tier. The free tier is great for local development of products, preparing to launch. The 25$ tier is a huge jump. It feels great for actual companies, people launching a service to profit. But lots of time, I'm not starting a company. I just want a database for some small service. I just want a few limits knocked off the free tier - No automatic shutdown (or even lengthened) - Doesn't count to 2 free project quota - Maybe a gigabyte included, but even that might be a bit much. Just the opportunity to pay for more storage, say at 0.25/gb Services that would be a good fit for this tier would be your weekend projects that you present to the public, but are probably open source and only offered as a good will. TD;LR, a tier between "local development" and "company"

Hi Wouldn't be better to have a "pay as you go" offer? Would be the perfect split between the free and paid price @Ping for toast

Here you go, and yes, that would be an amazing way to do it!

This is indeed a suggestion we got often. We planned to discuss about asap

I would be so excited! This is probably the only significant blocker for adoption in many of my projects (as well as probably the other common suggestion - offline support, but I don't need it so much as want it) I don't mind too much between pay as you go or a small subscription, although pay as you go is of course preferable. I mean, yall need to pay your bills and I need something I can afford for the small projects ❤️

Just want to chime in here with another type of usage. I have a default Pro instance for my production environment. Currently there is about 2GB of data. I have another Free instance that I'm using for my development environment and of course I can't fit a duplicate of the production data due to the 500MB limit. I'm ok with this limitation for now but if there is another tier around $5 or $10, I would happily upgrade my development instance.

I just want to add here that from a data standpoint you should not be storing your production data into your development database. Having the same table schema is fine but not the same data being shared. Also do note you can use local docker for your development work and the storage would be limited to your hard drive space.

That’s solid general advice. I should have clarified that for my web app, 99% or the storage is non user-sensitive stock market data that would be helpful to have for both instances and it’s only those tables that I would like to duplicate. The term

development

was also misleading, I have a

dev.*

domain prefix where I can let beta testers try out new features before production deployment, so it’s not just for local development. Even for this one I have actually set up a self hosting instance that runs fine on a small Linode instance. It was just a lot of hassle to setup and I would pay a fair amount to avoid that.

The term you're looking for in that case is "staging"

I guess also another topic is localization pricing also...

Hi guys Please have a look here: https://github.com/supabase/supabase/discussions/8243 cc @n10000k @e0 @Ping for toast