IT AI Index

Index › Vendors › Orkes · September 2026 Edition

1 category · Named, not ranked

Orkes

2Judge labels

0First choices

1Negative labels

2 of 12Models named it

1Category

September 2026 Edition. Every number here is derived from the raw labels under vendor table vv2026-09.2, every buyer segment counted.

Standing

1 label, too few to rank

A product needs 10 labels in a category before a share or quadrant is stated. Orkes was named 1 time in Orchestration, where Prefect led with 24%. The labels and the evidence are below, counted exactly.

By buyer segmentRead the same way at every buyer size.

Small businessnot named

No model named it for this buyer.

Mid-market55 of 86

under the label threshold

Enterprise67 of 89

under the label threshold

In orchestration · each standing computed within its segment · bars are 0 to 100 · the accent bar is the product's own best reading

Standing by category

Every category where a model named Orkes for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
Workflow orchestration	Data platform	0%	55 of 86	0%	1	under 10 labels · led by Prefect at 24%

Movement

This is the first edition on this tier, so no move can be computed for Orkes yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated Orkes across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	Mention	Labels
Claude Haiku 4.5	0	0
GPT-5.4 mini	0	0
Gemini 3.5 Flash	0	0
Perplexity Sonar	0	0
Grok 4.1 Fast	0	0
Mistral Small	1	1
DeepSeek V4 Flash	0	0
Llama 4 Maverick	0	0
Qwen 3.7 Flash	0	0
Kimi K2	0	0
GLM 4.7 FlashX	0	0
MiniMax M2.5	0	0

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct0 labelsNone

Paraphrase0 labelsNone

Comparative1 labelNone

Budget-constrained0 labelsNone

Scale-constrained0 labelsNone

Negative1 labelNone

First choiceAlternativeMentionNegative2 labels in all, every segment counted; 0 of the 0 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

No positive label carried a quote.

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

No model argued against it.

Named alongside

The products named in the same answers as Orkes, over the 2 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and Orkes was named but was not.

ProductSame answerTook the first choice insteadHead to head

AWS Step Functions2 of 20Not in the top three

Zapier2 of 20Not in the top three

Appian1 of 20Not in the top three

Azure Logic Apps1 of 20Not in the top three

Camunda1 of 20Not in the top three

Elementum1 of 20Not in the top three

Enate1 of 20Not in the top three

Google Cloud Workflows1 of 20Not in the top three

IBM Business Automation Workflow1 of 20Not in the top three

Kestra1 of 20Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named Orkes. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 2 of the 2 answers that named Orkes and are not a share of its labels.

Domains cited

elementum.ai2

moxo.com2

teamwork.com2

bmc.com1

devopsschool.com1

doczen.com1

enate.io1

infoq.com1

kineticdata.com1

manageengine.com1

Thirteen of the thirteen domain citations in answers naming Orkes came from somebody else's page.

Pages cited

elementum.ai/blog/best-workflow-orchestration-tools2

moxo.com/blog/workflow-orchestration-tools2

teamwork.com/blog/workflow-orchestration-tools2

bmc.com/blogs/workflow-orchestration1

devopsschool.com/blog/top-10-workflow-orchestration-tools-features-pros-cons-comparison1

doczen.com/blog/workflow-orchestration-software1

enate.io/blog/9-process-orchestration-software-solutions-worth-the-hype1

enate.io/blog/workflow-orchestration-tools1

Pages are listed as the models cited them.

Names read as Orkes

What the judge wrote, as written, with how often. The vendor table decides that these count as Orkes; a claim can dispute any of them.

Orkes (Conductor) 1

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when Orkes's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as Orkes, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at orkes.io is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.