Orkes

Name: Orkes
Brand: Orkes
Rating: 4.4 (31 reviews)

AI Native

Code, debug, and scale your distributed applications faster with Orkes

Est 2020|Valuation $105M|Raised $89.3M|32 Ref Customers

LinkedIn 19K|Web traffic 26K|FTEs 73|HQ Cupertino, California, US

MarketsWorkflow Orchestration

Published Oct 15, 2026

01Common complaints

- Organizations with an all-in AWS strategy and a preference for a native managed orchestration service with integrated IAM and service integrations may find AWS Step Functions operationally simpler and more tightly integrated. - Organizations requiring business-user process modeling and BPMN/DMN governance as the primary interface may be better served by process-oriented BPM suites. - If enterprise identity integration (SSO/SCIM/SAML) is mission-critical, buyers should validate identity-provider compatibility and integration details, as some reviewers have reported SSO integration challenges. - If specific certifications such as ISO 27001 are required and cannot be validated through vendor documentation or due diligence, organizations should consider that limitation in procurement decisions. - If fully self-serve transparent enterprise pricing is a hard requirement, note that detailed enterprise pricing was not publicly available in the materials reviewed. - Known issues surfaced in accessible review excerpts - Identity and SSO integration issues reported by some reviewers. - Intermittent UI performance issues in reviewer excerpts. - Concerns about product update policy and vendor communication in some reviews. - Perceived higher resource requirements for very large deployments in at least one review excerpt. - Limitations/gaps in publicly accessible information - Pricing transparency: enterprise pricing and packaging were not clearly public in the reviewed materials. - Compliance breadth: SOC 2 Type 2 is documented publicly; other certifications (ISO 27001, 27701, etc.) were not confirmed in accessible sources. - Data residency: no public region/residency matrix was identified in the accessible materials. - Roadmap and product-direction signals - Some comparison views and reviews indicate reviewers have differing opinions about roadmap direction; buyers should evaluate roadmap alignment during procurement.

Deal disqualifiers: characteristics of a poor fit

Use cases dominated by simple, short-lived workflows that can be handled with lightweight queues, cron jobs, or a single service.
Primary need for BPMN/business-user process modeling and governance as the main interface.
Situations requiring publicly documented formal security certifications or specific regional compliance attestations that were not available in the reviewed materials.

02Why they buy

- Conductor lineage and continuity - The vendor's founding team includes contributors to the Conductor project, and the offering is positioned to provide a managed path compatible with Conductor semantics. - Compatibility with Conductor OSS plus additional integrations - Vendor materials describe task types and integrations beyond core Conductor OSS, including tasks for language-model operations and human-action steps. - AI orchestration capabilities - Vendor documentation and product descriptions reference integrations with language models, prompt templates, vector databases, and human actions as workflow tasks. - Where competitors have advantages (balanced view) - AWS Step Functions: deep AWS ecosystem integration and a highly managed operational model. - Temporal: code-first deterministic workflow programming model and SDK maturity. - Camunda: business process modeling and governance features.

Why customers chose the product (themes supported by reporting)

Managed path for Conductor
- Reported reasons for selection include a managed option aligned with Conductor semantics and compatibility.
Language-agnostic orchestration and multi-language microservices support
- Observers note language-agnostic value for orchestrating services implemented in multiple languages.

03Field reports

Review platform availability and caveats

- Gartner Peer Insights - High-level ratings and excerpts are available publicly, while full review text may be gated behind the platform UI. - TrustRadius - A dedicated TrustRadius page for the vendor was not located via the queries performed for this report. - G2 - The vendor has a presence on G2 with reviewer counts visible in public snippets; full review details require accessing individual review pages.

Gartner Peer Insights — evidence of mixed sentiment

- Overall rating context - Publicly visible reviewer ratings indicate mixed feedback across a small set of accessible reviews. - Positive themes in review excerpts - Some reviewers describe the platform as reliable and flexible for workflow orchestration and note improved visibility and control after deployment. - Critical themes in review excerpts - Review excerpts cite issues such as SSO integration challenges and concerns about product update policies.

G2 — sentiment signals (limited direct quotation in accessible snippets)

G2 snippets indicate reviewers reported that the product can simplify the construction of complex workflows and supports scalability in some deployments; full review text should be examined for detail.
In comparison views, some reviewers preferred competitor roadmap direction or feature set for certain use cases.

Community and forum discussions (qualitative)

Community and discussion forums reference the product as a managed continuation of Conductor and discuss the ecosystem and stewardship transition.
Community posts include operational and deployment questions that indicate real-world implementation topics and friction points for some teams.

Why some customers expressed dissatisfaction or churn signals

Direct churn narratives were not clearly evident in the materials accessed; however, reviewers cited integration issues (SSO) and communication or update-policy concerns as potential dissatisfaction drivers.

Vendor-identified customers

Industry coverage and vendor materials list several named customers in different sectors.
- These mentions are useful as starting points but are vendor-published and may not include independent validation within the same source.
Critical evaluation
- Buyer diligence should include reference calls, validation of scale/performance claims, and requests for metrics tied to specific business outcomes.

Methodology gaps in vendor claims

Vendor statements about installs, developer counts, or customer-base growth are often not accompanied by methodological detail (definition of "install", timeframe, unique users vs accounts).

Suggested validation items for buyers

Reference call(s) with customers of similar scale and use case.
Quantitative SLO/SLA data (workflow latency, throughput, error rates) from proof-of-concept or references.
A cost model covering per-workflow execution, retries, event volume, operational overhead, and support tiers.

04Best fit

Company sizes

Likely best fit
- Mid-market to enterprise engineering organizations operating distributed systems with multiple services and workflows.
Evidence signals
- Public reviewer excerpts include comments from larger organizations.

Industries and verticals where adoption appears in reporting

Financial services, fintech, and insurance
Media and entertainment
Mortgage and real-estate finance
Healthcare diagnostics (vendor materials reference customer relationships)

Roles and personas

Decision makers
- VP Engineering, Head of Platform Engineering, CTO, Chief Architect
End users
- Backend engineers, SRE/platform engineers, DevOps engineers, workflow/automation engineers

Pain points and challenges the product addresses

Orchestrating multi-step business processes across services with retries, timeouts, and durable state.
Improving visibility and reliability of distributed workflows.
Reducing custom ad-hoc orchestration code scattered across services.

Qualification criteria: characteristics of a strong fit

The organization manages numerous multi-step workflows spanning multiple services and needs consistent durability and observability.
The organization uses Conductor OSS or requires compatibility with Conductor semantics.
The organization prefers a managed offering and vendor support rather than operating the workflow engine internally.

05The pitch

What the product does (core value proposition in objective terms)

Orkes is a workflow orchestration platform built around the Conductor engine. It coordinates long-running, failure-tolerant workflows across microservices, APIs, events, and tasks that involve machine learning models or human-in-the-loop steps.
The offering includes a managed Orkes Cloud, a developer "Playground" for evaluation and development, and enterprise features layered on the Conductor ecosystem.

Target market and market positioning

- Primary buyers/users - Platform engineering, backend engineering, and teams building distributed systems that require durable orchestration (retries, compensation, timeouts, state management). - Teams building AI-integrated workflows that require orchestration primitives and connectors for language models, vector databases, and prompt-based tasks. - Positioning themes observed in vendor materials and third-party descriptions - Described as a modern approach to workflow orchestration for distributed applications, with emphasis in vendor materials on durability, observability, and production operations. - Presented as a managed continuation of the Conductor open-source project after Netflix reduced stewardship of that repository.

Get a comprehensive analysis of Orkes including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →