{
  "manifest_version": "1",
  "slug": "vaultwarden",
  "title": "Vaultwarden",
  "headline": "Self-host Vaultwarden",
  "description": "Run Vaultwarden, the Bitwarden-compatible password manager, on an exe.dev VM: Bitwarden apps, a private admin panel, team sharing, and nightly backups.",
  "category": "security",
  "tags": [
    "password manager",
    "bitwarden",
    "bitwarden alternative",
    "vaultwarden",
    "docker compose",
    "sqlite",
    "1password alternative"
  ],
  "url": "https://exe.dev/deploy/vaultwarden",
  "markdown_url": "https://exe.dev/deploy/vaultwarden.md",
  "upstream": {
    "website": "https://github.com/dani-garcia/vaultwarden",
    "source": "https://github.com/dani-garcia/vaultwarden",
    "docs": "https://github.com/dani-garcia/vaultwarden/wiki",
    "license": "AGPL-3.0"
  },
  "example_vm_name": "my-vaultwarden",
  "time": "15 minutes",
  "stack": [
    {
      "name": "Vaultwarden 1.37",
      "detail": "The official vaultwarden/server image in Docker Compose, with SQLite and the web vault",
      "port": 8080,
      "data": "~/vaultwarden/data"
    },
    {
      "name": "nginx",
      "detail": "The public front door; passes the vault and live sync, refuses /admin",
      "port": 8000
    },
    {
      "name": "Nightly backup",
      "detail": "A systemd timer; a consistent copy of the database, attachments and keys, kept two weeks",
      "data": "~/vaultwarden/backups"
    }
  ],
  "access": [
    {
      "url": "https://my-vaultwarden.exe.xyz/",
      "who": "public",
      "what": "The vault, for Bitwarden apps and the web vault, once you choose to open it"
    },
    {
      "url": "https://my-vaultwarden.exe.xyz:8080/admin",
      "who": "private",
      "what": "The admin panel, behind exe.dev login and the admin password"
    }
  ],
  "delivers": [
    "Vaultwarden running with signups closed, ready for you to invite yourself.",
    "The admin panel on a private port behind exe.dev login, with an Argon2-hashed admin password.",
    "A public front door for Bitwarden apps that refuses /admin and keeps live sync working.",
    "Nightly backups of the database, attachments and keys, with one checked in a scratch copy.",
    "Everything starts again after a reboot."
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe.dev/new?prompt=Set%20up%20Vaultwarden%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe.dev%2Fdeploy%2Fvaultwarden.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-vaultwarden.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-vaultwarden.%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-%20Vaultwarden%20running%20with%20signups%20closed%2C%20ready%20for%20you%20to%20invite%20yourself.%0A-%20The%20admin%20panel%20on%20a%20private%20port%20behind%20exe.dev%20login%2C%20with%20an%20Argon2-hashed%20admin%20password.%0A-%20A%20public%20front%20door%20for%20Bitwarden%20apps%20that%20refuses%20%2Fadmin%20and%20keeps%20live%20sync%20working.%0A-%20Nightly%20backups%20of%20the%20database%2C%20attachments%20and%20keys%2C%20with%20one%20checked%20in%20a%20scratch%20copy.%0A-%20Everything%20starts%20again%20after%20a%20reboot.%0A%0ARead%20the%20whole%20recipe%2C%20including%20the%20closed%20details.%20For%20initial%20setup%2C%0Afollow%20%22Install%20by%20hand%22%20first%2C%20skipping%20VM%20creation%20and%20SSH%3A%20Docker%20and%0Aargon2%2C%20the%20admin%20password%20and%20settings%2C%20the%20Compose%20stack%2C%20nginx%2C%20the%0Abackup%20timer%2C%20and%20the%20backup%20test.%20The%20walkthrough%20at%20the%20top%20is%20for%20the%0Aowner%20afterwards.%0AWork%20as%20exedev%20in%20~%2Fvaultwarden.%20Never%20overwrite%20an%20existing%0Avaultwarden.env%20or%20admin-password.%20Don%27t%20create%20Vaultwarden%20accounts%2C%0Ainvite%20anyone%2C%20set%20up%20SMTP%20or%20Tailscale%2C%20or%20change%20DOMAIN.%20Don%27t%20run%0ARestore%20or%20Update.%20You%20can%27t%20make%20the%20VM%20public%20from%20the%20VM%3B%20leave%20that%0Ato%20the%20owner%2C%20and%20don%27t%20ask%20them%20to%20until%20you%27re%20done.%0AVerify%20docker.service%20is%20enabled%2C%20the%20container%20uses%20unless-stopped%2C%0A%2Falive%20answers%20on%20localhost%3A8000%20and%20localhost%3A8080%2C%20%2Fadmin%20returns%20404%0Aon%20localhost%3A8000%20and%20200%20on%20localhost%3A8080%2C%20the%20backup%20timer%20is%20enabled%0Aand%20the%20backup%20test%20passes.%20Do%20not%20reboot.%0ANever%20paste%20the%20admin%20password%20into%20the%20chat%3B%20say%20it%27s%20in%0A~%2Fvaultwarden%2Fadmin-password.%20Finish%20by%20pointing%20the%20owner%20to%20%22Choose%0Awho%20can%20reach%20it%22%20and%20%22Make%20your%20account%22.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe.dev/deploy/vaultwarden/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Vaultwarden on this VM by following the exe.dev recipe at https://exe.dev/deploy/vaultwarden.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-vaultwarden. This VM's name is the output of `hostname`: use it wherever the recipe writes my-vaultwarden. 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- Vaultwarden running with signups closed, ready for you to invite yourself.\n- The admin panel on a private port behind exe.dev login, with an Argon2-hashed admin password.\n- A public front door for Bitwarden apps that refuses /admin and keeps live sync working.\n- Nightly backups of the database, attachments and keys, with one checked in a scratch copy.\n- Everything starts again after a reboot.\n\nRead the whole recipe, including the closed details. For initial setup,\nfollow \"Install by hand\" first, skipping VM creation and SSH: Docker and\nargon2, the admin password and settings, the Compose stack, nginx, the\nbackup timer, and the backup test. The walkthrough at the top is for the\nowner afterwards.\nWork as exedev in ~/vaultwarden. Never overwrite an existing\nvaultwarden.env or admin-password. Don't create Vaultwarden accounts,\ninvite anyone, set up SMTP or Tailscale, or change DOMAIN. Don't run\nRestore or Update. You can't make the VM public from the VM; leave that\nto the owner, and don't ask them to until you're done.\nVerify docker.service is enabled, the container uses unless-stopped,\n/alive answers on localhost:8000 and localhost:8080, /admin returns 404\non localhost:8000 and 200 on localhost:8080, the backup timer is enabled\nand the backup test passes. Do not reboot.\nNever paste the admin password into the chat; say it's in\n~/vaultwarden/admin-password. Finish by pointing the owner to \"Choose\nwho can reach it\" and \"Make your account\".\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe.dev/deploy/vaultwarden/prompt.txt"
  },
  "updated": "2026-11-18",
  "verified": "2026-11-18",
  "related": [
    "agent-secrets",
    "uptime-kuma",
    "sqlite",
    "docker-compose",
    "codex-security",
    "open-code-review"
  ],
  "alternatives": [
    "Bitwarden",
    "1Password",
    "LastPass"
  ]
}
