Multiple Projects on Single Self-Hosted Supabase Instance

[iRobbie]

Can I run multiple projects on self hosted supabase on my vps, or do I have to install another one for each unique project? And also a new and unique port for each supabase stack?

[silentworks]

Yes you need a new instance per project. This is exactly how the hosted Supabase platform works. They have a new instance per project they setup, the dashboard just makes it look like they are all in the same place but they are individual servers.

[Yousef-Hegazy]

You can absolutely run multiple projects on a single self-hosted Supabase instance. For smaller or personal projects, sharing the same database and auth is perfectly fine and keeps things simple. For production or commercial projects, it is generally better to use separate Supabase instances on their own ports to ensure proper security, isolate resources, and make backups and upgrades easier to manage.

[aantti]

True, but with a clarification - that would require properly implementing multi-tenancy inside the database. I think the original question was if it's possible to have multiple databases with the self-hosted configuration, and the answer is - currently that's not what it is. At this time, a single self-hosted Docker Compose -based Supabase deployment is one database. Usually, people just set up multiple identical deployments. If it's on the same server, then yes - you'll have to figure out port separation.