Integrations & Ownership

• Publish: deploy selected version to the preview host.
• Custom domain: point your domain at NeoBuild hosting, verify DNS, then connect.
• Upload ZIP: import an existing React app.
• Download: export current version.
• Env vars: manage Supabase and API environment values.
• Build History: inspect preview builds, SQL apply, and edge publish.
• Token Usage: review AI usage by project.

NeoBuild uses your GitHub OAuth connection. Push writes the current IDE version to your repo. Pull imports GitHub changes into NeoBuild with merge or replace strategy.

• Use repo root for a dedicated app repository.
• Use neobuild/<projectId> or another folder in monorepos.
• Pull previews changes before updating files; Push creates a commit on the selected branch.
• Quick sync copies project files, with matching files overwritten on pull.
• Open Source control for a persistent Git working copy: load NeoBuild files, review diffs, stage files, commit, and push.
• Source control also provides branches, merge, rebase, cherry-pick, revert, history, and text conflict resolution. Apply Git files to create a new NeoBuild version; publishing stays separate.

Supabase runs in your org/project. You own billing, data, users, storage, and backups. NeoBuild connects via OAuth, configures env vars, and applies SQL only after review.

NeoBuild never silently runs AI-generated SQL. Review SQL, apply to the selected Supabase project, and repair failed scripts with targeted prompts.

Edge functions are Supabase-hosted server features: code that runs on the server rather than in the browser. Use one whenever an operation needs a secret or must not be trusted to the client — calling a paid API, receiving a payment or webhook callback, sending email, or anything a user should not be able to read or replay from the frontend.

They live under functions/ in your project and run on your own Supabase project. Ask for one in plain language and NeoBuild generates it alongside the rest of the app.

How secrets reach the function

1. The function reads its configuration at runtime with Deno.env.get().
2. .env.edge.example at the project root lists every variable the functions need, with placeholder values. Commit this file.
3. Real values go in Environment Variables, never in client env vars and never in a committed file. NeoBuild injects them at deploy.

Publishing

NeoBuild discovers the edge functions in a version, lists them with the Secret keys it detected, and publishes changed functions before preview or publish so the frontend can call current server logic. Nothing changed means nothing is published. You can also run it yourself with Publish server features. Each publish is recorded in Build History next to preview builds and SQL applies, so you can confirm what actually shipped.

Auto-fix repairs build errors silently on the current version, normally up to three attempts. If it fails, Issues appears and Fix all creates a new repair version with full error context.