Skip to Content
Faable DeployGuides & MigrationsMigrate from Netlify

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 a platform that runs full-stack apps and backends as well as static frontends. You connect your GitHub or GitLab repository, carry over environment variables and redirects, and re-point your domain. Teams move for data hosted in the EU (GDPR), a built-in Web Application Firewall, predictable EUR pricing, and bundling with Faable Auth.

Concept mapping

NetlifyFaable DeployNotes
SiteAppOne repository → one app at https://<app>.faable.link
Continuous DeploymentGitHub connectionPush to deploy
Netlify FunctionsAlways-on serviceRun your backend as a continuous process on the port Faable provides
Environment VariablesEnvironment VariablesSet per app in the dashboard or with faable deploy secrets set
Redirects / _redirectsApp routing / framework configHandle redirects in your framework or server
Custom Domains + SSLCustom domains + SSLCNAME/ALIAS + automatic certificates
—Built-in WAFEdge rules by path, user-agent and query, included

Migration steps

  1. Connect your repository in the Faable Dashboard .
  2. Read the port Faable provides. For server-rendered or backend apps, listen on the PORT environment variable rather than a hardcoded port (see the Express guide, and What the Builder Expects for details). Static sites build and serve with their standard build command — no change needed.
  3. Copy environment variables from Netlify’s site settings — in the dashboard, or from the terminal with the CLI: faable deploy secrets set KEY=VALUE KEY2=VALUE2.
  4. Re-create redirects. Move any _redirects / netlify.toml rules into your framework’s routing or your server, since Faable serves your app directly rather than through Netlify’s edge rules.
  5. Deploy by pushing your branch or running faable deploy — Faable detects, builds, and serves with free SSL. See Get Started.
  6. Move your domain via a custom domain and let SSL provision automatically; cut over once DNS propagates.

What to plan for

  • Functions → always-on process: Netlify Functions become routes in your own backend running as a continuous process. Most full-stack frameworks port directly.
  • Edge rules: redirects, headers, and rewrites configured in Netlify move into your app or framework configuration.

Last updated on

Migrate from VercelCustom Domain