nunu for desktop software

Fan out 100s of desktop QA agents.
Ship bulletproof releases.

Give them a goal in plain english. Agents drive your software on a Windows desktop we spin up, reading the screen instead of a DOM, so bugs surface before your users hit them.

Free first run for new teams, ends in48h 00m 00s
nexus2 of 118 agents shown
Run 1· Windowsrunning
>Import an OBJ, apply a subdivision modifier, then render a frame.
screwdriver.obj
File
Edit
Render
Scene
Camera
Light
Mesh
Screwdriver being modelled
Modifiers
+ Add Modifier
Viewport 1
Render
Agent 1
Selecting the imported part in the outliner.
57 more agents on this program
Run 2· Windowsrunning
>Create a purchase order with three line items, then post it.
Create Purchase Order
Purchase orderEditGotoEnvironmentSystemHelp
Save
Vendor
100214
Doc. date
04.08.2026
Purch. org
1000
Currency
EUR
Item overview
Delivery schedule
Conditions
Itm
Material
Short text
Qty
Un
Net price
Crcy
10
MAT-901
Hex bolt M8x40
100
PC
4,20
EUR
20
MAT-902
Washer M8
150
PC
1,10
EUR
30
MAT-903
Hex nut M8
200
PC
0,90
EUR
2 of 3 items enteredPRD (100)
Agent 2
Entering the second.
59 more agents on this program
every run reports to
GitHub
Jira
Slack
TestRail

over 30,000 test cases automated by desktop software teams

backed by
built by people affiliated with
ETH ZurichETH AI Center
Handpicked runs

See how our agents do QA for software you know.

Pick a run to watch what our agents tested.

300+more programs tested by our agents
Agent
Blender · Windows
passed
observe

Blender opened on its splash screen, default scene loaded.

machine30 min
Windows VM
11 · 26100
How it works

Describe it. We run it.

1

Write instructions in plain english.

No coding or technical expertise required. Describe what you want to have tested and our AI handles the rest.

2

Let our agents run your tasks.

One agent or hundreds. They drive the machine like an operator does: reading the screen, then clicking, dragging, typing and using shortcuts.

3

Get your results.

Jump straight to a bug via the live stream, or pull every result into your CI/CD pipeline.

Watch every run

Replay it frame by frame, exactly as the agent saw it.

Land on the bug

The timeline marks it. One click and you are there.

See every click

Every click, drag, keystroke and shortcut, with what it asserted at each one.

Wired into CI/CD

Fail the build, post to Slack, open the ticket.

Enterprise-ready

SOC 2 compliant, no scripts to maintain.

What they catch

Bugs that only happen in a real Windows environment you click through.

Scripted tests rarely leave the happy path. Agents go where your users actually go.

Long-running sessions

Leaks and slowdowns that only appear after hours of work, not in a two-minute test.

Real project files

Project files big and messy enough that opening one changes how everything behaves.

Other apps on the same machine

Copy-paste, drag-and-drop, and a file your program hands to another one and gets back.

Dialogs that interrupt

Warnings, recovered drafts and are-you-sure sheets that land mid-flow and are in no test script.

Native file dialogs

Open and save sheets that belong to the OS, not your program, and differ on every one.

Shortcuts and modifiers

Ctrl, Alt and Shift chords, and every shortcut a power user actually reaches for.

Dockable, resizable UI

Workspaces users rearrange, so no two installs present the same layout twice.

Installers and first run

Setup wizards, licence prompts, and the state a program is only ever in the first time it opens.

Coverage

Runs on a full Windows install, the way your users run it.

Windows VMs that behave like a user's desktop, not one golden workstation and not a headless container.

Windows

Windows 11

Point us at a build

no SDK, no code changes

.exe / .msi

Windows installer

portable .zip

unpacked and run in place

artifact URL

straight from your CI

Upload it in Nexus or push it straight from CI, and the fleet picks up the new build and starts the run.

The run viewer

Scrub to the moment it broke.

Click any point on the timeline and see exactly what happened at that moment.

Run 1 · Blender · Windows 111 issuehistory
device view16:14:02
Blender
Modifier Properties16:14:02
toLena Fischer
amount€140.00
fee€0.00
reference · shared dinner
Render Image
[observe]step 14 of 26

Subdivision modifier applied, viewport level set to 3.

# reasoning
Modifier, level and render engine all match what I set. Nothing else was added to the stack, so the mesh is the only thing changed. Checking the viewport before I render.
# result
summary verified · amount €140.00
frame_0412.pnga11y treedevice log
16:13:2016:14:1016:15:0016:15:5016:16:40
16:14:02

Put a fleet of agents on your next build.