Stepwork logoStepwork logo
How it works

Procedures

  • OverviewHow a Procedure runs the whole process
  • Extractions deep diveRead tables and documents, use them anywhere
Deterministic AgentsMarketplace

By department

  • ITAccounts, access, helpdesk requests
  • Security & ComplianceAccess reviews, evidence, audits
  • Finance & AccountingInvoices, billing, month-end close
  • Sales & RevOpsCRM to ERP, orders, quotes
  • OperationsOrders, deliveries, dispatch
  • HR & PeopleOnboarding and offboarding
See every use case

By industry

  • HealthcareReferrals, eligibility checks, EHR entry
  • 3PL and warehousingPDF orders, WMS entry, client billing
  • Freight and truckingRate confirmations, carrier checks, TMS
  • Fuel and convenience storesStore staff, POS IDs, back office
  • ConstructionJob setup, subcontractor insurance
  • Manufacturing and distributionPO entry, supplier dates, legacy ERPs
  • Accounting firmsMonth-end across every client file
  • Field services and tradesService calls to jobs to invoices
  • MSPsNew users and license true-ups
See every industry
Security
Log inBook a Demo
How it works

Procedures

  • OverviewHow a Procedure runs the whole process
  • Extractions deep diveRead tables and documents, use them anywhere
Deterministic AgentsMarketplace

By department

  • ITAccounts, access, helpdesk requests
  • Security & ComplianceAccess reviews, evidence, audits
  • Finance & AccountingInvoices, billing, month-end close
  • Sales & RevOpsCRM to ERP, orders, quotes
  • OperationsOrders, deliveries, dispatch
  • HR & PeopleOnboarding and offboarding
See every use case

By industry

  • HealthcareReferrals, eligibility checks, EHR entry
  • 3PL and warehousingPDF orders, WMS entry, client billing
  • Freight and truckingRate confirmations, carrier checks, TMS
  • Fuel and convenience storesStore staff, POS IDs, back office
  • ConstructionJob setup, subcontractor insurance
  • Manufacturing and distributionPO entry, supplier dates, legacy ERPs
  • Accounting firmsMonth-end across every client file
  • Field services and tradesService calls to jobs to invoices
  • MSPsNew users and license true-ups
See every industry
Security
Log inBook a Demo

Run work in the cloud and inside your network

  • Personal

    Only you

  • Organization

    Whole company

  • Engineering

    Team

  • Finance

    Team

Cloud containers run 24/7 in Stepwork’s cloud. Local containers run on Windows and Mac desktops, right next to your internal and on-prem systems. Every run lands in the same record.

Book a demo

Work keeps running after everyone logs off

Cloud containers stay on around the clock. Scheduled flows start on time at 2 AM, Slack requests get picked up after hours, and nobody has to leave a laptop open for a run to finish.

Now12:00 AM
12 AM6 AM12 PM6 PM12 AM

Your laptop

Open 9 AM – 6 PM

Open

Cloud container

On 24/7

  1. 2:00 AMUpcoming

    Export payroll changes

    ScheduleLaptop closed
  2. 6:30 AMUpcoming

    Run the weekly access review

    ScheduleLaptop closed
  3. 10:15 AMUpcoming

    Set up a new hire’s apps

    Slack
  4. 3:40 PMUpcoming

    Sync approved invoices

    Webhook
  5. 11:20 PMUpcoming

    Reset a locked account

    SlackLaptop closed

  • On time, any hour

    Scheduled flows start when they’re due, overnight and on weekends.

  • After-hours requests

    A Slack or webhook request at 11 PM runs at 11 PM, not the next morning.

  • No laptop left open

    Runs don’t stop when someone closes a lid, travels, or loses Wi-Fi.

Cloud container or local container

Same flows. Same run record. Different place to run. Cloud is where Stepwork scales. Personal and organization containers come by default, and you create team containers when a group needs its own machine. Local runs on one Windows or Mac desktop while that machine is on, and reaches what that machine can reach.

Cloud container

Local container

Where it runs

Cloud container

Stepwork cloud

Local container

A Windows or Mac desktop

Available in

Cloud container

Desktop and web

Local container

Desktop app for Windows and Mac

Reaches

Cloud container

SaaS and internet-facing apps

Local container

Internal and on-prem apps on your network, plus SaaS

Best for

Cloud container

Schedules, Slack, unattended runs

Local container

Work while that machine is on

How it scales

Cloud container

Personal, organization, and team containers

Local container

One machine per computer

Three cloud containers

