{
  "manifest_version": "1",
  "slug": "atuin",
  "title": "Atuin",
  "headline": "Self-host an Atuin sync server",
  "description": "Run your own Atuin sync server on an always-on exe.dev VM, so shell history and Atuin Threads agent sessions follow you to every laptop and VM.",
  "category": "dev-tools",
  "tags": [
    "atuin",
    "atuin sync server",
    "atuin threads",
    "shell history",
    "agent sessions",
    "claude code",
    "codex",
    "self-hosted"
  ],
  "url": "https://exe.dev/deploy/atuin",
  "markdown_url": "https://exe.dev/deploy/atuin.md",
  "upstream": {
    "website": "https://atuin.sh",
    "source": "https://github.com/atuinsh/atuin",
    "docs": "https://docs.atuin.sh/latest/self-hosting/server-setup/",
    "license": "MIT"
  },
  "example_vm_name": "my-atuin",
  "time": "10 minutes",
  "stack": [
    {
      "name": "atuin-server",
      "detail": "atuin-server 18.24.8, the official binary, managed by systemd",
      "port": 8000,
      "data": "~/atuin-server"
    },
    {
      "name": "SQLite",
      "detail": "end-to-end encrypted records; the server can't read them",
      "data": "~/atuin-server/atuin.db"
    },
    {
      "name": "Nightly backup",
      "detail": "a systemd timer that keeps a week of SQLite copies",
      "data": "~/atuin-server/backups"
    }
  ],
  "access": [
    {
      "url": "https://my-atuin.exe.xyz/",
      "who": "public",
      "what": "the sync API; only your account can log in, and records arrive already encrypted"
    }
  ],
  "delivers": [
    "atuin-server 18.24.8 on port 8000 with SQLite in `~/atuin-server`, started again after a reboot",
    "Registration closed, and one account, `me`, with a random password in `~/atuin-server/password`",
    "A login to that account that succeeds through the server's API",
    "A nightly SQLite backup in `~/atuin-server/backups`"
  ],
  "owner_runs_after": [
    "ssh exe.dev share set-public my-atuin"
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe.dev/new?prompt=Set%20up%20Atuin%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe.dev%2Fdeploy%2Fatuin.md%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-atuin.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-atuin.%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-%20atuin-server%2018.24.8%20on%20port%208000%20with%20SQLite%20in%20%60~%2Fatuin-server%60%2C%20started%20again%20after%20a%20reboot%0A-%20Registration%20closed%2C%20and%20one%20account%2C%20%60me%60%2C%20with%20a%20random%20password%20in%20%60~%2Fatuin-server%2Fpassword%60%0A-%20A%20login%20to%20that%20account%20that%20succeeds%20through%20the%20server%27s%20API%0A-%20A%20nightly%20SQLite%20backup%20in%20%60~%2Fatuin-server%2Fbackups%60%0A%0ARun%20the%20VM-side%20steps%20of%20%22Set%20up%20the%20server%22%20and%20%22Back%20up%20and%20restore%22%0A%28the%20timer%20only%29%2C%20skipping%20VM%20creation.%20Install%20exactly%20the%20pinned%0Aversion.%20If%20%60~%2Fatuin-server%60%20already%20has%20a%20database%2C%20keep%20it%20and%20don%27t%0Acreate%20the%20account%20again.%20Never%20print%20the%20password%3A%20say%20where%20it%20is.%0AVerify%20with%20the%20checks%20in%20those%20sections.%20You%20can%27t%20make%20the%20VM%20public%3B%0Afinish%20by%20telling%20the%20owner%20to%20run%20%60ssh%20exe.dev%20share%20set-public%20%3Cvm%3E%60%0Aon%20their%20computer%20and%20then%20follow%20%22Connect%20your%20computer%22%20and%20%22Join%0Aevery%20new%20VM%22.%20Don%27t%20install%20the%20Atuin%20client%20on%20this%20VM.%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%20exe.dev%20share%20set-public%20my-atuin%0A",
    "terminal": "curl -fsSL https://exe.dev/deploy/atuin/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Atuin on this VM by following the exe.dev recipe at https://exe.dev/deploy/atuin.md from top to bottom.\n\nThe recipe's example VM name is my-atuin. This VM's name is the output of `hostname`: use it wherever the recipe writes my-atuin. 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- atuin-server 18.24.8 on port 8000 with SQLite in `~/atuin-server`, started again after a reboot\n- Registration closed, and one account, `me`, with a random password in `~/atuin-server/password`\n- A login to that account that succeeds through the server's API\n- A nightly SQLite backup in `~/atuin-server/backups`\n\nRun the VM-side steps of \"Set up the server\" and \"Back up and restore\"\n(the timer only), skipping VM creation. Install exactly the pinned\nversion. If `~/atuin-server` already has a database, keep it and don't\ncreate the account again. Never print the password: say where it is.\nVerify with the checks in those sections. You can't make the VM public;\nfinish by telling the owner to run `ssh exe.dev share set-public \u003cvm\u003e`\non their computer and then follow \"Connect your computer\" and \"Join\nevery new VM\". Don't install the Atuin client on this VM.\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 exe.dev share set-public my-atuin\n",
    "prompt_url": "https://exe.dev/deploy/atuin/prompt.txt"
  },
  "updated": "2026-11-13",
  "verified": "2026-11-13",
  "related": [
    "claude-code",
    "codex",
    "pi",
    "opencode",
    "hermes-agent",
    "postgres"
  ],
  "files": [
    "https://exe.dev/deploy/atuin/join.sh"
  ]
}
