SaaS Edition Mapping Reference
Project in the Marketplace edition works on the same ideas as the SaaS edition. This page lists how to read each page and section of the SaaS edition in the Marketplace edition.
- As is — the same in the Marketplace edition. Read the SaaS edition's page
- Read differently — part of it differs. Shows what differs and where to read in the Marketplace edition
- Does not apply — the Marketplace edition does not have it
Overview
| Where in the SaaS edition | Status | In the Marketplace edition |
|---|---|---|
| Project — How a project is built | Read differently | What you place on steps are registered agents that an administrator registered. No goal (instructions), guardrails, playbook or skills are attached to the agent. Claw does not appear (Agent Guide) |
| Same — The two types | Read differently | The default type is workflow. A workflow is serial only and does not divide into lanes. It cannot be started by email |
| Same — Where things are in the UI | Read differently | The editor's palette is the list of registered agents. Each workflow run has a case screen. The external API is the Marketplace edition's API |
How it works
| Where in the SaaS edition | Status | In the Marketplace edition |
|---|---|---|
| Projects and steps — Steps and review steps; Agents and steps are not one to one | Read differently | The output of the previous step does not pass to the next step automatically. Bind the outputs you want passed under “Input bindings” in the step settings (Agent Guide) |
| Same — What happens when several agents share a step | Read differently | In a workflow, there is no “Run at the same time”; agents run one at a time, in placement order. In a cycle, placements run without waiting for one another, on their own schedules or by webhook |
| Same — Playbooks and skills | Does not apply | How the agent behaves is settled by the container image and the contract |
| Same — Project memory | Does not apply | There is neither project memory nor company memory. What is handed over between steps is files (Case Guide) |
| Cycle and workflow | Read differently | A cycle's placement starts a registered agent used in chat on a schedule or by webhook. The only text the agent receives as instructions is a fixed introductory sentence and the webhook's contents (Agent Guide) |
| Who decides what | Read differently | Starting a case, editing its settings and artifacts, cancelling it, and stopping a cycle execution are for owners only. Being named as a reviewer does not let you change the case settings. There is no external API called with a person's token |
| Human review — Automatic processing at the deadline | Read differently | The deadline does not decide. Instead there is the “external wait” (Review Guide) |
| How much to delegate | Read differently | The execution rules are used to check, before starting, whether the agent supports them. The platform does not stop operations during the run (Execution Rules and Traffic Guide) |
| Records and metrics | Read differently | Cycle executions have “Run ended (completion not measured)”, which is not part of the denominator of the metrics (Record Guide) |
Quickstart
| Where in the SaaS edition | Status | In the Marketplace edition |
|---|---|---|
| Workflow | Does not apply | There are no steps for creating agents. Read the Marketplace edition's Workflow |
| Cycle | Does not apply | Read the Marketplace edition's Cycle |
Guides
| Where in the SaaS edition | Status | In the Marketplace edition |
|---|---|---|
| Design Guide — What to settle for the work, how to divide projects | As is | |
| Same — What to give an agent | Does not apply | Agent Guide |
| Same — Dividing in a workflow | Read differently | There are no lanes |
| Same — Placing agents on steps | Read differently | In a workflow, there is no “Run at the same time”; agents run one at a time, in placement order. In a cycle, placements run without waiting for one another, on their own schedules or by webhook. In a workflow, the output of the previous step does not pass to the next step automatically. Bind the outputs you want passed under “Input bindings” in the step settings (Agent Guide) |
| Same — What to do when it does not go to plan | Does not apply | There is no “Handling of results”; it follows fixed rules (Trigger Guide) |
| Same — Letting the AI draft it for you | Does not apply | |
| Same — Checking a draft and applying it | Read differently | When you place a registered agent on a step for the first time, it is saved on the spot (it does not go into the draft) |
| Execution Rules Guide | Read differently | Execution Rules and Traffic Guide |
| Review Guide — Who decides | As is | |
| Same — Waiting, or proceeding at the deadline / What happens once the deadline passes | Does not apply | Review Guide |
| Same — Destination options | Does not apply | |
| Trigger Guide — Starting a workflow, a time per step, giving the time | Read differently | From the screen, start with “Start case”. Parameters cannot be passed from the external API or time triggers (Trigger Guide) |
| Same — Running a cycle, starting it from outside | Read differently | Overlapping and late sweeps, and how webhooks are handled, differ (Trigger Guide) |
| Same — Starting by email | Does not apply | |
| Same — Stopping and resuming | Read differently | There is cancelling a case and stopping a cycle execution |
| Connection Guide | Read differently | Connectors are assigned to the contract's connection slots in the step settings. In a cycle, the tokens of the project's connectors (enabled ones) pass to the agent (Agent Guide). The external-wait webhook secret is added |
| Record Guide — Where to look, reading a single run | Read differently | Record Guide |
| Same — Revisiting it from the track record (AI improvement suggestions) | Does not apply | There is no consulting on improvements or carrying them out |
References
| Where in the SaaS edition | Status | In the Marketplace edition |
|---|---|---|
| Settings Reference | Read differently | Settings Reference |
| Run Results Reference | Read differently | The seven words for results are the same. Cycles add “Run ended (completion not measured)” (Record Guide) |
| Records Reference | Read differently | There are no records for improvement suggestions, email or lanes. “Case Config Changed” is added |
| Glossary | Read differently | Glossary |
| Roles Reference | Read differently | See the “Who decides what” row above |