Feature
Server-side work that never reaches the browser
Payment webhooks, third-party API keys, email sending — the things that must not sit in frontend code run as Supabase edge functions, with secrets injected at deploy.
In short
Anything that needs a secret or must not be trusted to the browser runs as a Supabase edge function in your own project. NeoBuild finds the functions in your app, detects which secret names they need, injects the real values at deploy time, and publishes changed functions automatically before each preview or publish.
What it does
- Edge functions live under functions/ in your project and run on your own Supabase
- Secrets are read at runtime, never bundled into the frontend build
- NeoBuild detects the secret names a version needs and shows them for you to set
- Changed functions are published before preview or publish; unchanged ones are skipped
- Every publish is recorded in Build History alongside preview builds and SQL applies
- A security advisory flags secrets that would otherwise end up client-side
The difference between a demo and something you can charge for
A prompt-built app that talks to Stripe, sends email or calls a paid API needs somewhere safe to keep the key. If the only place is frontend code, the key is public the moment you publish — which is how a lot of AI-generated apps quietly leak credentials. Putting that work in edge functions on your own Supabase project, with secrets injected at deploy rather than compiled in, is what makes the difference between something you can demo and something you can take money through.
Documented in Integrations & Ownership.
FAQ
What is an edge function used for?
Work that must not happen in the browser: calling a third-party API with a secret key, receiving a payment or webhook callback, sending email, or any operation you do not want a user to be able to read or replay from the frontend.
Where are my API keys stored?
As secrets on your own Supabase project, injected at deploy. They are read by the function at runtime and are never placed in client environment variables or bundled into the frontend build.
Do I have to publish functions manually?
No. NeoBuild publishes changed edge functions before preview or publish, and skips the step entirely when there are none or nothing has changed. You can also trigger it yourself with Publish server features.
How do I know a function actually deployed?
Build History records each edge publish alongside preview builds and SQL applies. If a function returns 404 at runtime, it usually means it was never published to Supabase.
Try it on your own app
1,000,000 AI tokens free, no card. Then $1 (₹100) per million tokens — with the React source and your own Supabase database yours from the first build.
Start freeAll featuresWhat you can build