Migrate from Northflank to Runsite

// the mental model

Every Northflank concept has a Runsite home

Northflank describes services, databases and jobs in its dashboard or a northflank.json. Each maps cleanly onto a Runsite resource.

{
  "services": [
    {
      "name": "api",
      "type": "build-from-git",
      "ports": [{ "name": "http", "port": 8080 }]
    }
  ],
  "addons": [{ "type": "postgres" }]
}

// step by step

From Northflank to live in the EU

Six steps. Most of them take seconds. Northflank keeps serving traffic until you flip your DNS.

1. 1

   Create a Runsite project

   ~30 sec

   Sign in at runsite.app and create an empty project. No credit card, no sales call.

2. 2

   Connect your Git repo

   GitHub · GitLab · Bitbucket

   Authorize GitHub, GitLab or Bitbucket. Runsite scans the selected branch for your northflank.json and detects the stack automatically.

3. 3

   Review the detected setup

   Full preview before provisioning

   Runsite lists every service, database and env var it found and how each maps onto a Runsite resource. Tweak build or start commands inline. Nothing is created yet.

4. 4

   Provision in Frankfurt

   One click · eu-central

   Create the whole stack in one step. Cross-resource env vars are wired up for you, and you get fresh database and Redis credentials in the EU.

5. 5

   Drop in your secrets

   Secrets stay out of Git

   Secret values are never read from your repo. Paste API keys and tokens once in the dashboard; they're encrypted at rest and never logged.

6. 6

   Push to go live

   Live in < 2 min

   git push and your app builds and deploys in the EU in under two minutes. Point your custom domain when ready. Northflank keeps running until you cut over.

// no surprises

What moves on its own — and what you touch

Honest about the boundaries. The supported stack is recreated in one click; a short list needs a human, and Runsite flags every item.