Deployment

Four ways to get your Devaiy project out of the workspace and into the world. Pick based on where you want it to run and how much control you want.

Decision matrix

• I just want my code — I’ll handle hosting. → Download ZIP.
• I want my code in my own GitHub repo. → Export to GitHub.
• I want a live URL fast. → Deploy to Vercel (recommended) or Railway. Either works well since your backend lives in Supabase.

Devaiy doesn’t lock you in — using one method doesn’t prevent you from using another later. Many users start with Vercel for an MVP, then export to GitHub when they want their own CI/CD.

Download ZIP

From your project page, click Export → Download ZIP. You get a .zip file containing the full project (all source files, package.json,tsconfig.json, etc.). Unzip it locally, run npm installand npm run dev, and you have the project running on your machine.

• Best for: taking the code somewhere Devaiy doesn’t deploy to (your own server, Cloudflare Pages, AWS, etc.)
• No third-party account needed.
• What’s NOT included: Supabase secrets (those live in your Supabase Vault). You’ll need to provide your own .env if you want to run locally with full functionality.

Export to GitHub

From Export → GitHub, connect your GitHub account once (OAuth). Then for each project you can push to a new repo or update an existing one.

1. Click Export → GitHub.
2. First time: authorize Devaiy to access your GitHub. We ask for repo write permission only.
3. Choose a repo name and visibility (public or private). Click Create & Push.
4. Devaiy creates the repo and pushes the full project as the initial commit. From there it’s a normal Git repo — you can clone it, add collaborators, set up CI, etc.

Best for: using your own CI/CD, version control workflow, collaborating with others, or just having a backup outside Devaiy.

Deploy to Vercel

From Export → Vercel, connect your Vercel account once (OAuth). Then deploy with one click.

1. Click Export → Vercel.
2. First time: authorize Devaiy with Vercel.
3. Pick a project name (becomes the subdomain: your-name.vercel.app).
4. Devaiy uploads the code, Vercel builds it, you get a live URL.

Devaiy injects Supabase environment variables automatically (SUPABASE_URL, SUPABASE_ANON_KEY) so your app can talk to your database in production. Other integration secrets stay in Supabase Vault — the Edge Functions read them directly, so they don’t need to be on Vercel at all.

Recommended. Since your backend lives in Supabase, your Devaiy app is essentially a frontend that talks to Supabase — exactly what Vercel is built for. Fast, reliable, and the path most Devaiy users take.

Deploy to Railway

Same one-click flow as Vercel, but with Railway as the host. Either works equally well for Devaiy apps — pick Railway if you already use it for other projects and want to keep everything in one place.

1. Click Export → Railway.
2. First time: authorize Devaiy with Railway.
3. Pick a project name. Devaiy uploads, Railway builds and serves.

Custom domains

Both Vercel and Railway let you attach a custom domain to your deployment. Do this in their respective dashboards after deploying. Devaiy doesn’t manage custom domains directly — we just hand the project over to them; they handle the DNS and TLS.

Re-deploying after changes

Made changes in Devaiy and want them live? Just click Export → Vercel/Railway again. Devaiy pushes the new code; the platform rebuilds and updates the deployment in place (same URL).

For GitHub-exported projects, your existing CI/CD picks up the new commit.

Environment variables

Devaiy handles the most common env vars automatically:

• Supabase URL and anon key — injected into Vercel/Railway during deploy.
• Integration API keys (Stripe, OpenAI, etc.) — stay in your Supabase Vault. Edge Functions read them at runtime. They don’t need to be in your deploy target.

If your app needs additional env vars (e.g., a feature flag), add them directly in Vercel/Railway’s dashboard. Devaiy doesn’t overwrite manual additions on re-deploy.