Server GTM Hosting has moved to its own platform.

Visit TagLinc(opens in a new tab)
Applications

Move your site to FlyNode

Start here to move an existing app to FlyNode: pick your stack and follow the guide for Next.js, Laravel, MERN or any other app deployed from Git.

3 min readUpdated Nov 2, 2026FlyNode docs
Browse documentation

Need a hand?

Can't find your answer? Our team replies fast.

Contact support

Already have an app running somewhere else? This page is the starting point. Find your stack below, open its guide and follow the steps. Each guide covers the code, the database and the domain.

Pick your stack

Next.js

Deploy the app from Git as a Custom app and create a PostgreSQL database next to it, for Prisma or Drizzle.

Laravel

Deploy the app from Git with MySQL and Redis created next to it, then run your migrations from the terminal. Laravel 12 and Laravel 13 both work: a public GitHub project that needs Laravel 13 is built on PHP 8.4 automatically.

MERN (MongoDB, Express, React, Node)

Deploy the Node and Express server as a Custom app with a MongoDB beside it, then import your data.

Django, Rails and other stacks

There is no step-by-step guide for Django or Rails yet. Any app in a Git repository follows the same path: deploy it as a Custom app and add the database it needs. For Django and Rails that is usually PostgreSQL, and the Custom app form has a preset for it. FlyNode builds with Nixpacks, which detects most Node, Python and Go projects on its own. If it cannot work out how to start your app, set the install, build and start commands under Advanced build options.

The fast way: let Claude do it

For an app deployed from Git, you can skip the clicking. Connect Claude once with Deploy and Migrate with Claude or the CLI, then tell it what you have, for example Deploy this app to FlyNode with a PostgreSQL database. Claude builds it, adds the database and gives you a private link for your secrets.

The same steps for every stack

  1. Put the code in Git. FlyNode deploys from a GitHub repository, public or private.
  2. Deploy it and add the database. The Custom app form creates the database with the app and sets the connection variables for you.
  3. Bring the data across. Import a dump into the new database from the Database tab. Files up to 500 MB are accepted.
  4. Check it on the temporary address. Every app gets a FlyNode address, so you can test before you touch your domain.
  5. Point your domain at FlyNode. Follow Custom domains for apps and change your DNS only when you are happy with the result.

Good to know

Still stuck?

Open a support ticket from your dashboard and include the container name.

Contact support