Migrate from Fleek

Legacy guide - retired af CLI

This page was written for the retired af CLI and the sites/storage workflow. The current CLI is acc (compute services), which does not include these commands yet. Commands on this page will not work with acc. Kept for reference while this functionality is rebuilt.

Fleek has pivoted away from Web3 hosting to focus on AI inference. If you have sites, storage, or deployments on Fleek, this guide walks you through migrating everything to Alternate Futures.

Time to complete: 15-30 minutes per site

What Changes

Feature	Fleek	Alternate Futures
CLI command	`fleek`	`af`
Package name	`@fleekxyz/cli`	`@alternatefutures/cli`
SDK package	`@fleekxyz/sdk`	`@alternatefutures/sdk`
Config file	`fleek.json`	`af.config.json`
Token env var	`FLEEK_TOKEN`	`AF_TOKEN`
Project env var	`FLEEK_PROJECT_ID`	`AF_PROJECT_ID`
IPFS support	Yes	Yes
Arweave support	Limited	Full
Filecoin support	No	Yes
AI agents	No	Yes (Eliza, ComfyUI, custom)
Observability	No	Yes (OpenTelemetry)

Before You Start

Export your Fleek data before Fleek's service fully shuts down:
- Download your deployed site files
- Note your IPFS CIDs for any pinned content
- Export your domain configuration
- Save any environment variables
Create an Alternate Futures account at clouds.alternatefutures.ai

Install the Alternate Futures CLI:

npm install -g @alternatefutures/cli
af login

Step 1: Migrate Your Site

From Fleek CLI to AF CLI

If you were deploying with the Fleek CLI, the process is very similar with Alternate Futures.

Old (Fleek):

fleek sites init
fleek sites deploy

New (Alternate Futures):

af sites init
af sites deploy

The af sites init command creates an af.config.json file. If you had a fleek.json, here is how the configuration maps:

Fleek config (fleek.json):

{
  "id": "site-id",
  "name": "my-site",
  "distDir": "./dist",
  "buildCommand": "npm run build"
}

Alternate Futures config (af.config.json):

{
  "sites": [
    {
      "slug": "my-site",
      "distDir": "./dist",
      "buildCommand": "npm run build"
    }
  ]
}

From Fleek SDK to AF SDK

Old (Fleek):

import { FleekSdk, PersonalAccessTokenService } from '@fleekxyz/sdk/node';

const fleek = new FleekSdk({
  accessTokenService: new PersonalAccessTokenService({
    personalAccessToken: process.env.FLEEK_TOKEN,
    projectId: process.env.FLEEK_PROJECT_ID,
  }),
});

const result = await fleek.ipfs().add('./dist');

New (Alternate Futures):

import { AlternateFuturesSdk, PersonalAccessTokenService } from '@alternatefutures/sdk/node';

const af = new AlternateFuturesSdk({
  accessTokenService: new PersonalAccessTokenService({
    personalAccessToken: process.env.AF_TOKEN,
    projectId: process.env.AF_PROJECT_ID,
  }),
});

const result = await af.ipfs().add('./dist');

The SDK API is largely compatible. The main changes are the import path and environment variable names.

Step 2: Migrate IPFS Content

If you have content pinned on Fleek's IPFS infrastructure, you should re-pin it on Alternate Futures before Fleek's pinning service goes offline.

# If you have the original files, re-upload them
af storage add ./my-files

# Or upload from a directory
af ipfs add ./my-content

Your CIDs will remain the same since IPFS content-addressing is deterministic -- the same files always produce the same CID.

Step 3: Migrate Custom Domains

Export Your DNS Configuration

Before making changes, note your current DNS records:

# Check current DNS records
dig yourdomain.com A
dig yourdomain.com CNAME
dig yourdomain.com TXT

Configure Domains on Alternate Futures

# Add your domain to your AF site
af domains create --siteSlug my-site --hostname yourdomain.com

# Verify DNS configuration
af domains verify --hostname yourdomain.com

Update DNS Records

Update your DNS records at your registrar to point to Alternate Futures:

For subdomains (e.g., www.example.com):

Type: CNAME
Name: www
Value: cname.alternatefutures.ai
TTL: 3600

For root domains (e.g., example.com):

Type: A
Name: @
Value: [Platform IP from af domains detail]
TTL: 3600

See the Custom Domains guide for full details.

Step 4: Migrate CI/CD

GitHub Actions

Old (Fleek):

- name: Deploy to Fleek
  run: npx @fleekxyz/cli sites deploy
  env:
    FLEEK_TOKEN: ${{ secrets.FLEEK_TOKEN }}

New (Alternate Futures):

- name: Deploy to Alternate Futures
  run: npx @alternatefutures/cli sites deploy
  env:
    AF_TOKEN: ${{ secrets.AF_TOKEN }}
    AF_PROJECT_ID: ${{ secrets.AF_PROJECT_ID }}

Update Repository Secrets

Go to your repository Settings > Secrets and variables > Actions
Remove FLEEK_TOKEN and FLEEK_PROJECT_ID
Add AF_TOKEN with your Alternate Futures personal access token
Add AF_PROJECT_ID with your project ID

Step 5: Migrate ENS Domains

If you had ENS domains linked through Fleek:

# Link your ENS domain to your AF site
af ens create --domain mysite.eth --siteSlug my-site

# Verify the configuration
af ens verify --domain mysite.eth