Bondi Desktop
Bondi Desktop opens your cloud-hosted workspace in a Windows app with automatic updates, and your team keeps the screens and permissions it has in the browser. On Pro, a button on a published screen prints the PDF document set on it or opens its mapped folder on that computer, after Bondi checks the button on the server.
30-day trial with Pro capabilities · no card required
Started by a person, checked by the server
An owner or admin defines each printer or folder target and its shared default. A person presses the button on the published screen, and Bondi checks it against that screen before the computer prints or opens the folder.
Define the target
An owner or admin defines each printer or folder target and sets a shared default for each environment and operating system.
Map the target
Each computer uses the shared default, or a different printer or folder its user picks on that computer.
A person presses the button (a person acts)
The signed-in person on the published screen presses print or open folder. Nothing runs on the computer until they press it; Bondi then checks the request.
Check and run
Bondi checks the button, operation and target against the published screen and issues a single-use token that expires in two minutes. Bondi Desktop redeems it, then prints or opens the folder.
Diagram of the local-action sequence. Each step and check follows the product's behavior.
What it does
Bondi Desktop loads your cloud-hosted workspace, so screens, records and permissions match the browser. It checks for updates every six hours, downloads them in the background and asks before restarting to install.
Add a print or open-folder button to a screen. A print button prints the PDF document set on it, and a folder button opens a folder inside its mapped root. Each button resolves to the shared default printer or folder, or to one chosen on that computer.
Printing and opening folders start only from a button a person presses on a published screen. Workflows, scans and other screen events can't start them, and the app doesn't run commands or access arbitrary files.
Under the hood
The mechanisms behind the page, for the architects and security reviewers evaluating it.
Read the technical documentationEach use is authorized on the server: the button must be on a published screen the person can open, and its operation, target and PDF document must match that screen. The computer then receives a single-use token that expires after two minutes. Folder paths stay inside the mapped root, and a missing folder is created only when the published button is set to create it.
Owners and admins set the shared default for each target, environment and operating system, stored encrypted on the server. A person can choose a different printer or folder on their own computer; that choice is saved for their Windows user account and affects only that computer.
Your IT team secures each computer and the printers and folders mapped on it. Switching workspace or environment cancels print jobs that are still queued or rendering in the app.
Designed boundaries
The installer and automatic updates are for Windows. Bondi itself remains cloud-hosted.
Local actions follow the signed-in person, not the computer: there is no per-computer enrollment.
Opening a folder shows it in the file manager; it does not save a file into it.
Availability
Questions buyers ask
Not today. The installer and automatic updates are for Windows. On a Mac, your team uses Bondi in the browser.
No. An owner or admin sets a shared default printer or folder once for each environment and operating system, and every computer uses it. A person can choose a different printer or folder on their own computer when their setup differs.
No. Workflows have no step that prints to a local printer or opens a local folder. Local actions start only when a person presses the button on a published screen.
Yes. A hardware scanner reads Bondi's signed QR codes on screens with a scan listener, or on every app screen once you add a global listener, and runs the action set on that listener. It works the same in the desktop app as in the browser. Print and folder buttons don't control the scanner.
Next step
Name the documents your team prints and the shared folders it opens by hand. We'll show which ones become a button on the screen where the work happens.
