Skip to main content

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

Pages with the same names as in the SaaS edition (How It Works, the Design Guide, the Connection Guide, and the references for results, records, and roles, among others) also exist in the Marketplace edition. Read the Marketplace edition's page first, and use this list to check how it differs from the SaaS edition.

Overview​

Where in the SaaS editionStatusIn the Marketplace edition
Project — How a project is builtRead differentlyWhat 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 typesRead differentlyThe default type is workflow. There are no parallel lanes; the only lanes are those of a Branch step. It cannot be started by email
Same — Where things are in the UIRead differentlyThe 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 editionStatusIn the Marketplace edition
Projects and steps — Steps and review steps; Agents and steps are not one to oneRead differentlyThe 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 stepRead differentlyIn 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 skillsDoes not applyHow the agent behaves is settled by the container image and the contract
Same — Project memoryDoes not applyThere is neither project memory nor company memory. What is handed over between steps is files (Case Guide)
Cycle and workflowRead differentlyA 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 whatRead differentlyStarting a case is for project participants and people with the organization operations role; cancelling a case and stopping a cycle execution are for owners, operators and people with the organization operations role (the person who started a case can also cancel it); editing a case's settings and artifacts is for owners only. Being named as a reviewer does not let you change the case settings. When you call the external API with the token of a user who signed in from an external tool, operations can be called as your role in the project and the organization operations role allow (Who can call)
Human review — Automatic processing at the deadlineRead differentlyThe deadline does not decide. Instead there is the “external wait” (Review Guide)
How much to delegateRead differentlyThe 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 metricsRead differentlyCycle executions have “Run ended (completion not measured)”, which is not part of the denominator of the metrics (Record Guide)

Quickstart​

Where in the SaaS editionStatusIn the Marketplace edition
WorkflowDoes not applyThere are no steps for creating agents. Read the Marketplace edition's Workflow
CycleDoes not applyRead the Marketplace edition's Cycle

Guides​

Where in the SaaS editionStatusIn the Marketplace edition
Design Guide — What to settle for the workAs is
Same — Choosing the typeRead differentlyThe default type is workflow. What can be placed in a cycle is a registered agent used in conversations
Same — What to give an agentDoes not applyAgent Guide
Same — Dividing in a workflowRead differentlyThere are no parallel lanes. To divide where to go by the previous step's result, use a Branch step
Same — External automation and Branch stepsRead differentlyThere are no External automation steps. Branch steps are the same as in the SaaS edition, except that there is no “question” to check
Same — Placing agents on stepsRead differentlyIn 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 planDoes not applyThere is no “Handling of results”; it follows fixed rules (Trigger Guide)
Same — Publishing and reuseRead differentlyPlaybooks, skills and agents are not published. Projects can be published, and others can copy them with “Copy to my projects”
Same — Exporting, importing and sharing as a company templateRead differentlyWorks as is. A company template has no input files among the fields its users fill in
Same — Letting the AI draft it for youDoes not apply
Same — Checking a draft and applying itRead differentlyWhen 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). Where definition changes need approval, even the first placement becomes a version pending approval and is not used for runs until approved
Execution Rules GuideRead differentlyExecution Rules and Traffic Guide
Review Guide — Only the people you name, and their delegates, can decideAs is
Same — Waiting, or proceeding at the deadline / What happens once the deadline passesDoes not applyReview Guide
Same — What happens after the decisionRead differentlyDestination options cannot be placed on a review step
Same — Review or manual workAs is
Same — Editing the output and proceedingDoes not applyWhile a case awaits review, the owner makes the case's settings or artifacts a new version (Review Guide)
Same — Resuming a closed runDoes not applyThere is no operation to resume a case closed by rejection or failure as the same case. Start a new case (Review Guide)
Trigger Guide — Starting a workflow, a time per step, giving the timeRead differentlyFrom the screen, start with “Start case”. Parameters can be passed when starting a run through the external API, but not from time triggers or webhook triggers (Trigger Guide)
Same — Running a cycle, starting it from outsideRead differentlyOverlapping and late sweeps, and how webhooks are handled, differ (Trigger Guide)
Same — Starting by emailDoes not apply
Same — Stopping and resumingRead differentlyThere is cancelling a case and stopping a cycle execution
Same — The number that can run at onceRead differentlyWhat is counted is the total of running cases and cases awaiting review, up to 3 (Trigger Guide)
Connection GuideRead differently (Marketplace Connection Guide)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. The result notice for a cycle is sent only for executions in which the agent reported completion (report_completion), not for “Run ended (completion not measured)”
Record Guide — Where to look, reading a single runRead differentlyRecord Guide
Same — Clearing what needs a personRead differentlyThere are eight kinds, with “Waiting on external” added. Review requests for cases cannot be approved, rejected, or sent back in bulk. There is no “Rerun sweep”. Deadlines and stalls work the same in workflows (Record Guide)
Same — What was produced (registering in the library, chatting with this result)Does not applyThere is no operation to register a run record's artifacts in the library, and no “Chat with this result”
Same — Revisiting it from the track record (AI improvement suggestions)Does not applyThere is no consulting on improvements or carrying them out

References​

Where in the SaaS editionStatusIn the Marketplace edition
Settings ReferenceRead differentlySettings Reference
Run Results ReferenceRead differentlyThe seven words for results are the same. Cycles add “Run ended (completion not measured)” (Record Guide)
Records ReferenceRead differentlyThere are no records for improvement suggestions, email or the joining of lanes. “Case Config Changed” is added
GlossaryRead differentlyGlossary
Roles ReferenceRead differentlySee the “Who decides what” row above