Stepwork logoStepwork logo
ProcedureDeterministic AgentsMarketplaceSecurityClaude Co-Work Alternative
Book a Demo
ProcedureDeterministic AgentsMarketplaceSecurityClaude Co-Work Alternative
Book a Demo

FAQ

Everything you need to know about Stepwork

Get clear answers about Stepwork, deterministic agents, workflow automation, security, integrations, and how teams use Stepwork to run reliable operational processes.

Answers

Common questions

Categories

  1. Understanding Stepwork
  2. LLMs and AI
  3. Building workflows
  4. Security and control
  5. Integrations and data
  6. Getting started

Understanding Stepwork and deterministic agents

  • A deterministic agent follows a fixed, recorded path instead of deciding what to do from scratch each time. The same inputs produce the same steps.
  • Traditional AI agents can choose different actions on each run. Stepwork follows a defined process, making execution more repeatable and predictable.
  • A script is written in code and can break when an interface changes. Stepwork records the process through the interface and uses AI vision to recognize updated elements while preserving the recorded path.
  • Stepwork is designed for repetitive, multi-step operational work such as onboarding, offboarding, access reviews, data extraction, and cross-application processes.

LLMs and AI decision-making

  • LLMs can help interpret information or support specific steps, while the overall process remains defined through recorded flows, rules, and procedures.
  • Stepwork does not rely on an LLM to freely choose a new path on every run. The actions are defined in advance through recorded flows and procedures.
  • AI can help recognize an element or interpret information, but the workflow follows a predefined path. This allows Stepwork to handle interface changes while maintaining control over execution.
  • When an interface changes, Stepwork's AI vision can recognize an element in its new position or with a new label, allowing the run to continue on the recorded path.
  • The run stops and records the failed step and the reason for failure. The result remains available in the run history for review.

Building and running workflows

  • You perform the task once while Stepwork records the actions. That recording becomes a reusable flow.
  • A basic flow can be recorded in minutes by performing the task once.
  • A flow is one recorded process. A procedure connects multiple flows, decision rules, API calls, and approvals into a larger workflow.
  • Yes. Variables allow you to update values such as URLs, account names, tiers, and IDs without recording the flow again.
  • Yes. Flows and procedures can run on a schedule in an isolated cloud container when nobody is online.

Security, control, and reliability

  • Workflows run in an isolated browser container, either on a machine in your environment or in a Stepwork cloud container.
  • Stepwork reads credentials from 1Password when a flow runs and stores a reference to the vault item, not the password.
  • Access is scoped by role across administrators, managers, and members within your organization.
  • Yes. Teams can choose which flows are available to users and can require named approvals before sensitive steps continue.
  • Stepwork stops the run, records the failed step and reason, and keeps the complete history. Retried attempts are also recorded.
  • Yes. Each run records its steps, values, outcome, duration, and triggering user.
  • Stepwork records the actions taken, the values read, and the final outcome of each run. If a step fails, the run stops and records the reason so the result can be reviewed.

Integrations and data

  • No. Stepwork works directly through an application's interface, including applications with no API or incomplete API coverage.
  • Yes. Stepwork can read and interact with applications through their user interface.
  • Yes. Stepwork can read values, tables, and states from an interface and pass the extracted information to another flow, rule, or API.
  • Yes. A procedure can combine interface actions and API calls within the same process.
  • Yes. Extracted values can be passed to the next flow, evaluated by a rule, or sent to an existing API.

Getting started

  • Teams can automate repetitive operational processes such as onboarding, offboarding, access reviews, data extraction, and cross-application work.
  • Teams can start by recording a basic flow in minutes and then build more advanced procedures by connecting existing flows.
  • No. Basic flows are created by performing the task once while Stepwork records it. More advanced procedures can include rules, APIs, and approvals.
  • Yes. Stepwork includes templates for common processes such as onboarding, offboarding, and access reviews.
  • Teams need to identify the process, the applications involved, the required inputs, the expected outcome, and any approvals or access requirements.

See it run on a process you already repeat

Bring one. We will show you what it looks like as a flow and what each run records.

Book a Demo
Stepwork

Deterministic agents for work that must run the same way every time.

ProcedureDeterministic AgentsMarketplaceSecurityClaude Co-Work AlternativeFAQ
Terms and ConditionsPrivacy PolicyData Processing AgreementSubprocessors

2261 Market Street #4481, San Francisco, CA 94114, USA

Loot Discount inc dba Stepwork

© 2026 Stepwork. All rights reserved.