Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
All instances in a plan get charged compute based on the size of the instance for the time they are running during the month. For the basic Pro plan it will be around $10, BUT you get a $10 credit for your FIRST instance in the org. So total should be $25 for basic plan. If you add another instance then that is billed for its CPU time, but not another $25 fee. So two basic instances in the same org sharing storage and egress amounts would be $35.
This is very concerning for my planned usage of Supabase because simple compute usage is not being metered correctly, and there is no way to view history of changes to my Compute add-on in the logs on the Pro tier beyond 24 hours.
Furthermore, the issue is potentially worse than I expected because it appears that the compute usage metering has "accidentally" switched to Large under the Usage page after I specifically ensured that my Compute add-on is showing Small on the web interface
If they are active you get the full processing power available whether you use it or not. These are not billed by processor run time, but by you have a "server" available to you.
@garyaustin Any insights onto this issue? Support acknowledges this problem but I'm also curious about what exactly was the bug on the backend/code that is causing this issue. I'm still waiting for further communication from Support after support email says that they need to get Billing involved