whats-best.ai
Search Sign in

Workflow Management

Process Street

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Process Street, Inc. · www.process.st

Report an error on this page Is this your product? →

Link to this page

Process Street: AI-assisted analysis on whats-best.ai Process Street: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Process Street at a glance

Vendor
Process Street, Inc.
Headquarters
Not stated on the vendor’s pages as of 13 Oct 2026
Data hosting
Not stated on the vendor’s pages as of 13 Oct 2026
Free plan
Not stated on the vendor’s pages as of 13 Oct 2026
Panel verdict
The AI panel rates Process Street 1.5/5, the mean of 6 judges. Process Street, Inc. how scores are made
As of
Vendor pages captured 1 Oct 2026 to 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources

Process Street alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Head of IT

Weighted verdict

Answers for every automation a department builds without asking. Wants SSO, separate test and production, an inventory of workflows with their owners — and an exit: definitions exportable as BPMN or documented JSON, a self-hosted edition, and an engine licence that will still apply in five years.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Head of IT

Panel median The Head of IT This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Head of IT
Process design, forms & approvals 2.5 of 5 2.5 of 5
Connectors, API & on-premise reach 2 of 5 2 of 5
Execution, error handling & monitoring 1 of 5 1 of 5
Governance, credentials & audit trail 2 of 5 2 of 5
Hosting options & portability 1 of 5 1 of 5
European sovereignty 0.5 of 5 0.5 of 5

Process design, forms & approvals

How this is scored

Modelling the process people take part in: a visual designer or BPMN, forms, approval steps with roles and substitutes, deadlines and escalation, and versioning of a process that is already running — judged on whether a business owner can change a process without breaking the instances in flight.

0 — Linear trigger-action chains only; no human steps, no forms and no statement on approvals or roles.

3 — A visual builder with branching and a simple approval step, but approvers are named individuals rather than roles, there are no deadlines or escalation, and changing a process has no versioning.

5 — A visual designer with conditions and parallel paths, built-in forms, approval steps assigned to roles or groups, deadlines with reminders, and versions of a process kept with the running instances on their original version.

8 — BPMN 2.0 modelling or an equivalent documented notation, substitutes and escalation chains, multi-stage approvals with four-eyes rules, forms in German with validation and file upload, a task inbox for participants, and a test or simulation mode before publishing.

10 — The process is a governed asset: version history with diff and rollback, migration of running instances to a new version documented, process analytics on cycle time and bottlenecks per step, and the design documented well enough that a business team can maintain it without the vendor.

Report an error

The Head of IT

The captured feature list gives conditional logic, form fields, approvals with role assignments, dynamic due dates and revision restore — a business owner can genuinely change a checklist process. I found no public information on parallel paths, reminders or escalation chains, substitutes, a test or simulation mode before publishing, or whether running instances keep their original version when the workflow changes; version history is mentioned as tracked automatically, but only revision restore is described. 2 12 13

Report an error

Connectors, API & on-premise reach

How this is scored

Reaching the systems a European company actually runs: maintained connectors judged by name rather than count, a generic HTTP and webhook step, custom connectors, and a way to reach systems behind the firewall without opening it.

0 — No connectors beyond email, and no API or webhook step.

3 — A large connector count on a logo wall, with no statement of which actions each supports or who maintains them, and no generic HTTP step.

5 — Named connectors with their triggers and actions documented, including Microsoft 365 and at least one ERP or accounting system common in DACH (e.g. SAP, DATEV, Microsoft Dynamics), a generic HTTP/REST step, inbound webhooks, and a documented API to start and query workflows.

8 — Custom connectors buildable from an OpenAPI description or code, an on-premise agent or self-hosted runner reaching internal databases and file shares, SOAP and database steps, OAuth handled per connection, and connector maintenance ownership (vendor, partner or community) stated.

10 — Integration is engineered: a versioned public API with a deprecation policy, connector changelogs, rate limits per connector published, event-driven triggers rather than polling where the source allows it, and the vendor maintaining the German-market connectors (DATEV, SAP, ELO or d.velop) itself.

Report an error

The Head of IT

Named connections are real — Google Sheets, Slack, DocuSign, Salesforce and Jira natively, plus middleware through Zapier, Make, Power Automate and Tray.io with the Power Automate connector's actions spelled out — and there is a documented API and outbound webhooks from workflows, data sets and forms. I found no public information on a generic HTTP/REST step, inbound webhooks, connectors for SAP, DATEV or Dynamics, connector maintenance ownership, or any agent reaching systems behind our firewall. 2 8 8

