Multica vs Delos: Assign Issues or Give Workers Missions?
Compare Multica and Delos on shared ownership, repeatable procedures, action rules and where agents execute recurring work.
Founder, Task Machine
Multica and Delos offer different answers to a practical assignment question: should you give an agent an issue in the team's queue, or give a Worker a continuing role and missions? The deciding difference is shared ownership. Multica documents issues owned by people or agents, while Delos describes a Worker's activity without establishing the same human-owned task record.
That matters for an agency handing a client request from an agent to a consultant. You may want the consultant to take responsibility for the existing job, or you may want a persistent Worker to keep handling incoming messages within its role. Evaluate that handoff before comparing the number of connected tools.
Multica keeps handoffs on an issue
Multica's issue documentation puts status, discussion, deliverables and agent runs on one record. Assignment can name a person, agent or squad. A team can therefore use the issue as the place where execution responsibility changes.
Its project workflow guide describes steps passed to agents or people. Review can send a rejected issue back to an earlier step, which gives you a documented return path when a draft needs changes. A project lead can be a person or agent, and squad leaders route work to members.
The guide does not document general conditional branches or checks against each requirement. An issue with acceptance criteria and a reviewer is useful, but the public description does not establish that each delivered result is tested against those criteria. Keep the reviewer's expected evidence explicit when evaluating a workflow.
Delos starts with a Worker's role
Delos gives role-based Workers professional identities and communication channels. Its Worker creation guide describes missions, scheduled tasks and recurring work. A Worker can respond to an incoming email, and channel setup can give it a mailbox or phone number.
This fits a continuing client-facing role, such as handling messages within instructions you provide. Workers can hand work to each other and have human managers. A Worker's Activity tab keeps tasks, threads and history available for inspection.
Delos does not establish a lead role coordinating a goal, project or team in its published description. Its Activity documentation also does not describe a shared work item that a person and a Worker can each own. Those are specific boundaries to inspect if several consultants need to divide responsibility for the same client queue.
Distinguish written procedures from project steps
Delos's Behaviour Studio guide describes skills as written procedures placed in the Worker's context. You describe the skill in natural language and review the proposed procedure. Workers can also delegate to other Workers, but the documentation does not establish a defined multi-step process that executes identically on each run.
Multica documents project steps, a next step and a send-back step for rejection. Its workflow therefore gives a team a published handoff structure, while the Delos skill tells a Worker how to perform its role. Neither description establishes a general branch-and-verifier process for each requirement.
For a client report, inspect the actual artifact before enabling recurrence. In Multica, look for who receives the review step and where rejection returns the issue. In Delos, read the skill that the Worker receives and decide what evidence the human manager will inspect after it runs.
Check what asking for approval actually means
Delos's action rules offer Always, Ask and Never. Ask calls a confirmation tool that pauses execution. Delos explicitly describes these rules as instructions, not a code-level permission system, and says they do not automatically propagate to sub-agents.
Multica documents human workflow review steps, with notifications in its Inbox. Its public documentation does not describe per-agent action approval configuration or a collection of action approval requests in that Inbox. A handoff for review should not be treated as a published gate on every tool action.
Suppose an agent delegates a draft customer reply. With Delos, check that the delegated instructions repeat the relevant restrictions. With Multica, check whether the human review step happens before the reply is sent. The evaluation should name the action being held, not merely whether a product includes a review surface.
Test the skill and inspect the delivered work
Delos's skill evaluation campaigns grade expectations on test cases and suggest skill changes you can keep or discard. That is useful evidence when refining a procedure before repeating it. Its documentation does not describe acceptance checks on every delivered task.
Multica lets an issue contain acceptance criteria and lets workflows return rejected work. Its documentation does not establish result checking against those criteria. For either product, distinguish a procedure that performed well in a test from the evidence attached to this client's actual report.
Deployment and payment also differ. Multica's home page says internal organizational use is free, including self-hosting, with commercial licensing for external hosting or embedding and no published cloud price. Delos's pricing page advertises a free trial with up to €45 in credits and Standard from €45 per month, with Workers using shared credits. Plan credits do not roll over, purchased extra credits do not expire, and its Enterprise Workers plan offers deployment on your own infrastructure.
Multica and Delos, point by point
The following table compares the products on the same questions. Each answer carries its own source and check date so the published scope remains visible.
Both columns answer the same questions from each company's public pages. Yes means the company publishes the capability the question asks about, Partly means something narrower, No means it says it does not offer it, and Not published means its public pages do not describe it. Every answer links to its source and shows when we last checked it. The oldest check on this page was November 13, 2026.
| What you compare | Multica | Delos |
|---|---|---|
| Goals |
Multica
Partly
Projects have a shared goal and a member or agent lead. The documentation does not describe linked outcome metrics monitored by that lead. |
Delos
Partly
Give a Worker missions and ask it to build a dashboard from Tables data. Delos does not establish tracking a measurable target against a Worker's goal and reviewing or acting on it. |
| Leads |
Multica
Yes
Project leads can be people or agents, and squad leaders route issues to members. The documentation does not describe goal leads that monitor outcomes or project leads that independently review goal conflicts. |
Delos
Partly
Workers can hand work to one another, and each Worker has human managers. Delos does not establish a lead role that reviews and coordinates work across a goal, project or team. |
| Tasks |
Multica
Yes
Assign an issue to a person, agent or squad. Its discussion, deliverables, status and multiple agent runs remain on the issue. |
Delos
Partly
A Worker's Activity tab tracks its tasks, threads and history. Delos does not describe a shared task record that people and Workers can each own. |
| Recurring work |
Multica
Yes
Autopilots start from schedules or webhooks, creating an issue each time or running without one. Recurring wakeups also return an agent to an existing issue, but regular checks require an end date. |
Delos
Yes
Workers can perform recurring missions, scheduled tasks and work triggered by events such as an incoming email. Delos does not describe a stable root task with separate occurrence histories. |
| Workflows |
Multica
Yes
Project workflows hand steps to agents or people, with a next step and a send-back step for rejected work. They do not document general conditional branches or per-requirement verifier checks. |
Delos
Partly
Workers follow written skill procedures and can hand work to other Workers. Delos does not establish a defined multi-step process that runs in the same way each time. |
| Autonomy |
Multica
Partly
An Inbox collects notifications and workflows can hand a review step to a person. The documentation does not describe configuring which agent actions require approval or collecting approval requests in the Inbox. |
Delos
Partly
Set per-action rules to Always, Ask or Never. Ask calls a confirmation tool that pauses execution. Delos does not establish that approval requests are collected for you. These rules are instructions, not a code-level permission system, and do not automatically propagate to sub-agents. |
| Learned autonomy |
Multica
Not published
Multica documents agent access and workflow handoffs. Its documentation does not describe proposing changes to an agent's autonomy based on approval history. |
Delos
Not published
Workers can improve skills with you, and you set action rules. Delos does not describe recommending autonomy changes from approval and correction history. |
| Memory |
Multica
Partly
Multica retains Hermes memory per agent and can optionally enable Codex native memory. Its documentation does not describe whether users can inspect or correct that memory. |
Delos
Partly
Workers have persistent memory of interactions, preferences, templates and processes. Delos describes adding and removing Assistant memory items, but does not establish that users can inspect or correct Worker memory. |
| Planning |
Multica
Yes
Chat agents can create issues when asked, and issues can contain acceptance criteria. The documentation does not describe a required plan and acceptance-criteria review before an agent starts. |
Delos
Partly
Describe a skill in natural language and Delos drafts its procedure for review. Delos does not establish a conversational work plan that becomes tasks, steps or a reviewed plan before execution. |
| Intake |
Multica
Yes
A webhook can trigger an autopilot that creates an issue, and a squad leader can route an assigned issue to members. The documentation does not describe a project-token intake that places a proposal in the Inbox first. |
Delos
Yes
Delos filters incoming email and WhatsApp messages using the Worker's role and instructions before starting it. Rollout may be observation-only. The messages are handled by the Worker rather than routed by a team lead to task owners. |
| Connectors |
Multica
Yes
Agents can use individual or shared MCP servers, and autopilots accept webhook triggers. The documentation does not describe the same catalog of API, command-line and MCP connectors. |
Delos
Yes
Delos advertises 3,000+ tools and provides a connector catalog with an API and MCP tab. Slack, Teams, mail and other channels use webhooks to trigger Workers. |
| Models |
Multica
Partly
You can select a model and thinking level for supported agent runtimes. The documentation does not describe automatic model selection for each work stage based on price and budget. |
Delos
Yes
Delos says Workers automatically switch models for each type of task. Skill evaluation campaigns can use a selected model. Its sources do not establish that you can fix a model for all of a Worker's work. |
| Cloud or your own computer |
Multica
Yes
Connect a laptop or server to run installed coding agents, or use Multica's managed cloud sandboxes. You can also self-host the Multica service. |
Delos
Yes
Delos is a cloud platform, and its Enterprise Workers plan offers deployment on your own infrastructure. |
| Your own subscription |
Multica
Yes
Multica invokes installed AI coding tools such as Claude Code, Codex and GitHub Copilot CLI using your local sign-in or model-provider setup. Available models depend on the tool, local configuration, signed-in account and subscription entitlements. |
Delos
Not published
Delos Workers run on credit packs. Delos does not describe using your own AI subscription or model-provider API key. |
| Pricing |
Multica
Partly
Multica says internal organizational use, including self-hosting, is free, and external hosting or embedding requires a commercial license. It does not publish a cloud price on its home page. |
Delos
Yes
Delos advertises a free trial with up to €45 in credits and Standard from €45 per month. Workers draw on shared credits. Plan credits refill each cycle without rollover, purchased extra credits do not expire, and a typical task uses about 200 credits. |
| Correctness |
Multica
Partly
Issues can contain acceptance criteria, and a workflow can send rejected work back from a review step. The documentation does not establish that results are checked against defined criteria. |
Delos
Yes
Skill evaluation campaigns grade test-case expectations and propose changes for you to keep or discard. Delos does not describe acceptance checks on every delivered task. |
For software work
| What you compare | Multica | Delos |
|---|---|---|
| Code review rules |
Multica
Partly
You can assign an agent a review skill or instructions and set a workflow review step. The documentation does not establish that code is reviewed against rules. |
Delos
Partly
A GitHub Worker reviews pull requests for bugs, security and style issues. Delos does not establish review against your own repository rules. |
| Adversarial review |
Multica
Partly
A workflow can send work to a review agent and return rejected work for changes. Its documentation does not establish an independent second review of risky changes. |
Delos
Not published
Delos describes Worker pull-request reviews. It does not describe two independent reviewers performing an adversarial review of high-risk changes. |
| Risk rating |
Multica
Partly
Linked pull requests show checks and merge conflicts. The documentation does not describe rating the exact revision's merge risk. |
Delos
Not published
A Worker can review a pull request and suggest changes. Delos does not describe rating an exact revision's merge risk with rollback and detection notes. |
| Pull requests |
Multica
Partly
Agents can open pull requests, and linked issues show their state, checks and conflicts. The documentation does not establish that agents work on pull requests with review feedback. |
Delos
Partly
A Worker can review pull requests, fix bugs, add tests and open a pull request for the team to merge. Delos does not establish that Workers address review feedback on their pull requests. |
A fact we cannot find or cannot check is left out, and prices can change after the date shown. Task Machine publishes this comparison and is an interested party. Multica and Delos are named only to identify them, and there is no relationship between the companies. Has something changed? Tell us.
Who each one suits
Pick Multica if the shared issue queue is central to your team and you want review handoffs between humans and agents. Its workflow docs do not establish general conditional branches or per-requirement result checks.
Pick Delos if a role-based Worker receiving missions through its own communication channels matches your work. Its action rules are instructional, do not automatically propagate to sub-agents, and should be evaluated with that boundary in mind.
Where Task Machine fits
Task Machine makes each job a person-owned or agent-owned Task and places human questions, approvals and verifier checks in explicit Workflows. Its review documentation describes checking acceptance requirements before a person reviews the result. That addresses the difference between testing a reusable procedure and judging an individual delivery.
Task Machine is the wrong pick if you need Delos's phone identities, because its docs do not describe built-in phone identities for each agent. See Switch from Delos to Task Machine. The Multica comparison and Delos comparison set out the corresponding workflow choices. Take one client-report procedure and identify its owner, send-back path and delivery check against those pages.