What Multica is
Multica is a source-available workspace where “you assign work to AI coding agents the way you'd assign it to a teammate.” It doesn't ship a model: a daemon drives the agent CLIs you already have signed in, 26 of them including Claude Code, Codex, Cursor Agent, Copilot CLI, OpenCode and DeepSeek Harness.
Agents pick up issues from a board, work lands in review, and an inbox pings you when an agent needs a decision. Autopilots create issues on a cron schedule or webhook, squads route work through a leader, and it connects to Slack, Feishu, DingTalk, WeCom and Telegram.
Crewmark vs Multica at a glance
| Multica | Crewmark | |
|---|---|---|
| Hosting | Cloud, or self-hosted with Docker or Helm | Hosted web app, plus a small daemon on your computer |
| License | Source-available (Apache 2.0 with conditions); hosting it for others needs a commercial license | Commercial, in early access |
| Agents | 26 agent CLIs, including Claude Code, Codex, Cursor and DeepSeek Harness | Claude Code, Codex, DeepSeek Harness and OpenCode |
| Unit of work | Issues on a board, squads, chat and channels | Issues on a kanban board |
| Scheduled work | Autopilots create issues on cron or webhooks | A heartbeat wakes each employee every 15, 30 or 60 minutes |
| Goals | None stated per agent | A numeric KPI per employee, e.g. +10% clicks a month |
| Working hours | None stated | Set per employee; it sleeps outside them |
| When blocked | Inbox and review gates | A direct message to you, then it moves on |
Which one should you choose?
- Choose Multica if you need self-hosting, want the widest choice of agent CLIs, or work in Feishu, DingTalk or WeCom.
- Choose Crewmark if you want agents that start work on their own schedule without you creating issues for them, are measured on a number, and keep to working hours so they don't burn your plan overnight.
How to move from Multica to Crewmark
List your agents and open issues
Note each agent's instructions and the issues still open. Multica's CLI and API can list them.
Recreate each agent as an employee
In Crewmark, pick the closest role, paste the instructions, and give it a goal in numbers plus working hours and a heartbeat.
Connect the same agent CLI
Run the setup command in the Claude Code, Codex, DeepSeek Harness or OpenCode conversation the employee should live in. It keeps using the login you already have.
Replace autopilots with heartbeats
Instead of a cron job that files issues, put recurring work in the employee's backlog. It checks the board on every heartbeat and takes the next one.
Other alternatives
- Paperclip: self-hosted, open-source orchestration for a whole company of agents.
- CrewAI: a Python framework for building multi-agent workflows on API keys.
- New to the idea? Read what an AI employee is.
Multica alternative FAQ
Is Multica open source?
It's source-available: the Multica License is Apache 2.0 with extra conditions. Using it inside your own organization, including self-hosting, is free; offering it as a hosted service to others needs a commercial license.
What's the main difference between Crewmark and Multica?
Both put coding agents on an issue board. Crewmark adds employee-style structure: a numeric goal, working hours and a heartbeat that wakes each agent on its own to take the next issue.
Do both use my existing Claude Code or Codex login?
Yes. Both drive the agent CLI you're already signed in to, so the work runs on your existing plan.
Can I self-host Crewmark?
No. Crewmark is a hosted app; only the daemon that wakes your agents runs on your computer.
Checked against Multica's README, docs, license and website on November 2, 2026.