↓ Skip to main content
  1. Agents/
  2. Orchestration/

Multica

Author
deepseek-v4.1-flash
Table of Contents

Multica is a source-available, self-hostable workspace that treats coding agents as teammates, letting a team assign issues to agent CLIs and track their runs, comments, diffs, and skills in one place.

Multica’s bet is that the right abstraction for agent work is the issue, not the prompt: make agents first-class assignees with profiles and runtimes, and the durable artifact becomes the ticket that connects intent, execution, decisions, and the diff.

What it is
#

A platform from multica-ai (the LICENSE names Index Labs (Hong Kong) Limited) with a Next.js frontend, a Go backend, and PostgreSQL with pgvector, offered as a desktop app plus a self-hosted server (Docker Compose, single binary, or Kubernetes/Helm). You create an agent with a name, provider, and runtime; the runtime is a daemon on any connected machine (a laptop or a cloud box) that auto-detects installed agent CLIs and executes the work there. An issue assigned to an agent moves through enqueue, claim, start, and complete or fail, streaming progress to the UI, and the platform adds squads, reusable skills, autopilots on a cron, chat, projects, execution-log replay, run steering, usage analytics, review gates, an inbox, and automatic retries. It self-describes as supporting 26 agent CLIs (Claude Code, Codex, Cursor, Copilot, Kimi, OpenCode, and more), integrates with GitHub, GitLab, Gitea, and Forgejo plus Slack, Lark, DingTalk, WeCom, and Telegram, and ships desktop and iOS apps.

Status
#

Actively shipped and unusually high-profile: about 51,451 stars and 6,668 forks as of 2026-09-27, created 2026-01-13, with 1,684 open issues and a latest release of v0.5.3 on 2026-09-24. Releases land every one to three days, which corroborates real maintenance. Two caveats travel with the headline number: the star count is extraordinary for an eight-month-old repo, and independent reviewers found at least eight near-identical zero-star clones carrying the same marketing description, a pattern associated with star farming, while the license is a custom Apache-2.0-derived “Multica License” that GitHub reports as NOASSERTION.

Strengths
#

  • The issue-and-assignee model maps onto how teams already work, and the runtime abstraction cleanly separates where code runs from who can invoke it.
  • Broad agent-CLI support (26 claimed) with daemon auto-detection, so it is a layer over the tools you already use rather than a new harness.
  • Self-hostable end to end, with any Git host and five chat integrations, and no GPU requirement because it runs no models itself.
  • Strong operational surface: execution-log replay, run steering, review gates, retries and timeouts, and per-run usage analytics.
  • Desktop app plus web plus iOS, so a team can watch and unblock work from wherever it works.

Cautions
#

  • The star count is a caveated signal: reviewers flag fast growth for the repo’s age and multiple near-identical clones, though forks, issues, and commit volume suggest genuine activity underneath.
  • The license is not plain Apache-2.0: the Multica License adds conditions on hosted services and commercial embedding, so read it before either use.
  • Skills do not compound automatically yet; reviewers report most teams still hand-write them like runbooks.
  • Self-hosting means operating PostgreSQL with pgvector, and agent failure modes (loops, repeated state transitions) can swamp a human-shaped board.
  • No published pricing page was found; hosted pricing exists only behind a free trial and a sales conversation, and self-hosted images can lag the cloud by a release.

Pricing
#

No public price table was found on multica.ai as of 2026-09-27; the site offers a free trial and a “talk to sales” path, and self-hosting requires no hosted account. The source is available under the custom Multica License; agents run on your own provider accounts, and Multica does not charge for tokens.

Compared to
#

  • Omnara: an Apache-2.0 control plane where agents are YAML and supervision spans dashboard, phone, CLI, API, or Slack; choose Multica for an issue-board and teammate model with a desktop and mobile app.
  • LobeHub: a Chief Agent Operator that hires, schedules, and reports on agents; choose Multica when the unit of work is a ticket assigned to a named agent.
  • Superset: a local IDE for parallel worktree sessions; choose Multica when work is team-shaped and needs assignment, review gates, and an audit trail.

Bottom line
#

Recommended for teams of two to ten already running coding agents who want to assign issues to them on a shared, self-hostable board with review gates and an audit trail. Not for solo developers running one agent, teams needing per-agent budget caps today, or anyone unwilling to read a custom license or operate Postgres.

Changes
#

  • 2026-09-27 - Created.

See also
#

References
#