{
  "manifest_version": "1",
  "slug": "multica",
  "title": "Multica",
  "headline": "Self-host Multica",
  "description": "Run Multica, the issue board where coding agents take the tickets, on an exe.dev VM: Claude Code and Codex on the same VM, no API keys to paste.",
  "category": "ai-agents",
  "tags": [
    "multica",
    "ai agents",
    "issue tracker",
    "agent task board",
    "claude code",
    "codex",
    "linear alternative",
    "self-hosted"
  ],
  "url": "https://exe.dev/deploy/multica",
  "markdown_url": "https://exe.dev/deploy/multica.md",
  "upstream": {
    "website": "https://multica.ai",
    "source": "https://github.com/multica-ai/multica",
    "docs": "https://github.com/multica-ai/multica/blob/main/SELF_HOSTING.md",
    "license": "Multica License (source-available)"
  },
  "example_vm_name": "my-multica",
  "time": "15 minutes",
  "stack": [
    {
      "name": "Multica 0.10.0",
      "detail": "Go API and Next.js web app, the official images in Docker Compose",
      "port": 3000,
      "data": "Docker volume multica_backend_uploads"
    },
    {
      "name": "PostgreSQL 17 with pgvector",
      "detail": "pgvector/pgvector:pg17 in Docker Compose",
      "data": "Docker volume multica_pgdata"
    },
    {
      "name": "nginx",
      "detail": "Serves the web app on port 8000, sends WebSockets straight to the API, and signed-out visitors to the bridge",
      "port": 8000
    },
    {
      "name": "exe.dev bridge",
      "detail": "A small Python service that signs people in with their exe.dev login and sends Multica's email through exe.dev's email gateway",
      "port": 8090
    },
    {
      "name": "Multica daemon",
      "detail": "The agent runtime, a systemd user service that runs Claude Code and Codex on the VM",
      "data": "~/multica_workspaces"
    },
    {
      "name": "exe.dev LLM gateway",
      "detail": "Claude and GPT models for the agents, without API keys"
    }
  ],
  "access": [
    {
      "url": "https://my-multica.exe.xyz/",
      "who": "private",
      "what": "Multica, signed in with your exe.dev login"
    },
    {
      "url": "https://my-multica.exe.xyz/",
      "who": "shared",
      "what": "Teammates you share the VM with, signed in as themselves; they join a workspace when you invite them"
    },
    {
      "url": "https://my-multica.exe.xyz/api/",
      "who": "private",
      "what": "The REST API, for scripts with an exe.dev token and a Multica token"
    }
  ],
  "delivers": [
    "Multica 0.10.0 at your VM's private URL, signing you and your teammates in with your exe.dev logins, back after a reboot.",
    "The VM connected as Multica's agent runtime, with Claude Code and Codex on exe.dev's LLM gateway and no API keys on the VM.",
    "The `multica` CLI signed in on the VM, so you, Shelley, and scripts can create, assign, and close issues.",
    "Generated secrets in one private file, and a nightly backup of the database, uploads, and secrets, with a tested restore."
  ],
  "deployable": true,
  "deploy": {
    "new_vm_url": "https://exe.dev/new?prompt=Set%20up%20Multica%20on%20this%20VM%20by%20following%20the%20exe.dev%20recipe%20at%20https%3A%2F%2Fexe.dev%2Fdeploy%2Fmultica.md%3Fvia%3Ddeploy%20from%20top%20to%20bottom.%0A%0AThe%20recipe%27s%20example%20VM%20name%20is%20my-multica.%20This%20VM%27s%20name%20is%20the%20output%20of%20%60hostname%60%3A%20use%20it%20wherever%20the%20recipe%20writes%20my-multica.%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-%20Multica%200.10.0%20at%20your%20VM%27s%20private%20URL%2C%20signing%20you%20and%20your%20teammates%20in%20with%20your%20exe.dev%20logins%2C%20back%20after%20a%20reboot.%0A-%20The%20VM%20connected%20as%20Multica%27s%20agent%20runtime%2C%20with%20Claude%20Code%20and%20Codex%20on%20exe.dev%27s%20LLM%20gateway%20and%20no%20API%20keys%20on%20the%20VM.%0A-%20The%20%60multica%60%20CLI%20signed%20in%20on%20the%20VM%2C%20so%20you%2C%20Shelley%2C%20and%20scripts%20can%20create%2C%20assign%2C%20and%20close%20issues.%0A-%20Generated%20secrets%20in%20one%20private%20file%2C%20and%20a%20nightly%20backup%20of%20the%20database%2C%20uploads%2C%20and%20secrets%2C%20with%20a%20tested%20restore.%0A%0ARead%20the%20whole%20recipe%2C%20including%20the%20closed%20details.%20For%20initial%20setup%2C%0Afollow%20%22Install%20by%20hand%22%20in%20order%2C%20skipping%20VM%20creation%20and%20SSH.%20The%0Awalkthrough%20at%20the%20top%20is%20for%20the%20owner%20afterwards%3A%20don%27t%20create%20a%0Aworkspace%2C%20agents%2C%20or%20issues%20yourself.%20%22Connect%20this%20VM%20as%20the%20agent%0Aruntime%22%20signs%20in%20to%20Multica%20as%20the%20VM%20owner%20only%20to%20mint%20the%20daemon%27s%0Atoken.%0AInstall%20exactly%20the%20pinned%20versions.%20Keep%20the%20VM%20private%3A%20never%20run%0Ashare%20set-public.%20On%20an%20existing%20VM%2C%20ask%20before%20replacing%20anything%20on%0Aport%208000.%20Do%20not%20reboot%2C%20restore%2C%20or%20update.%0AVerify%3A%20%2Freadyz%20says%20ok%2C%20%60multica%20daemon%20status%60%20says%20running%2C%20the%0Amultica-daemon%20user%20service%20is%20enabled%20and%20active%2C%20Linger%3Dyes%2C%20the%0Abackup%20timer%20is%20scheduled%2C%20and%20the%20test%20backup%20holds%20multica.dump.%0ANever%20send%20a%20made-up%20X-ExeDev-Email%20header%3A%20Multica%20creates%20an%20account%0Afor%20every%20address%20the%20bridge%20signs%20in.%0AFinish%20with%20https%3A%2F%2F%3Cvm%3E.exe.xyz%2F%3A%20opening%20it%20signs%20the%20owner%20in%20with%0Atheir%20exe.dev%20login.%0A%0AFinish%20with%20the%20URLs%20I%20should%20open.%0A",
    "terminal": "curl -fsSL https://exe.dev/deploy/multica/prompt.txt | ssh exe.dev new --prompt=/dev/stdin",
    "prompt": "Set up Multica on this VM by following the exe.dev recipe at https://exe.dev/deploy/multica.md?via=deploy from top to bottom.\n\nThe recipe's example VM name is my-multica. This VM's name is the output of `hostname`: use it wherever the recipe writes my-multica. 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- Multica 0.10.0 at your VM's private URL, signing you and your teammates in with your exe.dev logins, back after a reboot.\n- The VM connected as Multica's agent runtime, with Claude Code and Codex on exe.dev's LLM gateway and no API keys on the VM.\n- The `multica` CLI signed in on the VM, so you, Shelley, and scripts can create, assign, and close issues.\n- Generated secrets in one private file, and a nightly backup of the database, uploads, and secrets, with a tested restore.\n\nRead the whole recipe, including the closed details. For initial setup,\nfollow \"Install by hand\" in order, skipping VM creation and SSH. The\nwalkthrough at the top is for the owner afterwards: don't create a\nworkspace, agents, or issues yourself. \"Connect this VM as the agent\nruntime\" signs in to Multica as the VM owner only to mint the daemon's\ntoken.\nInstall exactly the pinned versions. Keep the VM private: never run\nshare set-public. On an existing VM, ask before replacing anything on\nport 8000. Do not reboot, restore, or update.\nVerify: /readyz says ok, `multica daemon status` says running, the\nmultica-daemon user service is enabled and active, Linger=yes, the\nbackup timer is scheduled, and the test backup holds multica.dump.\nNever send a made-up X-ExeDev-Email header: Multica creates an account\nfor every address the bridge signs in.\nFinish with https://\u003cvm\u003e.exe.xyz/: opening it signs the owner in with\ntheir exe.dev login.\n\nFinish with the URLs I should open.\n",
    "prompt_url": "https://exe.dev/deploy/multica/prompt.txt"
  },
  "updated": "2026-11-17",
  "verified": "2026-11-17",
  "related": [
    "issue-tracker",
    "paperclip",
    "kanzo",
    "claude-code",
    "codex",
    "openclaw"
  ],
  "alternatives": [
    "Linear",
    "Jira"
  ],
  "files": [
    "https://exe.dev/deploy/multica/exe-bridge.py"
  ]
}