Report an error

Execution, error handling & monitoring

How this is scored

What happens when a step fails at 3 a.m.: retries, error paths, alerting, an execution history someone can search, limits on runtime and throughput, and a status page that admits incidents.

0 — Nothing stated about failed runs; an error stops the workflow silently.

3 — Failed runs are marked and an email is sent, but retries are manual, execution history is short or undocumented, and runtime and throughput limits are unstated.

5 — Automatic retries with configurable back-off, an error path or error workflow, a searchable execution log with input and output per step, failure alerts by email or chat, and runtime, payload and rate limits documented.

8 — Replay of a failed run from the failing step, idempotency guidance, queueing and concurrency controls, execution history retention stated per plan, monitoring exportable to the customer's own tools, and a public status page with incident history and an uptime commitment.

10 — Operations are designed for production: an SLA with service credits, horizontal scaling or high-availability setup documented for self-hosted installs, dead-letter handling, end-to-end tracing across workflows, and post-incident reports published.

Report an error

The Head of IT

The captured pages are silent on failure: I found no public information on retries, error paths or error workflows, failure alerts, execution-history retention, or runtime, payload and rate limits, and no status page. What is documented is regular backups and time-stamped logs of every action, and the terms reserve the right to modify or discontinue the service without notice — I would not run an unattended process on that. 3 4 12

Report an error

Governance, credentials & audit trail

How this is scored

Keeping automation from becoming shadow IT: roles and permissions, SSO, where connection credentials are stored, separate environments with controlled publishing, an audit trail of changes and approvals, and what the execution log retains of the payload. An approval record is also a record of employees' behaviour, so what the trail captures matters to a works council.

0 — Single-user accounts or one shared login; no roles, no audit log and no statement on credential storage.

3 — Admin and member roles and shared team folders, but credentials are visible to anyone who can edit a workflow, there is no audit log, and execution payloads are kept without a stated period.

5 — Role-based permissions per workflow or folder, SSO via SAML or OIDC, credentials stored encrypted and usable without being revealed, an audit log of workflow changes, and the retention period of execution data stated.

8 — Separate development, test and production environments with a publishing approval, SCIM provisioning, external secret stores supported, payload redaction or log-off per workflow, configurable execution data retention, and the audit trail exportable — with the fields it records about users described.

10 — Governance a works council and an auditor can both sign off: field-level masking of personal data in logs, delegated administration per department, a central inventory of every workflow and connection with its owner, certifications published (ISO 27001 or SOC 2), and documentation of what the platform records about individual users.

Report an error

The Head of IT

Documented roles — Users, Managers, Admins — with distinct permissions, task permissions and an audit history of who did what, when and with which supporting information give me something to govern with. But I found no public information on SSO via SAML or OIDC, SCIM provisioning, where connection credentials are stored, separate test and production environments with controlled publishing, export of the audit trail, or vendor certifications, and the only retention statement I found is "for as long as your account is active or as needed". 3 11 13

Report an error

Hosting options & portability

How this is scored

Where the engine runs and whether the workflows can leave: cloud regions, self-hosted or on-premise editions, the licence of the engine, and export of workflow definitions in a format another tool or a later version can read.

0 — Cloud-only with no stated region, and no export of workflow definitions.

3 — Cloud-only with a region named, and an export that produces a proprietary file only the same product can import.

5 — An EU cloud region selectable, workflow definitions exportable as documented JSON or BPMN 2.0, and an API to read definitions and execution history for backup.

8 — A self-hosted or on-premise edition with its system requirements documented, workflow definitions versionable in Git, the engine's licence published, and a documented migration path between cloud and self-hosted in both directions.

10 — The customer owns its automation: an open-source or source-available engine, definitions in an open standard executable elsewhere, air-gapped installation supported, and a stated exit process that hands back definitions, credentials metadata and execution history in documented formats.

Report an error

The Head of IT

A private cloud option with dedicated infrastructure is offered as a middle ground, and the terms mention tools to export information including user content to third-party services. I found no public information on a self-hosted or on-premise edition, a cloud region, the engine's licence, or export of workflow definitions as documented JSON or BPMN — so I cannot see an exit for our processes, and that is a blocker for me. 4 13

Report an error

European sovereignty

How this is scored

Who the contracting entity is, where workflows execute and where execution logs with their payload copies are stored, and who the subprocessors are — including the AI model providers behind any AI steps. Independently sourced by the sovereignty pipeline. A self-hosted edition counts only for the data that actually stays on the customer's servers.

