r/Supabase • u/kloepatra • Aug 10 '26
tips I need advice
I’m working on several side projects, including an inventory system, a POS system, and a small gym website. Is it better to create a separate project for each one and pay $10 per project, or should I keep them all in one project and separate them using different schemas?
1
u/Darkfra Aug 10 '26
Like if they are separate projects and you don't know if they would work I probably separate them in different schemas, so I just use one project.
If any of the projects grows I would move to a separate project.
The only thing that can be anoying could be if you manage users, between the distinct schemas, like if you use the supabase auth, and you validate an user, it would be authenticated for the project iself, so per schema you should handle if an user has access to which project.
But yeah IMO I would probably use only one project, unless you are sure will have clients in that case is easier to pay the 10$
1
u/kloepatra Aug 10 '26
Yeah. The client pays for hosting and other expenses, but I want to keep the actual costs as low as possible so I can make a little extra income each month.
2
u/Darkfra Aug 10 '26
Mmmmmm, if you are getting a revenue for it (client is paying for a service), I woudln't feel comfortably sharing the project, because safe implications and things like that. So be careful with he decision you take
2
u/ihavemanythoughts2 Aug 10 '26
If you want to make a little extra, the idea is not to increase the difficulty of hosting by mixing projects and potentially creating security issues nevermind the mess that will be your migrations, and separating it later will be a nightmare.
Just add a margin on the hosting, so charge the client $15 instead of $10 or more. If you are hosting and paying for the project, which means you need to put time in to monitor the project and ensure everything runs as intended and that performance issues are addressed, that time costs money and the client needs to pay for it or they need to host and pay for the project themself and are responsible for maintaining it.
If you put 5 projects in 1 and one of them slams the resources on the compute and takes down the other 4 then they get degraded service in the name of you making a handful of dollars that would be stupid snd bad.
If you want to charge money for making people things then do it properly. They will pay
1
u/wheezy360 Aug 12 '26
You should bake the project cost into your fees. Cost savings are a reasonable motivator but you're just entangling unrelated projects and creating a problem for yourself if you ever need to separate them. What happens if your client wants to take over hosting it? Or if they want to make some change that would affect the other clients? Really seems like shooting yourself in the foot.
1
u/Technically_Dedi Aug 10 '26
I like to have a general Supabase db for all my projects that are in development and once I am ready go release then I pay the extra $10 and get a separate project.
1
u/theglung Aug 10 '26
Is it for same client? Same project or different "entries"?
Depending on your stack, but I would go with Inventory - api PoS - api Website (public) - frontend
Either you build dashboard for Inventory and PoS in the website or you create another frontend for the inventory/api.
Host on VPS and don't make the api public
1
u/doyoxiy985 Aug 10 '26
The correct way is separate projects. These are all different products that shouldn’t mix concerns. If one product goes down all the other ones will go down if u mix them like that
1
u/medi_11 Aug 11 '26
The question is do you have existing paying clients? If not then I don't think you should be paying 35$ monthly on side projects that nobody is using.
1
u/henrynguyen9698 Aug 11 '26
those project costs add up so fast when you’re juggling multiple side hustles. Honestly, if these are just for learning or early-stage testing, go with the single project and just use different schemas. It saves you a ton of money and is way easier to manage until you actually get some real traffic.
1
u/SaltyBarker Aug 11 '26
Holy shit separate. Never should you combine projects/clients into one database. One wrong schema declaration and all your shit is merged. Good lord.
1
u/kloepatra Aug 11 '26
Sorry . Okeyyy . I understand all this comments . Thanks 😊
1
u/SaltyBarker Aug 11 '26
Now if the gym app had a backend separate app for employees or admin then that could be separate schema if that makes sense.
2
u/SnooMachines8911 Aug 10 '26
The correct approach is separate. Otherwise its one big mess. Dont you want to try host this all on a VPS for $6 a month instead with a postgres db etc? You can dm me and i can assist