Self-Hosting Supabase: Migrating to remote db and Serving Edge Functions Locally

[Pavan-Kumar-KN]

Hey,

I have built a React project using Supabase, and now I am planning to self-host the Supabase stack. For migrating my existing project, the migrations ran correctly. For reference, I followed this article:

https://www.supadex.app/blog/how-to-self-host-supabase-(without-losing-your-mind)

Note: The article does not mention that after running the supabase start command, you need to visit the following URL:

http://127.0.0.1:54323/project/default

I followed the article exactly as instructed. After that, all the containers started successfully and were running properly. However, I have some questions.

---

1) Database Migration & Moving to AWS RDS

I ran the migration files from my existing project in the project root directory using:

npx supabase migration up

All migrations were applied successfully, and the database is currently hosted locally (via Docker).

Now, I am planning to move the database to AWS RDS. How can I change the database configuration to use AWS RDS instead of the local Docker database?

---

2) Edge Functions Issue

The article does not mention anything about functions. In the project root, I ran:

npx supabase functions serve

Output:

saasuniverse@saass-MacBook-Pro saasuniverse-v2 % npx supabase functions serve
Setting up Edge Functions runtime...
v1.70.5: Pulling from supabase/edge-runtime
...
2026-02-26T08:53:58.756076901Z Serving functions on http://127.0.0.1:54321/functions/v1/<function-name>
2026-02-26T08:53:58.756127117Z  - http://127.0.0.1:54321/functions/v1/ad-ai-generate
2026-02-26T08:53:58.756132311Z  - http://127.0.0.1:54321/functions/v1/ad-brand-dna
2026-02-26T08:53:58.756135158Z  - http://127.0.0.1:54321/functions/v1/ad-campaign-import
2026-02-26T08:53:58.756137421Z  - http://127.0.0.1:54321/functions/v1/ad-campaign-launch
2026-02-26T08:53:58.756139589Z  - http://127.0.0.1:54321/functions/v1/ad-report-sync
...
Using supabase-edge-runtime-1.70.5 (compatible with Deno v2.1.4)

However, when I open the self-hosted application dashboard at:

http://127.0.0.1:54323/project/default/functions

I do not see the functions listed there.

The tables are synced correctly after running the migration command, but I am unsure how the functions should be handled in a self-hosted setup.

---

Steps to Reproduce the Issue

1. Build any React project (using Lovable or manually) with Supabase.
2. Add a simple Edge Function and one simple table with migration.
3. After setting up the project in the cloud, follow the article to run the project locally.
4. To sync the database, run the following command in the project root:

npx supabase migration up

This command takes the SQL files from the supabase/migrations folder.

At this step, I want to know how to configure the project to use a remote database (e.g., AWS RDS) instead of the local Docker database.

After that, my main doubt is: how do I properly serve and manage the project’s Edge Functions in a self-hosted environment?

[aantti]

Hi @Pavan-Kumar-KN, to address your questions above:

1. Self-hosted Supabase is described here - https://supabase.com/docs/guides/self-hosting
2. Do not use local development & CLI for "self-hosting" - when you start a development stack via npx supabase it should be used for the purposes of local development and testing only, and should never be exposed to any external traffic. The reason for that is that CLI starts Supabase with default placeholder secrets and API keys, access to the UI is not password protected, and the locally running MCP server also doesn't support authentication.
3. Regarding "I am planning to move the database to AWS RDS" - while overall it is possible to use RDS or Aurora Postgres, in practice this isn't an officially supported configuration, and it will come with a lot of limitations unless you don't use Supabase features that require pg_net and some other extensions that aren't available on RDS/Aurora. Managed Postgres databases also don't allow you to use any superuser role, this brings additional limitations. You can use an external database, but it should be a fully controlled Postgres instance.
4. Edge functions are available on self-hosted Supabase - check this how-to: https://supabase.com/docs/guides/self-hosting/self-hosted-functions
5. The management UI for functions is supported in self-hosted Supabase, but currently doesn't have code editing (it's WIP).
6. Studio/Dashboard in self-hosted Supabase may lack other management features (e.g. configuring settings via the UI, etc.)
7. Make sure to use the most recent self-hosted Supabase configuration and check the CHANGELOG periodically.
8. Support and troubleshooting for self-hosted Supabase is mostly community-driven, and on a best-effort basis. Check GitHub issues & discussions, r/Supabase, and Supabase Discord. If you'd like to see how self-hosted works for users - check Self-hosting: What's working (and what's not)? #39820.

Hope this helps

[Pavan-Kumar-KN]

Thank you @aantti