0 — Non-EU vendor and contracting entity, execution location unstated, and subprocessors unnamed.

3 — An EU region offered as an option while the contracting entity is non-EU, or the subprocessor list is absent, or AI steps send data to model providers of unstated location.

5 — EU execution and log storage as standard and an EU contracting entity, but parts of the chain — AI steps, support access, telemetry — are non-EU without an explained safeguard.

8 — EU execution on named infrastructure, EU contracting entity, subprocessor list published with locations including AI providers, a DPA covering execution payloads, and a self-hosted option that sends no workflow data to the vendor.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, AI steps runnable on European or self-hosted models, certification published, and a self-hosted edition that works without any call home.

Report an error

The Head of IT

The contracting entity is Process Street, Inc. of San Francisco, and I found no public information on where workflows execute or where execution logs are stored, on a subprocessor list, or on which AI providers run behind the Dash and Cora agents and where they sit. The privacy policy's commitments — no AI training on our data, per-tenant isolation and secrets encrypted at rest — are safeguards, but they are not location transparency. 3 4 13

Report an error

Pricing transparency not rated — the vendor publishes no price

How this is scored

Whether a buyer can compute the monthly cost of their own processes from public pages alone: what the billing unit is (task, operation, execution, run, user or flow) and what counts as one, the allowance per tier, overage prices, and the cost of premium connectors, self-hosting, environments and AI steps.

0 — No public prices at all; every tier is a sales conversation.

3 — A starting price exists, but the billing unit is undefined or what counts as one task or execution is unstated — the invoice is unknowable.

5 — Tier prices public with the billing unit defined and the monthly allowance given, but at least one commonly needed piece (overage, premium connectors, extra environments, self-hosted licence, AI steps) is unpriced.

8 — Every tier priced publicly with its unit, allowance and limits, overage priced per unit, premium connector and add-on prices listed, self-hosted licensing stated, minimum term and VAT treatment given.

10 — Complete price computability: the monthly cost derivable for a given number of workflows, runs and steps per run, with a published calculator or worked examples, every add-on and overage on a public page, and the effect of loops and retries on the count explained.

Report an error

The Head of IT

The captured pricing page lists features, apps, branding options and support services, but I found no public prices, no tier structure and no billing unit — whether you pay per user, per run or per task is not stated. The only commercial path shown is a "Contact sales" link, so a buyer cannot compute even a baseline monthly cost. 1 2

Report an error

European sovereignty — proven facts

0 of 4 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Ownership Not determined — uncited Report an error
Data residency Not determined — uncited Report an error
Subprocessors Not determined — uncited Report an error

Questions about Process Street

Is Process Street European?

No. whats-best.ai classifies Process Street as Rest of world.

Where does Process Street store data?

Not stated on the vendor’s pages as of 13 Oct 2026.

Does Process Street have a free plan?

Not stated on the vendor’s pages as of 13 Oct 2026.

What are the best alternatives to Process Street?

As of 15 Oct 2026, the panel rates Tray.ai (3/5), n8n (3/5) and Camunda (2.5/5) highest among the other 16 Workflow Management products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is n8n (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Process Street alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about Process Street? Tell us Report an error on this page

Sources (13)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage www.process.st Checked 13 Oct 2026 Details →
  2. 2 Pricing page www.process.st Checked 13 Oct 2026 Details →
  3. 3 Privacy policy www.process.st Checked 13 Oct 2026 Details →
  4. 4 Terms of service www.process.st Checked 13 Oct 2026 Details →
  5. 5 Process design, forms & approvals — found from sitemap www.process.st Checked 13 Oct 2026 Details →
  6. 6 Process design, forms & approvals — found from sitemap www.process.st Checked 13 Oct 2026 Details →
  7. 7 Connectors, API & on-premise reach — found from sitemap www.process.st Checked 13 Oct 2026 Details →
  8. 8 Connectors, API & on-premise reach — found from sitemap www.process.st Checked 13 Oct 2026 +1 earlier capture: 1 Oct 2026 Details →
  9. 9 Execution, error handling & monitoring — found from sitemap www.process.st Checked 13 Oct 2026 Details →
  10. 10 Execution, error handling & monitoring — found from sitemap www.process.st Checked 13 Oct 2026 Details →
  11. 11 Governance, credentials & audit trail — found from sitemap www.process.st Checked 13 Oct 2026 Details →
  12. 12 Governance, credentials & audit trail — found from sitemap www.process.st Checked 13 Oct 2026 Details →
  13. 13 Hosting options & portability — found from sitemap www.process.st Checked 13 Oct 2026 Details →