{
  "manifest_version": "1",
  "slug": "garage",
  "title": "Garage",
  "headline": "Self-host Garage S3 storage",
  "description": "Run Garage on an exe.dev VM: an S3-compatible API for your apps, static websites from buckets, private by default, and backups to a second place.",
  "category": "databases",
  "tags": [
    "garage",
    "s3",
    "object storage",
    "s3 compatible",
    "static website hosting",
    "minio alternative",
    "rclone"
  ],
  "url": "https://exe.dev/deploy/garage",
  "markdown_url": "https://exe.dev/deploy/garage.md",
  "upstream": {
    "website": "https://garagehq.deuxfleurs.fr",
    "source": "https://git.deuxfleurs.fr/Deuxfleurs/garage",
    "docs": "https://garagehq.deuxfleurs.fr/documentation/quick-start/",
    "license": "AGPL-3.0"
  },
  "example_vm_name": "my-garage",
  "time": "15 minutes",
  "stack": [
    {
      "name": "Garage 2.5",
      "detail": "One static binary run by systemd; metadata in SQLite",
      "port": 3900,
      "data": "/var/lib/garage"
    },
    {
      "name": "nginx",
      "detail": "Sends signed S3 requests to the API and everything else to bucket websites",
      "port": 8000
    }
  ],
  "access": [
    {
      "url": "https://my-garage.exe.xyz/",
      "who": "private",
      "what": "the S3 API and bucket websites; public only if you choose"
    }
  ],
  "delivers": [
    "Garage 2.5 started at boot, keeping its metadata in SQLite with every write flushed to disk and a snapshot every 6 hours.",
    "A bucket called `app-data` and a key that can use it, with the settings in `~/garage/app.env`.",
    "One URL, `https://my-garage.exe.xyz/`, for S3 clients and bucket websites, private until you share it.",
    "The admin API on localhost only, for the `garage` command and a web UI on another VM.",
    "`garage-backup`, which copies a metadata snapshot and the data to a second place."
  ],
  "owner_runs_after": [
    "ssh my-garage.exe.xyz cat garage/app.env",
    "ssh exe.dev ssh-key generate-api-key --vm=my-garage --label=s3 --exp=90d"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe.dev/new?prompt=Set%20up%20Garage%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe.dev%2Fdeploy%2Fgarage.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-garage.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-garage.%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-%20Garage%202.5%20started%20at%20boot%2C%20keeping%20its%20metadata%20in%20SQLite%20with%20every%20write%20flushed%20to%20disk%20and%20a%20snapshot%20every%206%20hours.%0A-%20A%20bucket%20called%20%60app-data%60%20and%20a%20key%20that%20can%20use%20it%2C%20with%20the%20settings%20in%20%60~%2Fgarage%2Fapp.env%60.%0A-%20One%20URL%2C%20%60https%3A%2F%2Fmy-garage.exe.xyz%2F%60%2C%20for%20S3%20clients%20and%20bucket%20websites%2C%20private%20until%20you%20share%20it.%0A-%20The%20admin%20API%20on%20localhost%20only%2C%20for%20the%20%60garage%60%20command%20and%20a%20web%20UI%20on%20another%20VM.%0A-%20%60garage-backup%60%2C%20which%20copies%20a%20metadata%20snapshot%20and%20the%20data%20to%20a%20second%20place.%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%20Garage%2C%20its%20config%2C%20the%0Aservice%2C%20the%20layout%2C%20the%20app-data%20bucket%20and%20key%2C%20the%20placeholder%0Awebsite%2C%20nginx%20on%20port%208000%2C%20and%20garage-backup.%0ADon%27t%20make%20the%20VM%20public%2C%20set%20up%20Tailscale%20or%20other%20nodes%2C%20or%20schedule%0Abackups%20%28they%20need%20a%20destination%20only%20the%20owner%20can%20choose%29.%20Never%0Aoverwrite%20an%20existing%20%2Fetc%2Fgarage.toml%20or%20~%2Fgarage%2Fapp.env.%20Check%20that%0A%60aws%20s3%20ls%20s3%3A%2F%2Fapp-data%60%20works%20with%20~%2Fgarage%2Fapp.env%2C%20that%0Ahttp%3A%2F%2Flocalhost%3A8000%2F%20shows%20the%20placeholder%20page.%20Don%27t%20paste%20keys%20or%20tokens%20into%20the%0Achat%3B%20say%20they%20are%20in%20~%2Fgarage%2Fapp.env%20and%20%2Fetc%2Fgarage.toml.%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-garage.exe.xyz%20cat%20garage%2Fapp.env%0A%20%20ssh%20exe.dev%20ssh-key%20generate-api-key%20--vm%3Dmy-garage%20--label%3Ds3%20--exp%3D90d%0A",
    "terminal": "curl -fsSL https://exe.dev/deploy/garage/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Garage on this VM by following the exe.dev recipe at https://exe.dev/deploy/garage.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-garage. This VM's name is the output of `hostname`: use it wherever the recipe writes my-garage. 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- Garage 2.5 started at boot, keeping its metadata in SQLite with every write flushed to disk and a snapshot every 6 hours.\n- A bucket called `app-data` and a key that can use it, with the settings in `~/garage/app.env`.\n- One URL, `https://my-garage.exe.xyz/`, for S3 clients and bucket websites, private until you share it.\n- The admin API on localhost only, for the `garage` command and a web UI on another VM.\n- `garage-backup`, which copies a metadata snapshot and the data to a second place.\n\nRead the whole recipe, including the closed details. For initial setup,\nfollow \"Install by hand\" from top to bottom: Garage, its config, the\nservice, the layout, the app-data bucket and key, the placeholder\nwebsite, nginx on port 8000, and garage-backup.\nDon't make the VM public, set up Tailscale or other nodes, or schedule\nbackups (they need a destination only the owner can choose). Never\noverwrite an existing /etc/garage.toml or ~/garage/app.env. Check that\n`aws s3 ls s3://app-data` works with ~/garage/app.env, that\nhttp://localhost:8000/ shows the placeholder page. Don't paste keys or tokens into the\nchat; say they are in ~/garage/app.env and /etc/garage.toml.\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-garage.exe.xyz cat garage/app.env\n  ssh exe.dev ssh-key generate-api-key --vm=my-garage --label=s3 --exp=90d\n",
    "prompt_url": "https://exe.dev/deploy/garage/prompt.txt"
  },
  "published": "2026-11-19",
  "updated": "2026-11-19",
  "verified": "2026-11-19",
  "related": [
    "garage-webui",
    "s3-storage",
    "minio",
    "rustfs",
    "seaweedfs",
    "postgres"
  ],
  "alternatives": [
    "Amazon S3",
    "MinIO",
    "Cloudflare R2"
  ],
  "files": [
    "https://exe.dev/deploy/garage/exedev_token.py",
    "https://exe.dev/deploy/garage/garage-backup"
  ]
}
