Migrate from Vercel to Faable Deploy
Short answer: Migrating from Vercel to Faable Deploy keeps the part you like — push to Git, get a live deploy with automatic SSL — while moving your app from Vercel’s frontend-first serverless model to a platform that runs any stack as an always-on service (frontend and backend). You connect your GitHub repository, move your environment variables, and re-point your custom domain. Teams move for European data sovereignty (full GDPR), a built-in Web Application Firewall, predictable EUR pricing without surprise egress tiers, and bundling hosting with Faable Auth in one subscription.
Concept mapping
| Vercel | Faable Deploy | Notes |
|---|---|---|
| Project | App | One repository → one app at https://<app>.faable.link |
| Git integration | GitHub connection | Push to deploy, same workflow |
| Serverless / Edge Functions | Always-on service | Your server process runs continuously, listening on the port Faable gives it |
| Environment Variables | Environment Variables | Set per app in the dashboard or with faable deploy secrets set |
| Custom Domains | Custom domains | CNAME/ALIAS + automatic SSL |
| Vercel WAF / Firewall (add-on) | Built-in WAF | OWASP CRS, included |
| Analytics / Observability | Logs & monitoring | Logs in the dashboard |
Migration steps
- Connect your repository. Sign in to the Faable Dashboard and link the GitHub repo you deploy on Vercel today.
- Make sure your app reads the port Faable provides. Your server should bind to the
PORTenvironment variable rather than a hardcoded port (see the Express guide for the one-line pattern, and What the Builder Expects for the details). Static frontends and most frameworks work with their standardstartcommand — no change needed. - Copy environment variables from your Vercel project settings into the Faable app — in the dashboard, or from the terminal with the CLI:
faable deploy secrets set KEY=VALUE KEY2=VALUE2. - Deploy. Push to your branch (or run
faable deploy); Faable detects the stack, builds, and serves it with free SSL. See Get Started and What is zero-config CI/CD?. - Move your domain. Add your custom domain in Faable, update the DNS record, and let SSL provision automatically. Keep the Vercel deployment live until DNS propagates.
- Cut over and decommission the Vercel project once traffic is flowing through Faable.
What to plan for
- Serverless → long-running process: if you relied on per-request serverless functions, your backend now runs as a continuous, always-on process. Most frameworks (Next.js, Express, Nuxt, SvelteKit) run unchanged; purely edge-runtime code may need adjusting.
- Build settings: install/build/start commands carry over; set them on the app if your framework isn’t auto-detected.
Related
Last updated on