Compared
Portal Hound vs virtual desktops.
A virtual desktop puts a whole Windows machine in the U.S. and streams it to the worker. For teams whose work is in web portals, that's a lot of machine, cost and lag to get one thing: a U.S. address and a controlled environment. Portal Hound gets that part done without the desktop.
Side by side
| Virtual desktops (Windows 365, WorkSpaces, Citrix) | Portal Hound | |
|---|---|---|
| What the worker uses | A streamed remote desktop; every click crosses the ocean twice | Their own computer and browser; only approved portals cross to the gateway |
| Latency on portal work | Noticeable: typing and scrolling are streamed | Minimal: the browser is local, only portal requests travel |
| Cost per worker | Typically $30 to $70 a month plus licensing and admin | Plans by team size, often well under $20 a seat |
| Control over which sites | Depends on policies you configure on the desktop | Built in: approved portals only, enforced on the gateway |
| Identity and log | Desktop login; auditing depends on your setup | One identity per worker, every portal session logged |
| Data on the worker's machine | None by design, which is the main argument for desktops | Only what the browser holds, as with any laptop; pair with your device policy |
| Setup time | Images, licensing, profiles, patching | Minutes per worker |
When each one fits
Choose virtual desktops when
Workers need installed Windows applications, or policy requires that no data ever reaches an offshore device. Some regulated environments require this.
Choose Portal Hound when
The work is in web portals, you want named identity and a log, and you'd rather not pay for and support a second computer per person.
Use both when
A small group needs installed applications on a hosted desktop, and the larger portal-only group doesn't.
Neither is a way around
A portal's terms. A U.S. desktop and a U.S. gateway both only matter for access you're authorized to have.
Questions
Isn't a virtual desktop more secure because nothing is on the worker's machine?
For data-at-rest on the device, yes. For who reached what, Portal Hound's named identity and log are usually stronger than a shared desktop pool. Many teams find a device policy plus Portal Hound covers their risk at a fraction of the cost.
Can we move from desktops to Portal Hound gradually?
Yes. Approve the portals, roll the app out to one team, and retire their desktops when the team is comfortable.
Does Portal Hound work inside a virtual desktop?
It can, but there's rarely a reason to: the desktop already has a U.S. address. Use one or the other per team.
Related
See it with your own portals.
Fifteen minutes with the worker app and the admin console answers most of this.