{
  "manifest_version": "1",
  "slug": "seaweedfs",
  "title": "SeaweedFS",
  "headline": "Self-host SeaweedFS",
  "description": "Run SeaweedFS 4.54 on an exe.dev VM: an S3 API with scoped keys, the admin UI behind exe.dev login, WebDAV and FUSE, and continuous backups elsewhere.",
  "category": "databases",
  "tags": [
    "seaweedfs",
    "s3",
    "object storage",
    "s3 compatible",
    "minio alternative",
    "webdav",
    "fuse",
    "small files",
    "backups"
  ],
  "url": "https://exe.dev/deploy/seaweedfs",
  "markdown_url": "https://exe.dev/deploy/seaweedfs.md",
  "upstream": {
    "website": "https://seaweedfs.com",
    "source": "https://github.com/seaweedfs/seaweedfs",
    "docs": "https://github.com/seaweedfs/seaweedfs/wiki",
    "license": "Apache-2.0"
  },
  "example_vm_name": "my-seaweedfs",
  "time": "10 minutes",
  "stack": [
    {
      "name": "SeaweedFS 4.54",
      "detail": "`weed mini`: master, volume server, filer, S3 API, WebDAV and admin UI in one systemd service",
      "port": 8333,
      "data": "/var/lib/seaweedfs"
    },
    {
      "name": "Admin UI",
      "detail": "Buckets, users, keys and policies, behind exe.dev login and its own password",
      "port": 8000
    },
    {
      "name": "Filer, master and WebDAV",
      "detail": "The file system view of your buckets, on private ports",
      "port": 8888
    },
    {
      "name": "Keys",
      "detail": "The S3 admin key and admin UI password, mode 600",
      "data": "/etc/seaweedfs/seaweedfs.env"
    }
  ],
  "access": [
    {
      "url": "https://my-seaweedfs.exe.xyz/",
      "who": "private",
      "what": "the SeaweedFS admin UI"
    },
    {
      "url": "https://my-seaweedfs.exe.xyz:8333/",
      "who": "private",
      "what": "the S3 API, for clients that send a VM token; you can make it public"
    },
    {
      "url": "https://my-seaweedfs.exe.xyz:8888/",
      "who": "private",
      "what": "the filer UI, every bucket as folders"
    },
    {
      "url": "https://my-seaweedfs.exe.xyz:7333/",
      "who": "private",
      "what": "WebDAV, for clients that send a VM token as their password"
    }
  ],
  "delivers": [
    "SeaweedFS 4.54 running `weed mini` under systemd, with its data in /var/lib/seaweedfs, back after a reboot.",
    "An S3 API that refuses requests without a valid key, and an admin key in /etc/seaweedfs/seaweedfs.env.",
    "An `app` bucket and a key that can use only that bucket, in `~/seaweedfs/app.env`, checked with put, get, a multipart upload and a presigned URL.",
    "The admin UI at the VM's private URL, behind exe.dev login and its own password.",
    "The VM still private, with the choices for reaching S3 from elsewhere explained."
  ],
  "owner_runs_after": [
    "ssh my-seaweedfs.exe.xyz cat seaweedfs/app.env",
    "ssh my-seaweedfs.exe.xyz sudo cat /etc/seaweedfs/seaweedfs.env"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe.dev/new?prompt=Set%20up%20SeaweedFS%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe.dev%2Fdeploy%2Fseaweedfs.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-seaweedfs.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-seaweedfs.%20Skip%20the%20step%20that%20creates%20the%20VM%3B%20you%20are%20on%20it.%0A%0AYou%20are%20done%20when%20all%20of%20these%20are%20true.%20Check%20each%20one%20yourself%3A%0A-%20SeaweedFS%204.54%20running%20%60weed%20mini%60%20under%20systemd%2C%20with%20its%20data%20in%20%2Fvar%2Flib%2Fseaweedfs%2C%20back%20after%20a%20reboot.%0A-%20An%20S3%20API%20that%20refuses%20requests%20without%20a%20valid%20key%2C%20and%20an%20admin%20key%20in%20%2Fetc%2Fseaweedfs%2Fseaweedfs.env.%0A-%20An%20%60app%60%20bucket%20and%20a%20key%20that%20can%20use%20only%20that%20bucket%2C%20in%20%60~%2Fseaweedfs%2Fapp.env%60%2C%20checked%20with%20put%2C%20get%2C%20a%20multipart%20upload%20and%20a%20presigned%20URL.%0A-%20The%20admin%20UI%20at%20the%20VM%27s%20private%20URL%2C%20behind%20exe.dev%20login%20and%20its%20own%20password.%0A-%20The%20VM%20still%20private%2C%20with%20the%20choices%20for%20reaching%20S3%20from%20elsewhere%20explained.%0A%0ARead%20the%20whole%20recipe%2C%20including%20the%20closed%20details.%20For%20initial%20setup%2C%0Afollow%20%22Install%20by%20hand%22%20from%20top%20to%20bottom%3A%20the%20weed%20binary%2C%20the%20keys%0Afile%2C%20the%20systemd%20service%2C%20the%20app%20bucket%20and%20key%2C%20and%20the%20s3-check.py%0Arun.%20The%20walkthrough%20sections%20are%20for%20the%20owner%20afterwards%3A%20don%27t%20make%0Athe%20VM%20or%20the%20S3%20port%20public%2C%20create%20VM%20tokens%2C%20set%20up%20Tailscale%2C%0Abackups%2C%20mounts%2C%20or%20more%20VMs%2C%20and%20don%27t%20run%20the%20Update%20or%20Restore%0Ainstructions%20during%20initial%20setup.%20Never%20overwrite%20an%20existing%0A%2Fetc%2Fseaweedfs%2Fseaweedfs.env%20or%20~%2Fseaweedfs%2Fapp.env.%20Leave%20the%20VM%0Aprivate%20and%20do%20not%20reboot.%20Don%27t%20paste%20keys%20or%20passwords%20into%20the%20chat%3B%0Asay%20where%20they%20are.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open%20and%20these%20commands%2C%20which%20only%20I%20can%20run%2C%20from%20my%20own%20computer%20%28with%20this%20VM%27s%20name%20in%20them%29%3A%0A%20%20ssh%20my-seaweedfs.exe.xyz%20cat%20seaweedfs%2Fapp.env%0A%20%20ssh%20my-seaweedfs.exe.xyz%20sudo%20cat%20%2Fetc%2Fseaweedfs%2Fseaweedfs.env%0A",
    "terminal": "curl -fsSL https://exe.dev/deploy/seaweedfs/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up SeaweedFS on this VM by following the exe.dev recipe at https://exe.dev/deploy/seaweedfs.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-seaweedfs. This VM's name is the output of `hostname`: use it wherever the recipe writes my-seaweedfs. Skip the step that creates the VM; you are on it.\n\nYou are done when all of these are true. Check each one yourself:\n- SeaweedFS 4.54 running `weed mini` under systemd, with its data in /var/lib/seaweedfs, back after a reboot.\n- An S3 API that refuses requests without a valid key, and an admin key in /etc/seaweedfs/seaweedfs.env.\n- An `app` bucket and a key that can use only that bucket, in `~/seaweedfs/app.env`, checked with put, get, a multipart upload and a presigned URL.\n- The admin UI at the VM's private URL, behind exe.dev login and its own password.\n- The VM still private, with the choices for reaching S3 from elsewhere explained.\n\nRead the whole recipe, including the closed details. For initial setup,\nfollow \"Install by hand\" from top to bottom: the weed binary, the keys\nfile, the systemd service, the app bucket and key, and the s3-check.py\nrun. The walkthrough sections are for the owner afterwards: don't make\nthe VM or the S3 port public, create VM tokens, set up Tailscale,\nbackups, mounts, or more VMs, and don't run the Update or Restore\ninstructions during initial setup. Never overwrite an existing\n/etc/seaweedfs/seaweedfs.env or ~/seaweedfs/app.env. Leave the VM\nprivate and do not reboot. Don't paste keys or passwords into the chat;\nsay where they are.\n\nFinish with the URLs I should open and these commands, which only I can run, from my own computer (with this VM's name in them):\n  ssh my-seaweedfs.exe.xyz cat seaweedfs/app.env\n  ssh my-seaweedfs.exe.xyz sudo cat /etc/seaweedfs/seaweedfs.env\n",
    "prompt_url": "https://exe.dev/deploy/seaweedfs/prompt.txt"
  },
  "published": "2026-11-19",
  "updated": "2026-11-19",
  "verified": "2026-11-19",
  "related": [
    "s3-storage",
    "rustfs",
    "garage",
    "minio",
    "postgres",
    "sqlite"
  ],
  "alternatives": [
    "MinIO",
    "Amazon S3",
    "Cloudflare R2"
  ],
  "files": [
    "https://exe.dev/deploy/seaweedfs/exedev_token.py",
    "https://exe.dev/deploy/seaweedfs/s3-check.py"
  ]
}
