To self host or not to self host
What would I gain? Asking purely because I bought a big server recently to accomodate growth of my app and thinking whether I could leverage that with supabase as well
3 Replies
checkout railway.com
or digital ocean
similar but yuo haveto use github actions for droplets
Pro:
- you have more control over your infra. you can add custom rate-limit rules and block users at proxy level before the request reaches your self-hosted supabase.
Cons:
- In self-hosted, all the config is done via env variables. For example: if you want to enable oauth or change bucket object size limit or change db password, you'll need to provide configuration via env variables.
- When using hosted version, edge functions are deployed in multiple regions. You don't have that when self-hosting. For this, you'll need to use another service like fly.io for the serverless functions to truly be edge functions
- If there are any updates, you'll need to manually test these before updating in prod.
- You'll have to setup your own backups and store those backups in a safe place.
Update I also asked this on reddit and I think I will start off by doing that with our dev database to mess around and NOT break prod