Migrate from Netlify to Faable Deploy
Short answer: Migrating from Netlify to Faable Deploy keeps the Git-driven workflow — connect a repo, push, get a live site with automatic SSL — while moving from Netlify’s static-site-plus-functions model to Linux containers that run full-stack apps and backends as well as static frontends. You connect your GitHub repository, carry over environment variables and redirects, and re-point your domain. Teams move for European data sovereignty (GDPR), a built-in Web Application Firewall, predictable EUR pricing, and bundling with Faable Auth.
Concept mapping
| Netlify | Faable Deploy | Notes |
|---|---|---|
| Site | App | One repository → one app at https://<app>.faable.link |
| Continuous Deployment | GitHub connection | Push to deploy |
| Netlify Functions | Linux container | Run your backend as a continuous process on $PORT |
| Environment Variables | Environment Variables | Set per app in the dashboard |
Redirects / _redirects | App routing / framework config | Handle redirects in your framework or server |
| Custom Domains + SSL | Custom domains + SSL | CNAME/ALIAS + automatic certificates |
| — | Built-in WAF | OWASP CRS, included |
Migration steps
- Connect your repository in the Faable Dashboard .
- Bind to
$PORT. For server-rendered or backend apps, listen on0.0.0.0and thePORTvariable (see the Express guide). Static sites build and serve with their standard build command. - Copy environment variables from Netlify’s site settings.
- Re-create redirects. Move any
_redirects/netlify.tomlrules into your framework’s routing or your server, since Faable serves your app directly rather than through Netlify’s edge rules. - Deploy by pushing your branch or running
faable deploy— Faable detects, builds, and serves with free SSL. See Get Started. - Move your domain via a custom domain and let SSL provision automatically; cut over once DNS propagates.
What to plan for
- Functions → container process: Netlify Functions become routes in your own backend running as a container. Most full-stack frameworks port directly.
- Edge rules: redirects, headers, and rewrites configured in Netlify move into your app or framework configuration.
Related
Last updated on
Last updated on