Migrate from Fleek

Fleek Hosting shut down on January 31, 2026. If you had a site on Fleek, this guide walks you through getting it back up on Pinner.

The short version

If you already have your build output and just need to get it live:

# 1. Authenticate
pinner auth
 
# 2. Launch the wizard: handles upload, website creation, and DNS in one flow
pinner websites wizard
 
# Done: your site is live on IPFS

What you had on Fleek vs. what Pinner provides

Fleek Hosting was an all-in-one platform. It combined CDN, IPFS pinning, DNS, SSL, ENS, IPNS, and CI into a single service. Pinner takes a different approach: it handles IPFS pinning, website hosting, DNS, and SSL, but each concern stays independently manageable. If Pinner ever stops serving your needs, your CIDs and your content move with you.

Quick path

The fastest way to get your site back up if you have your build output ready.

1. Install and authenticate

npm install -g @lumeweb/pinner
pinner auth

pinner auth prompts for your email and password interactively. For CI/CD, pass your API key directly: pinner auth YOUR_API_KEY.

2. Deploy with the wizard

The interactive wizard handles upload, website creation, and DNS setup in one guided flow: closest to the one-click experience you had on Fleek:

# Build your site if you haven't already
npm run build
 
# Launch the wizard
pinner websites wizard

The wizard walks you through:

1. Content source: select the directory to upload (e.g. ./dist)
2. Target type: IPFS or IPNS
3. Domain: your custom domain or a *.pinner.xyz subdomain
4. DNS mode: Pinner-managed (recommended) or self-managed
5. Validation: verifies DNS records are in place

That's it. Your site is live on IPFS.

# Upload the build output to IPFS
pinner upload ./dist

# For a subdomain (fastest: no DNS setup needed)
pinner websites create mysite.pinner.xyz --cid <CID>
 
# For a custom domain
pinner websites create mysite.example.com --cid <CID>

pinner websites ssl status mysite.example.com

Full path with CI

If you had a Fleek GitHub integration that auto-deployed on push, replace it with Pinner's GitHub Action. The workflow is similar: build, upload, deploy.

Replace your Fleek workflow

Your Fleek workflow probably looked something like this:

# Old Fleek workflow (no longer works)
- name: Deploy to Fleek
  uses: fleek-platform/action@v1
  with:
    apiKey: ${{ secrets.FLEEK_API_KEY }}
    siteId: ${{ secrets.FLEEK_SITE_ID }}

Replace it with:

- name: Deploy to Pinner
  uses: lumeweb/pinner-deploy-action@v0
  with:
    api-key: ${{ secrets.PINNER_API_KEY }}
    path: ./dist
    domain: mysite.example.com

Set the PINNER_API_KEY secret in your repository settings:

1. Go to Settings → Secrets and variables → Actions
2. Click New repository secret
3. Name: PINNER_API_KEY
4. Value: your API key from API Keys

The action uploads your build output, pins it on IPFS, and creates or updates the website record all in one step.

For IPNS publishing, automatic cleanup, and pin-by-CID mode, see the full GitHub Actions documentation.

Feature differences to know about

A few things work differently on Pinner. Being upfront about these so you're not surprised.

No public anonymous gateway

Fleek provided a public IPFS gateway. Pinner operates ipfs.pub, but it's not an anonymous, general-purpose gateway. For details on why and how to access IPFS content, see Why no public gateway.

You can also use check.ipfs.pub (Pinner's deploy of check.ipfs.network) to verify your content is available on the IPFS network.

DNS is separate from domain registration

On Fleek, you could register a domain and it was automatically configured. Pinner doesn't sell domains; you register at your preferred registrar and point DNS at Pinner's nameservers. If you already own your domain, this is a one-time setup.

ENS: use pinner point

If you had an ENS name pointing at your Fleek site, use pinner point to map the ENS name to your new CID via IPNS:

pinner point myname.eth --cid <CID>

This creates an IPNS key and publishes the CID under it. See Onchain Names for the full flow.

Your CIDs stay the same

This is important: the content identifier (CID) for your files doesn't change when you move providers. IPFS content addressing is provider-independent. If you have CIDs from Fleek, you can pin them directly on Pinner without re-uploading:

pinner pin add QmYourCIDHere

Or via the GitHub Action:

- name: Pin existing CID
  uses: lumeweb/pinner-deploy-action@v0
  with:
    api-key: ${{ secrets.PINNER_API_KEY }}
    cid: QmYourCIDHere

Self-hosting vs. Pinner

The IPFS Foundation published a modular migration guide that walks through self-hosting with Kubo + Caddy + Cloudflare DNS + GitHub Actions. That approach gives you maximum control but requires running your own IPFS node and managing infrastructure.

Pinner gives you the same modularity without the operational overhead. Your CIDs are yours, your content is portable, and you can switch providers at any time, but you don't have to maintain an IPFS Cluster or a reverse proxy. If self-hosting appeals to you, the Shipyard guide is excellent. If you'd rather focus on building your site than running infrastructure, Pinner handles the IPFS layer for you.

Migration checklist

• Install Pinner CLI (npm install -g @lumeweb/pinner)
• Authenticate (pinner auth)
• Upload your site or pin existing CIDs
• Create the website record
• Configure DNS (see DNS migration if using a custom domain)
• Verify SSL provisioning
• Replace Fleek GitHub Action with pinner-deploy-action
• Set up pinner point if you had ENS names
• Remove Fleek secrets from your repository
• Monitor your site for 24-48 hours during DNS propagation

Next steps

• DNS Migration from Fleek: detailed DNS setup and troubleshooting
• Deploy with GitHub Actions: full CI/CD setup
• Custom Domains: domain setup reference
• Migrate from Pinata: migrating SDK calls if you were also using Pinata for pinning