qventisqventis

Automate the desktop apps your tools can't see

Custom-drawn grids and remote sessions break coordinate scripts. Qventis recognizes every control by sight and records each click as a plain-English step that runs the same every time.

  • Finds controls by sight
  • Citrix and remote desktop
  • No app source needed
Post a journal entryDesktop, recorded, 5 steps
  1. Open the 'Ledger' app

  2. Choose 'Journal' from the 'Entry type' list

  3. Set cell 'Debit' to '{{entry.amount}}' on row 1

  4. Click the 'Post' button

  5. Check that the 'Balance' label shows '0.00'

Where desktop automation breaks down

Custom-drawn controls

Buttons and grids painted straight to the screen look like controls to a person and like a blank rectangle to an accessibility API.

WPF and WinForms panes

Third-party and older components expose little to the tree, so scripts fall back to coordinates and break.

Unmaintained drivers

WinAppDriver is no longer actively maintained, per Microsoft's public repository. Teams built on it need a path forward.

How Qventis sees every control

Vision recognition

The engine looks at the screen the way a tester does. It finds the 'Post' button by what it shows and where it sits.

  • No source code or hooks in the app
  • Works on custom-drawn grids and panes
  • Zero AI tokens at run time
See the Qventis Engine

Questions

Do we need source code or hooks in the app?

No. Vision recognition works from what is on screen, so the app stays unchanged.

Is AI used to find controls during a run?

No. Recognition is compiled into the test ahead of time and runs deterministically.

Can we keep our existing web framework?

Yes. Start with desktop alone and call the engine from your current framework through the CLI.

See your hardest desktop app automated live

We record a flow with you and run it from the CLI.