Docs
Edge Functions
How SupaClone handles Supabase Edge Function code, settings, and the secret values that must stay manual.
Last updated 2026-07-09
What can be cloned
When Edge Function cloning is selected, SupaClone can copy function code and supported function settings from the source project to the target project.
If a function does not exist on the target, SupaClone creates it. If it already exists, SupaClone updates it.
What is not copied
Secret values are not copied automatically.
This includes Edge Function secrets such as:
- API tokens.
- Webhook signing secrets.
- Database credentials.
- Third-party service keys.
- Provider-specific client secrets.
SupaClone compares what it can read and reports missing secret names as manual steps, but the values must be entered by you in the target project.
After cloning functions
After cloning Edge Functions:
- Add required secrets in the target project.
- Review environment-specific URLs.
- Check webhook destinations and callback URLs.
- Run a target-project smoke test.
- Confirm logs do not expose sensitive values.
Runtime differences
An Edge Function can depend on external systems that are not part of Supabase. SupaClone cannot prove that third-party APIs, DNS, webhook senders, or payment providers are configured for the target.
Treat function cloning as a code/config copy, then run integration tests before sending real traffic to the target.
Ready to run a verified clone?
Start with a fresh target project, choose exactly what to copy, and review the clone report after the run completes.
Clone your first project free