Personal and organization come by default. Create team containers when a group needs its own machine.

  • Personal

    Keep this machine private to you

    A personal cloud container is a private machine in the cloud. Use it for sensitive or high-access tasks that should not share a screen with the rest of the organization. Your runs stay on your container. Other people run on theirs at the same time.

    Book a demoRun flows from your chat

    Container

    Start, stop, and sign in to where your flows run.

    Local
    Your personal account
  • Organization

    Your own cloud, not a shared screen

    An organization container is a shared cloud machine for company-wide work. You can create more than one. Each is one screen and one active run at a time. People who can open that container can watch the live view. They do not each get a copy of the run. Use several company-wide containers to separate and triage different streams of work.

    Book a demoHow procedures stay consistent

    Container

    Start, stop, and sign in to where your flows run.

    Cloud
    Your personal account
    Your personal account
    Everyone
    Engineering
    Finance
    Take over
  • Team

    Run your own work on your cloud

    A team cloud container is a shared machine for one group's flows. Finance work can run on Finance's container instead of mixing with company-wide or personal work. Admins create these containers so the organization can scale by team.

    Book a demoBrowse use cases by department

    Container

    Start, stop, and sign in to where your flows run.

    Cloud
    Everyone
    Take over

    New shared container

    Admins and the team's managers can open it and send runs to it.

    Name
    e.g. Finance
    CancelCreate

Triage work across shared containers

Split company-wide work into separate shared containers. Each one runs one flow at a time, the next request waits its turn, and anyone with access can watch the live screen without taking it over.

  • IT requests

    Shared container

    Running
    Live
    Slack

    Reset a locked account

    Up next

    1. SlackGrant Figma access
    2. WebhookOffboard a contractor
    AKMJ2 watching · view only14 done today

  • Finance close

    Shared container

    Running
    Live
    Schedule

    Download vendor invoices

    Up next

    1. ScheduleReconcile card charges
    2. WebhookUpdate a vendor record
    RS1 watching · view only9 done today

  • Security reviews

    Shared container

    Running
    Live
    Schedule

    Collect vendor SOC 2 reports

    Up next

    1. ScheduleExport users for access review
    2. WebhookCheck MFA settings
    LTDNPW3 watching · view only6 done today

Windows and Mac, side by side

Stepwork’s desktop app and its local container run on Windows and Mac. Teams record and run the same flows on either one.

  • Available now
    • Windows
    • macOS

    Windows and Mac desktops

    Install the desktop app on a Windows or Mac machine. Its local container runs flows in an isolated browser on that computer, apart from the browser people use every day.

    How runs stay isolated
  • Enterprise
    • Windows

    Dedicated Windows machines

    For always-on work inside your environment, Stepwork can run on a dedicated Windows machine your team manages, so runs don’t depend on anyone’s laptop being open.

    Talk to us

Connect on-prem systems to the cloud

On-prem and internal apps stay where they are. You choose where each flow runs. Work that needs your network runs on a local container inside it, and everything else runs in the cloud. Every run lands in the same run record.

Your network

  • On-prem app

    On your servers

  • Internal tool

    Only on your network

Local container

Windows or Mac machine

Stepwork cloud

Stepwork

Same flows, same record

  • Schedules and triggers
  • Cloud containers
  • Run record
  • Available now
    • Windows
    • macOS

    A local container in your network

    Install the desktop app on a Windows or Mac machine inside your network. Its local container reaches what that machine can reach: internal tools, on-prem apps, and your SaaS apps.

    How procedures stay consistent
  • Enterprise
    • AWS
    • Microsoft Azure
    • Google Cloud

    Containers in your own cloud

    Run containers in your AWS, Azure, or Google Cloud account, next to your private systems. You control the network and credentials, and Stepwork coordinates the work.

    Talk to us

FAQ

Questions about containers

  • A Stepwork container is an isolated browser environment where a recorded flow runs. It runs on a Windows or Mac desktop as a local container, or always-on in Stepwork's cloud as a cloud container — personal, team, or organization-wide — so runs can keep going when your laptop is closed.
  • Yes. The desktop app and its local container run on Windows and Mac, and the same flows run on either one. Teams that need an always-on Windows machine in their own environment can talk to us about a dedicated setup.
  • Yes, through a local container on a machine inside your network. It reaches what that machine can reach, including internal tools and on-prem apps, and its runs land in the same run record as your cloud runs.
  • Yes, for enterprise teams. Containers can run in your AWS, Azure, or Google Cloud account while Stepwork coordinates the work. Book a demo to plan the setup.
  • So runs keep going when a laptop is closed, and so you can scale work across personal, team, and company-wide machines.
  • Personal is private to you. Organization is company-wide, and you can create more than one. Team is shared by one group and is created when you need it.
  • No. One run on one shared screen. People who can open that container may watch. The next run waits until the current one finishes.
  • No. One active run at a time on that machine.
  • When the work needs apps on your network, such as internal tools or on-prem systems, or should run on a specific Windows or Mac desktop while Stepwork is open on that machine.
  • Administrators create shared cloud containers. Each person gets a personal cloud container.

See your flows run in the cloud and on-prem

Bring a process that touches a cloud app and an on-prem system. We will show it on local and cloud.

Book a demo
Stepwork

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

ProcedureExtractionsContainersDeterministic AgentsMarketplaceUse CasesIndustriesSecurityClaude Co-Work AlternativeStepwork MCPAngelList Case StudyFAQ
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.