Developer-focused computer-use agent for automating legacy Windows desktop applications through natural-language workflows, APIs and SDKs.
Product sources: Cyberdesk official product site + Y Combinator S25 company page
Cyberdesk is a developer-oriented computer-use platform for automating legacy Windows applications. A developer installs its driver on a physical or virtual Windows machine, describes a workflow in plain English and triggers runs through an API; the current product exposes TypeScript and Python SDKs, scheduling, retries, error handling and run observability.1
The platform is aimed at applications that are difficult to integrate through normal APIs, including EHR/EMR systems, ERPs, accounting software and logistics portals.1 Cyberdesk also describes a trajectory/replay architecture in which stable paths can be reused and live computer-use reasoning can be reserved for unexpected states.2 Claims that repeated tasks become fully deterministic or several times faster remain first-party performance claims rather than independently validated benchmarks.
Cyberdesk is currently sales-led. The public site offers a demo and a self-serve waitlist, but no numeric subscription, usage or enterprise pricing was verified on the current public surface.1
That limits up-front cost comparison with conventional RPA or other computer-use platforms. Buyers should request the unit of billing, included runtime or execution volume, infrastructure requirements, support terms, retry/failure billing and any commercial terms for on-premises or regulated deployments during evaluation.
Cyberdesk's security page, updated March 30, 2026, describes encryption in transit and at rest, service-level authorization, environment separation and least-privilege access.3 Highly sensitive values such as passwords and API keys are handled through Basis Theory-backed vaulting; the page says those values are not logged as normal workflow data and are kept out of ordinary model traffic, with aliases persisted where appropriate.3
For model interactions, Cyberdesk says it prefers zero-data-retention configurations where a provider and workload support them and minimizes model inputs to what a task needs.3 The current Privacy Policy, updated May 1, 2026, covers personal, usage and device data as well as virtual-desktop content, and describes retention according to service need, risk and legal requirements.4
The readable public security page links to a Trust Center but does not itself establish a completed third-party compliance certification, so this review does not infer one.3 Independent product evidence is also sparse: the fixed current source audit did not surface an exact-product professional benchmark, review corpus or eligible numeric user-rating dataset. Missing evidence is neutral, but it limits confidence in vendor reliability and performance claims.
Cyberdesk is best suited to developer teams that need to automate real Windows software where no practical API exists. Healthcare intake/data-entry, finance/accounting, logistics and other legacy-enterprise workflows are explicit current use cases.1 Y Combinator independently corroborates the active company and the same developer-facing Windows automation surface.5
The product is not medical decision support merely because some workflows touch EHRs; its role is desktop automation. Organizations using it around patient, financial or other sensitive records should treat data permissions, secret handling, human approval, auditability and rollback as deployment requirements rather than assuming an automated action is correct because the agent completed it.
a clear focus on Windows software that traditional integrations struggle to reach; API and SDK access; reusable workflow trajectories; retries and error handling; structured outputs and observability; support for physical and virtual machines; and thoughtful separation of sensitive secrets from routine model context.13
no public numeric pricing; self-serve access remains waitlist-based; independent reliability and performance evidence is thin; public compliance assurance is less explicit than the underlying security-control description; and write-capable automation in EHRs, ERPs or financial systems requires careful verification and human-control design.
Products matched by shared tasks, audience, workflow, product type and capabilities.