Kryon

Name: Kryon
Brand: Kryon

Find us on the Nintex LinkedIn channel, focusing on process management, optimization and automation.

Est 2008|Valuation $100M|Raised $65.3M

LinkedIn 19K|Website|FTEs 150|HQ Bellevue, Washington, US

MarketsBusiness Process Management (BPM)Workflow Automation

Published Sep 26, 2026

01Common complaints

- Organizations that require extensive community support and abundant online troubleshooting resources: public reviews indicate a smaller community and greater reliance on vendor support tickets. - Procurement scenarios that require a continually available standalone vendor identity: Kryon has been integrated into Nintex, and buyers concerned about vendor continuity or standalone branding should include this consideration in vendor selection criteria. - Workloads with high sensitivity to runtime stability and memory usage: public reviews include reports of crashes and memory consumption; buyers should validate current product versions in a pilot with representative applications. - Organizations requiring transparent, self-serve pricing and predictable, published licensing models: Kryon (as a standalone brand) does not have clearly published pricing in public sources reviewed for this report.

Deal disqualifiers (poor fit)

- Organizations that prioritize a very large community, broad third-party marketplace, and abundant talent supply may favor alternatives with larger ecosystems (for example, UiPath or Microsoft). - Workloads requiring demonstrable runtime stability without historical stability concerns should validate current software performance via a pilot before procurement. - Buyers seeking fully transparent, self-serve pricing may find vendor-driven negotiated pricing models to be a poor fit.

Known issues highlighted by reviewers

Reported crashes, bugs, and memory consumption concerns in some deployments
Smaller online community and limited forum content, increasing dependency on vendor support

Roadmap and packaging uncertainty

Because kryonsystems.com now redirects to Nintex, buyers should assume that branding, packaging, and feature consolidation may continue as Nintex integrates Kryon-origin capabilities into its broader product lineup.

Security and compliance documentation gaps

While Nintex’s RPA pages reference several certifications and alignment statements, specific public artifacts (for example, SOC 2 report scope and type, hosting and data residency details) were not located in the public sources reviewed. Buyers should request these documents and clarification on security controls.

02Why they buy

Features commonly cited in vendor materials and customer feedback (with caveats)

Process discovery integrated with automation workflows: Kryon historically emphasized a workflow that combines discovery and bot creation.
Relatively short reported ramp-up and user-friendly visual design: multiple user reviews referenced a learning curve that some users found modest compared with other platforms.

Areas where competitors may have advantages

Ecosystem scale, community resources, and partner networks are generally larger at UiPath and Microsoft, which can affect hiring, training, and third-party solution availability.
Independent, third-party benchmarking and broader analyst coverage are more prevalent for larger vendors, which can provide additional validation data for procurement.

Why customers chose Kryon (observed patterns)

Review patterns and vendor materials suggest reasons cited for selection include:

Short time-to-adoption reported by some users.
Visual, UI-centric automation capabilities.
Emphasis on process discovery in vendor positioning.

03Field reports

Because Kryon has been acquired and the brand has shifted, review data can be fragmented (some reviews refer to Kryon while others surface under alternate product names or under Nintex). Historical review platforms provide signals but require careful interpretation.

Review platform highlights — examples of positive feedback

From Capterra and similar review narratives referencing Kryon-related capabilities:

Multiple reviewers cited relatively short ramp-up times and suitability for users new to RPA.
Training and onboarding content (vendor "Academy" style materials) were mentioned positively in several reviews.

Review platform highlights — examples of criticism

Negative themes include:

Smaller community and limited forum resources: reviewers noted smaller community presence and a heavier reliance on vendor support tickets.
Stability and performance concerns: some reviewers reported software crashes and higher-than-expected memory consumption.
Integration gaps: reviewers cited missing integrations such as certain cloud-native document editors as a limitation in some deployments.

G2 and other review sites

Searches surfaced multiple product pages with overlapping or similar names, indicating naming collisions and the need for careful filtering when using general review aggregators.

Why some customers left / churn signals (inferred)

Primary churn risk indicators from available reviews include:

Reliability issues (crashes/bugs)
Smaller community and limited self-serve troubleshooting resources
Negotiated pricing and licensing variability, which can be unpredictable across deals

Vendor-published customer examples (not independently validated)

Vendor press materials and announcements have listed notable customers across industries. These references indicate vendor-reported relationships but do not provide independently audited outcomes or verified ROI calculations.

ROI claims — methodology concerns

Vendor materials have included specific ROI and time-reduction claims. Public sources reviewed for this report did not provide sufficient methodology detail (sample sizes, assumptions, license costs, labor rates, bot utilization rates) to independently validate those figures. Such claims should be treated as vendor-reported and validated through customer references, pilots, or third-party audits where required.

04Best fit

Company size

Most plausible ICP: mid-market to enterprise organizations with multiple repeatable back-office workflows and sufficient scale to justify governance.

Industries

Industries referenced in vendor and customer materials include:

Financial services and insurance
Telecommunications
Technology
Healthcare (examples of process automation were referenced in industry press)

Roles and personas

Decision makers: CIO/IT leadership, Head of Shared Services, Automation CoE lead
End users: business analysts, RPA developers, operations analysts, and frontline staff who may use attended bots

Qualification criteria (good fit)

Many repetitive, rules-based tasks across multiple UI applications (including legacy systems)
Interest in identifying automation candidates using discovery tools
Willingness to adopt Nintex ecosystem capabilities given the consolidation of product lines

05The pitch

What the product does (core value proposition)

Kryon is an enterprise Robotic Process Automation (RPA) and process discovery product that provides automated discovery of repetitive user tasks and process variants and tools to build and deploy attended and unattended software robots. The offering includes capabilities for computer-vision style automation (operating across web, desktop, legacy, and Citrix-style UIs), optical character recognition (OCR), and analytics/monitoring. Important market reality: Kryon was acquired by Nintex. As a result, kryonsystems.com redirects to Nintex’s RPA product page and Kryon is part of the broader Nintex automation portfolio rather than a standalone vendor site.

Target market and positioning

- Target buyers: Operations/Shared Services leaders, IT automation teams, Centers of Excellence (RPA CoE) teams, and business analysts seeking task/process discovery and RPA execution. - Positioning: Historically positioned around an end-to-end workflow (discovery → automation). Vendor materials present this approach as intended to reduce implementation time and to facilitate adoption by non-technical users; independent validation of those claims is limited in the public materials reviewed. - Typical environments: Enterprises with mixed legacy and modern applications; departments seeking attended "desktop assistant" automations and back-office unattended bots.

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

Download full report →