{
  "manifest_version": "1",
  "slug": "payload",
  "title": "Payload",
  "headline": "Self-host Payload CMS",
  "description": "Run Payload CMS 3 and its Next.js website template on a VM: SQLite and uploads on a persistent disk, the admin behind exe.dev login, email, backups.",
  "category": "web-apps",
  "tags": [
    "payload",
    "payload cms",
    "headless cms",
    "nextjs",
    "typescript",
    "sqlite",
    "content api",
    "cms self-hosting",
    "lexical"
  ],
  "url": "https://exe.dev/deploy/payload",
  "markdown_url": "https://exe.dev/deploy/payload.md",
  "upstream": {
    "website": "https://payloadcms.com",
    "source": "https://github.com/payloadcms/payload",
    "docs": "https://payloadcms.com/docs",
    "license": "MIT"
  },
  "example_vm_name": "my-payload",
  "time": "15 minutes",
  "stack": [
    {
      "name": "Payload 3.94",
      "detail": "the website template on Next.js 16, as payload.service (next start)",
      "port": 8000,
      "data": "~/payload (your code, in git) → a release in ~/releases"
    },
    {
      "name": "SQLite",
      "detail": "one database file; PostgreSQL if you'd rather",
      "data": "~/data/payload.db"
    },
    {
      "name": "Uploads",
      "detail": "Payload's media collection, on the VM's disk",
      "data": "~/data/media"
    },
    {
      "name": "Node.js 24 LTS",
      "detail": "NodeSource's apt package, with pnpm 11"
    },
    {
      "name": "exe.dev pieces",
      "detail": "sign-in through exe.dev, a gate for /admin, email, and AI meta descriptions"
    },
    {
      "name": "Nightly backup",
      "detail": "database, uploads, settings, and the project's git history",
      "data": "~/backups"
    }
  ],
  "access": [
    {
      "url": "https://my-payload.exe.xyz/",
      "who": "private",
      "what": "the website and the content API, until you make them public"
    },
    {
      "url": "https://my-payload.exe.xyz/admin",
      "who": "private",
      "what": "Payload's admin, only for people signed in to exe.dev, even when the site is public"
    },
    {
      "url": "https://my-payload.exe.xyz:3000/",
      "who": "private",
      "what": "the dev server, when you start it, with its own database"
    }
  ],
  "delivers": [
    "Payload 3.94 with the website template (pages, posts, media, forms, search, SEO) answering on port 8000, restarting after a reboot.",
    "Content in SQLite and uploads in ~/data, backed up every night and before every deploy.",
    "/admin and the login APIs open only to people signed in to exe.dev, who are signed in to Payload by their email.",
    "Payload's email (password resets, form notifications) sent through exe.dev, and an Auto-generate button for meta descriptions that uses the LLM gateway.",
    "~/payload as the place to change the code, a dev server on port 3000, and ~/bin/payload-deploy to migrate, build, and switch with rollback."
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe.dev/new?prompt=Set%20up%20Payload%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe.dev%2Fdeploy%2Fpayload.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-payload.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-payload.%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-%20Payload%203.94%20with%20the%20website%20template%20%28pages%2C%20posts%2C%20media%2C%20forms%2C%20search%2C%20SEO%29%20answering%20on%20port%208000%2C%20restarting%20after%20a%20reboot.%0A-%20Content%20in%20SQLite%20and%20uploads%20in%20~%2Fdata%2C%20backed%20up%20every%20night%20and%20before%20every%20deploy.%0A-%20%2Fadmin%20and%20the%20login%20APIs%20open%20only%20to%20people%20signed%20in%20to%20exe.dev%2C%20who%20are%20signed%20in%20to%20Payload%20by%20their%20email.%0A-%20Payload%27s%20email%20%28password%20resets%2C%20form%20notifications%29%20sent%20through%20exe.dev%2C%20and%20an%20Auto-generate%20button%20for%20meta%20descriptions%20that%20uses%20the%20LLM%20gateway.%0A-%20~%2Fpayload%20as%20the%20place%20to%20change%20the%20code%2C%20a%20dev%20server%20on%20port%203000%2C%20and%20~%2Fbin%2Fpayload-deploy%20to%20migrate%2C%20build%2C%20and%20switch%20with%20rollback.%0A%0ARead%20the%20whole%20recipe%2C%20including%20the%20closed%20details.%20For%20initial%20setup%2C%0Afollow%20%22Set%20up%20by%20hand%22%20from%20%22Install%20Node.js%22%20to%20the%20end%20of%20it%2C%20as%0Aexedev%3B%20the%20walkthrough%20sections%20are%20for%20the%20owner%20afterwards.%20Use%20the%0Aexact%20versions%20given.%20Never%20overwrite%20an%20existing%20~%2Fpayload.env%20or%0A~%2Fpayload%2F.env.%20Don%27t%20create%20Payload%20users%2C%20don%27t%20press%20or%20call%20%22Seed%0Ayour%20database%22%2C%20don%27t%20make%20the%20VM%20public%2C%20and%20don%27t%20run%20Restore%20or%0AUpdate.%20Do%20not%20reboot.%20If%20a%20build%20fails%2C%20read%20its%20output%20and%20fix%20what%0Ayou%20can%3B%20never%20commit%20secrets.%20Finish%20with%0Ahttps%3A%2F%2F%3Cvm%3E.exe.xyz%2Fadmin%20and%20ask%20the%20owner%20to%20open%20it%20and%20create%20the%0Afirst%20user%20with%20the%20email%20of%20their%20exe.dev%20account.%20Don%27t%20paste%0Asecrets%20into%20the%20chat%3B%20say%20they%20are%20in%20~%2Fpayload.env.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe.dev/deploy/payload/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Payload on this VM by following the exe.dev recipe at https://exe.dev/deploy/payload.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-payload. This VM's name is the output of `hostname`: use it wherever the recipe writes my-payload. 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- Payload 3.94 with the website template (pages, posts, media, forms, search, SEO) answering on port 8000, restarting after a reboot.\n- Content in SQLite and uploads in ~/data, backed up every night and before every deploy.\n- /admin and the login APIs open only to people signed in to exe.dev, who are signed in to Payload by their email.\n- Payload's email (password resets, form notifications) sent through exe.dev, and an Auto-generate button for meta descriptions that uses the LLM gateway.\n- ~/payload as the place to change the code, a dev server on port 3000, and ~/bin/payload-deploy to migrate, build, and switch with rollback.\n\nRead the whole recipe, including the closed details. For initial setup,\nfollow \"Set up by hand\" from \"Install Node.js\" to the end of it, as\nexedev; the walkthrough sections are for the owner afterwards. Use the\nexact versions given. Never overwrite an existing ~/payload.env or\n~/payload/.env. Don't create Payload users, don't press or call \"Seed\nyour database\", don't make the VM public, and don't run Restore or\nUpdate. Do not reboot. If a build fails, read its output and fix what\nyou can; never commit secrets. Finish with\nhttps://\u003cvm\u003e.exe.xyz/admin and ask the owner to open it and create the\nfirst user with the email of their exe.dev account. Don't paste\nsecrets into the chat; say they are in ~/payload.env.\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe.dev/deploy/payload/prompt.txt"
  },
  "updated": "2026-11-18",
  "verified": "2026-11-18",
  "related": [
    "nextjs",
    "sqlite",
    "postgres",
    "wordpress",
    "dev-test-prod",
    "strapi"
  ],
  "alternatives": [
    "Contentful",
    "Sanity",
    "Strapi Cloud",
    "Vercel"
  ],
  "files": [
    "https://exe.dev/deploy/payload/exedev-ai.ts",
    "https://exe.dev/deploy/payload/exedev-auth.ts",
    "https://exe.dev/deploy/payload/exedev-email.ts",
    "https://exe.dev/deploy/payload/payload-backup",
    "https://exe.dev/deploy/payload/payload-deploy",
    "https://exe.dev/deploy/payload/proxy.ts"
  ]
}
