Softwr

Automation Integration · head to head

Orkes vs Testsigma

Orkes logo

Orkes

Automation Integration

Commercial Conductor, now the maintainer of the workflow engine Netflix archived

From
Free
Free plan
Yes
Testsigma logo

Testsigma

Testing

Natural language test automation for web, mobile and API with a self hosted open source edition

From
Free
Free plan
Yes

The short version

  • Both are free.
  • Only Orkes lists JSON workflow definitions; only Testsigma lists natural language authoring.
  • Where Testsigma falls short: support and engineering are concentrated in Indian time zones, which slows incident turnaround for teams working in the Americas.
  • Prices and features on this page were last checked on 20 November 2026.

How do Orkes and Testsigma differ?

Orkes and Testsigma differ on pricing model (Quote against Per user per month), platforms and category. Only the attributes on which Orkes and Testsigma actually diverge.

Attributes where Orkes and Testsigma differ
AttributeOrkesTestsigma
Pricing modelQuotePer user per month
PlatformsLinux, Self-hosted, WebWeb, iOS, Android, Linux
CategoryAutomation IntegrationTesting

Identical on both: starting price (Free), free tier (Yes).

Which features does each one have?

They share no listed features; 8 appear only for Orkes and 6 only for Testsigma. Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Orkes

  • JSON workflow definitions
  • Polyglot workers
  • Visual workflow builder
  • AI and LLM tasks
  • Human tasks
  • Event handlers
  • RBAC and secrets
  • Hosted or self-hosted

Only in Testsigma

  • Natural language authoring
  • Unified web, mobile and API tests
  • Self hosted community edition
  • Cloud device and browser grid
  • Data driven runs
  • Custom functions

What is each one used for?

The jobs each tool is most often brought in to do.

Orkes

  • A microservices estate that needs orchestration across services written in different languages without a shared SDKnot Testsigma
  • A team already running Conductor OSS that wants a supported distribution now that Netflix has stopped maintaining itnot Testsigma
  • An AI platform composing agent steps, model calls and vector lookups as versioned workflow definitionsnot Testsigma
  • A business process needing human approval steps interleaved with automated service callsnot Testsigma

Testsigma

  • A team maintaining separate Selenium and Appium suites that wants one place for web and native mobile coveragenot Orkes
  • Organisations that must keep test data and execution on premises for regulatory reasonsnot Orkes
  • QA groups with manual testers being asked to automate without first learning Javanot Orkes
  • Evaluating low code test automation properly before committing budget, by running the free edition against the real applicationnot Orkes

Where do Orkes and Testsigma fall short?

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Orkes

  • Netflix archived the Conductor repository in December 2023 and Orkes took over maintenance, so the large-company backing that justified many original adoptions no longer exists
  • Enterprise pricing is entirely unpublished, and the only free option is explicitly a prototyping sandbox whose limits can change at any time, so there is no supported low-cost entry point
  • Self-hosting Conductor OSS in production means operating the engine plus its persistence and indexing dependencies, typically Postgres or Cassandra with Elasticsearch, which is a substantial platform commitment
  • JSON workflow definitions are language agnostic but verbose and awkward to test, and teams accustomed to defining workflows in code find them a step backwards in developer experience
  • Orkes is a small company whose commercial future is tied to a single open source project it also maintains, which concentrates both vendor and project risk in the same place

Testsigma

  • The natural language layer is a fixed vocabulary rather than real English, so testers spend the first weeks learning which phrasings the parser accepts, which is learning a language after all
  • Anything conditional or arithmetic falls through to custom Java or JavaScript, and that code lives in the platform editor rather than your repository, where it gets no code review and no version history you control
  • The community edition lags the cloud product and is not the version the vendor demonstrates, so a self hosted evaluation can understate or overstate what you would actually buy
  • Cloud execution is billed separately from authoring seats, so a suite that grows from two hundred to two thousand tests changes the bill without anyone changing the plan
  • Support and engineering are concentrated in Indian time zones, which slows incident turnaround for teams working in the Americas

How much do Orkes and Testsigma cost?

Orkes is free to use; Testsigma is free to use. Plan by plan below, from each vendor's own pricing page.

Orkes

Free
  • Developer EditionFree
    • All Conductor OSS features plus enterprise capabilities
    • Sandbox for prototyping only
    • Rate limits and resources may change without notice
  • EnterpriseOn request
    • Availability SLA up to 99.99%
    • Orkes-hosted or customer-hosted deployment
    • Dedicated technical account manager

Testsigma

Free
  • Community EditionOn request
    • Self hosted, open source, no licence fee
    • You supply the infrastructure and the browser or device grid
  • CloudOn request
    • Priced per authoring user with additional charges for parallel cloud executions and device minutes
    • Published tiers exist but the figures that matter at team scale come from sales
  • ProOn request
  • EnterpriseOn request

Which should you pick?

Choose Orkes if

  • You need json workflow definitions.
  • You want to start without paying.
  • You work on Linux, Self-hosted, Web.
  • You also want polyglot workers.

Choose Testsigma if

  • You need natural language authoring.
  • You want to start without paying.
  • You work on Web, iOS, Android, Linux.
  • You also want unified web, mobile and api tests.

Questions people ask

Is Orkes or Testsigma better?
Neither clearly leads. Orkes starts at Free and Testsigma at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Orkes or Testsigma?
Orkes starts at Free and Testsigma at Free.
Does Orkes or Testsigma run on more platforms?
Orkes runs on Linux, Self-hosted, Web. Testsigma runs on Web, iOS, Android, Linux.
Can I use Orkes for free?
Both have a free tier, so you can try either at no cost before committing.
What is Orkes best used for?
Orkes is most often used for a microservices estate that needs orchestration across services written in different languages without a shared sdk, a team already running conductor oss that wants a supported distribution now that netflix has stopped maintaining it, an ai platform composing agent steps, model calls and vector lookups as versioned workflow definitions, a business process needing human approval steps interleaved with automated service calls. Of those, a microservices estate that needs orchestration across services written in different languages without a shared sdk and a team already running conductor oss that wants a supported distribution now that netflix has stopped maintaining it are not what Testsigma is typically brought in for.
What can Orkes do that Testsigma cannot?
Orkes covers JSON workflow definitions, Polyglot workers, Visual workflow builder, AI and LLM tasks. Testsigma covers Natural language authoring, Unified web, mobile and API tests, Self hosted community edition, Cloud device and browser grid.

Answered from the vendors’ own pages

Orkes: Does Netflix still maintain Conductor?

No. Netflix archived its repository in December 2023. The open source project continues at conductor-oss under Apache 2.0, maintained by Orkes.

Testsigma: Is the open source edition genuinely usable in production?

Yes for self hosted execution, though it trails the cloud version on newer features and you maintain the grid yourself.

Orkes: Is there a free production tier?

No. The Developer Edition is a sandbox that the vendor states is unsuitable for production. Self-hosting Conductor OSS is the free production route.

Testsigma: Do testers need to know Selenium?

Not to write ordinary steps. They will need someone who does as soon as the suite needs custom functions or awkward waits.

Orkes: What does Enterprise cost?

Nothing is published; it is quoted by deployment and support requirements.

Testsigma: Can it test native iOS and Android applications?

Yes, through Appium underneath, on the hosted device grid or your own devices.

Orkes: How does it compare with Temporal?

Conductor uses declarative JSON workflow definitions and external workers; Temporal defines workflows in code. Temporal has the larger community.

Share

Related pages

Other head to heads