Osprio View is the universal software surface for Osprio hardware — one app that hosts every workspace. Run it right in the browser over WebUSB with no drivers to install, or as an optional native client, across Linux, macOS, Windows, Android, and iOS.
Comparing options? See how the plans stack up →
Osprio View is the shell every Osprio workspace runs inside. The per-workspace detail lives on each workspace's own page — this is what the software gives you everywhere.
Open workspaces in tabs inside one app, the way a browser holds many pages. A shared shell owns each tab's state and lifecycle, so the work in one tab stays isolated from the next.
That means you can run a live capture in one tab while emulating a CP or PD in another, switching between them without tearing anything down or losing your place.
Osprio View runs right in the browser and talks to hardware over WebUSB. There is nothing to install — no vendor drivers, no kernel modules, no separate command-line utilities to keep in sync with the app.
Connecting a device is a permission prompt, not a setup project, which is what makes it realistic to pick up an Osprio device on any machine and start working immediately.
A shared session manager enforces cross-tab device exclusivity: a given piece of hardware has exactly one owning workspace at a time.
That is what keeps two workspaces from contending for the same device on the bus — no surprise collisions where a capture and an emulation fight over the same port mid-session.
Update connected-device firmware from the same app, run as a guided flow rather than a separate flashing tool you have to source and trust.
Firmware update sits deliberately outside any live workspace session, so it can never collide with an in-flight capture, emulation, or provisioning run.
Check the health of a connected device without leaving the app or reaching for a separate utility. Built-in diagnostics surface device state, link status, and the readouts you need to confirm hardware is behaving before you start real work.
Because it lives in the same shell as every workspace, a quick diagnostic pass is always one step away — so when something looks off mid-session, you can confirm whether it is the device, the bus, or the test setup without breaking your flow.
Osprio Mini runs a single firmware app at a time, so a given unit can only serve the workspace its current app belongs to — a Mini on the capture app drives Capture, a Mini on the emulator app drives Emulator. The app switcher changes which app is running on a connected Mini right from Osprio View.
That lets one device move between jobs: point a Mini that is currently emulating at the app switcher, flip it to the capture app, and the same hardware is ready to sniff the bus in Capture Workspace — then switch it back when you are done. No separate flashing tool to source, and no second device just to cover a different workspace.
Osprio View ships both light and dark themes, so the app matches the bench, the field, or whatever lighting you are working in — switch on demand without restarting or losing session state.
The theme applies uniformly across every workspace and panel, so packet tables, profile editors, and progress views all stay legible and consistent whichever mode you pick.
The architectural choices that make every workspace above feel the way it does.
Prefer a desktop app? An optional native client wraps the very same interface with OS-level USB access, so you get the identical workspaces installed locally.
It is the same product either way — the browser and native builds share one codebase, so nothing diverges in how the two feel or what they can do.
One codebase runs across Linux, macOS, Windows, Android, and iOS — not a split desktop-and-mobile product line that drifts apart over time.
Whatever you carry to the bench or the field, the workspaces, layouts, and behavior come along unchanged, so there is nothing new to relearn per platform.
Osprio View loads once and stays resident, so moving between workspaces and tabs is instant — no full-page reloads breaking your flow.
Keeping the app in memory is also what lets a workspace hold live session state, like a running capture or emulation, while you work elsewhere in the shell.
Workspaces are modular surfaces inside one parent app, not separate downloads. New workflows ship as new workspaces without a new install or a product rename.
That is why the catalog can grow — Capture, Emulator, Provisioner, and more to come — while the thing you launch stays a single, familiar app.
See the bus. Decode the truth
Live RS-485 capture, structured packet decode, secure channel inspection, and offline session replay.
Test the device you have against the device you need
CP and PD simulation, reusable action automation, secure channel peer validation, and fault injection.
Secure-channel commissioning without the field pain
In-field PD commissioning — address, baud, and SCBK install-mode keying — as live one-at-a-time quick steps or slot-backed batch plans, with per-PD progress and a post-completion key export.
Compliance claims become repeatable evidence
Planned: semi-automated PD conformance testing at the desk, with detailed compliance reports across command coverage and physical-layer behavior.
No. Osprio View runs in the browser over WebUSB with no drivers, kernel modules, or vendor utilities to install — or as an optional native desktop client if you prefer one.
One codebase runs across Linux, macOS, Windows, Android, and iOS — in the browser over WebUSB or as an optional native client — so there's no separate desktop and mobile product.
You can keep several workspace tabs open, but each connected device runs one workspace at a time — a shared session manager enforces device exclusivity so two workspaces never contend for the same hardware. To run workspaces in parallel, connect more than one Osprio device.
Have a question? Ask us →