{
  "manifest_version": "1",
  "slug": "twenty",
  "title": "Twenty",
  "headline": "Self-host Twenty CRM",
  "description": "Self-host Twenty, the open-source Salesforce alternative, with Docker on an exe.dev VM: a private CRM, its API, AI chat with no key, and nightly backups.",
  "category": "productivity",
  "tags": [
    "crm",
    "salesforce alternative",
    "hubspot alternative",
    "open source crm",
    "twenty crm",
    "docker compose",
    "postgresql",
    "sales pipeline",
    "contacts"
  ],
  "url": "https://exe.dev/deploy/twenty",
  "markdown_url": "https://exe-staging.dev/deploy/twenty.md",
  "upstream": {
    "website": "https://twenty.com",
    "source": "https://github.com/twentyhq/twenty",
    "docs": "https://docs.twenty.com/developers/self-host/capabilities/docker-compose",
    "license": "AGPL-3.0 (some enterprise features need a paid key)"
  },
  "example_vm_name": "my-twenty",
  "time": "15 minutes",
  "stack": [
    {
      "name": "Twenty 2.60",
      "detail": "twentycrm/twenty, the web app, REST and GraphQL APIs, and a worker for sync, imports and workflows",
      "port": 8000,
      "data": "~/twenty/storage"
    },
    {
      "name": "PostgreSQL 16",
      "detail": "Every record, setting and workflow",
      "data": "~/twenty/postgres"
    },
    {
      "name": "Redis 8",
      "detail": "Job queue and cache"
    },
    {
      "name": "exe.dev LLM gateway",
      "detail": "Twenty's AI chat and agents, with no API key on the VM"
    },
    {
      "name": "Nightly backup",
      "detail": "Database, files and the encryption key from a systemd timer; keeps 14",
      "data": "~/twenty-backups"
    }
  ],
  "access": [
    {
      "url": "https://my-twenty.exe.xyz/",
      "who": "private",
      "what": "Twenty, behind exe.dev login and Twenty's own sign-in"
    },
    {
      "url": "https://my-twenty.exe.xyz/rest/",
      "who": "private",
      "what": "The REST, GraphQL and MCP APIs, for scripts with a VM token and a Twenty API key"
    }
  ],
  "delivers": [
    "Twenty 2.60 on PostgreSQL and Redis, back after a reboot.",
    "A CRM only you and the people you share the VM with can reach, with Twenty's own accounts on top.",
    "AI chat and agents through exe.dev's LLM gateway, with no API key.",
    "API access for scripts and other VMs with a VM token and a Twenty API key.",
    "Nightly backups of the database, uploaded files and encryption key, with a test restore."
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe-staging.dev/new?prompt=Set%20up%20Twenty%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe-staging.dev%2Fdeploy%2Ftwenty.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-twenty.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-twenty.%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-%20Twenty%202.60%20on%20PostgreSQL%20and%20Redis%2C%20back%20after%20a%20reboot.%0A-%20A%20CRM%20only%20you%20and%20the%20people%20you%20share%20the%20VM%20with%20can%20reach%2C%20with%20Twenty%27s%20own%20accounts%20on%20top.%0A-%20AI%20chat%20and%20agents%20through%20exe.dev%27s%20LLM%20gateway%2C%20with%20no%20API%20key.%0A-%20API%20access%20for%20scripts%20and%20other%20VMs%20with%20a%20VM%20token%20and%20a%20Twenty%20API%20key.%0A-%20Nightly%20backups%20of%20the%20database%2C%20uploaded%20files%20and%20encryption%20key%2C%20with%20a%20test%20restore.%0A%0ARead%20the%20whole%20recipe%2C%20including%20the%20closed%20details%2C%20and%20follow%20%22Install%0Aby%20hand%22%20first%2C%20skipping%20VM%20creation%20and%20SSH.%20The%20walkthrough%20before%20it%0Ais%20for%20the%20owner%20afterwards.%20Do%20not%20run%20the%20public%20webhook%2C%20Restore%20or%0AUpdate%20instructions%20during%20setup.%0AWork%20as%20exedev%20in%20~%2Ftwenty.%20Never%20overwrite%20an%20existing%20~%2Ftwenty%2F.env%3A%0Ait%20holds%20the%20encryption%20key.%20Do%20not%20create%20the%20Twenty%20workspace%20or%20any%0Aaccount%3B%20the%20first%20person%20to%20sign%20up%20becomes%20the%20admin%2C%20and%20that%20must%20be%0Athe%20owner.%20Leave%20sharing%20alone.%0AVerify%20docker.service%20is%20enabled%2C%20all%20four%20containers%20run%20with%20restart%0Aunless-stopped%2C%20localhost%3A8000%2Fhealthz%20reports%20%22status%22%3A%22ok%22%2C%20the%0Agateway%20answers%20from%20the%20server%20container%2C%20the%20backup%20timer%20is%20enabled%2C%0Aand%20the%20backup%20test%20passes.%20Do%20not%20reboot.%0AFinish%20with%20the%20URL%20https%3A%2F%2F%3Cvm%3E.exe.xyz%2F%20and%20tell%20the%20owner%20to%20open%20it%0Aright%20away%20and%20create%20the%20workspace%2C%20since%20the%20first%20sign-up%20becomes%0Athe%20admin.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe-staging.dev/deploy/twenty/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Twenty on this VM by following the exe.dev recipe at https://exe-staging.dev/deploy/twenty.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-twenty. This VM's name is the output of `hostname`: use it wherever the recipe writes my-twenty. 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- Twenty 2.60 on PostgreSQL and Redis, back after a reboot.\n- A CRM only you and the people you share the VM with can reach, with Twenty's own accounts on top.\n- AI chat and agents through exe.dev's LLM gateway, with no API key.\n- API access for scripts and other VMs with a VM token and a Twenty API key.\n- Nightly backups of the database, uploaded files and encryption key, with a test restore.\n\nRead the whole recipe, including the closed details, and follow \"Install\nby hand\" first, skipping VM creation and SSH. The walkthrough before it\nis for the owner afterwards. Do not run the public webhook, Restore or\nUpdate instructions during setup.\nWork as exedev in ~/twenty. Never overwrite an existing ~/twenty/.env:\nit holds the encryption key. Do not create the Twenty workspace or any\naccount; the first person to sign up becomes the admin, and that must be\nthe owner. Leave sharing alone.\nVerify docker.service is enabled, all four containers run with restart\nunless-stopped, localhost:8000/healthz reports \"status\":\"ok\", the\ngateway answers from the server container, the backup timer is enabled,\nand the backup test passes. Do not reboot.\nFinish with the URL https://\u003cvm\u003e.exe.xyz/ and tell the owner to open it\nright away and create the workspace, since the first sign-up becomes\nthe admin.\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe-staging.dev/deploy/twenty/prompt.txt"
  },
  "published": "2026-11-21",
  "updated": "2026-11-21",
  "verified": "2026-11-21",
  "related": [
    "chatwoot",
    "n8n-2",
    "metabase",
    "postgres",
    "s3-storage",
    "docker-compose"
  ],
  "alternatives": [
    "Salesforce",
    "HubSpot",
    "Pipedrive",
    "Attio"
  ]
}
