Available to approved private-beta participants.
Remote support, built around the session
Support now.
Stay ready.
Start on-demand Windows sessions with a one-time code today. Secure unattended access and macOS support are in development—inside the same focused workspace.
- 01Code verified
- 02Device context ready
- 03Displays available
Current product availability
Persistent access for deliberately enrolled devices.
Compatibility and deployment details will publish before beta.
Two ways in. One workspace.
Help when they call. Return when they're away.
ScreenViewer is growing from a fast on-demand support tool into a complete remote-support workspace for authorized Windows and Mac endpoints.
On-demand support
Start an attended session with a one-time code when someone needs help right now.
- A direct request-to-session flow
- Visible connection state and device context
- Multi-display navigation that stays out of the way
Unattended access
Return to deliberately enrolled devices for maintenance and support without waiting for someone to join.
- Persistent access to approved endpoints
- Technician and device-level authorization
- Fast revocation and accountable session history
From “hello” to “fixed”
A shorter path to the work.
Share a code
Give the user a single-use code for an on-demand support session.
Connect clearly
Enter a focused workspace with the session state and device context in view.
Fix what matters
Control the screen, move between displays, and finish the job.
Platform roadmap
Windows first. macOS next.
Platform support is stated plainly so beta participants know what they can use today and what they are helping us build.
On-demand support, available now.
Start with a one-time code, keep the remote screen central, and move between displays from a focused technician workspace.
Mac control, built with Apple's rules in view.
Development is focused on clear privacy-permission setup, exact compatibility guidance, and a trustworthy deployment path for IT.
| Capability | Windows | macOS |
|---|---|---|
| On-demand sessions | Private beta | In development |
| Unattended access | In development | In development |
| Multi-display workspace | Private beta | Planned |
| Managed device enrollment | In development | In development |
Security, without the footnotes
Access should always be clear.
On-demand sessions begin with a one-time code and visible connection state. Before unattended access reaches beta, the product is being designed around approved devices, scoped technician access, fast revocation, and accountable session history.
Detailed security documentation will expand as each capability is validated and released. No unearned compliance badges. No vague “military-grade” claims.Deliberate enrollment
An unattended endpoint should be explicitly approved and easy to remove.
Scoped access
Technicians should reach only the devices their role allows.
Visible accountability
Every connection should leave a clear, reviewable history.
Built for the people behind the fix
One remote workspace. Every kind of IT support.
Internal IT
Give employees a faster, calmer path back to work across the devices they use.
IT consultants
Keep client support direct, personal, and easy to move between.
Managed providers
Build toward persistent, authorized access without losing customer context.
Shipping deliberately
What's live. What's next. No blurred lines.
Windows on-demand beta
One-time codes, a focused connection flow, and multi-display navigation.
Authorized unattended access
Device enrollment, persistent reach, scoped technician access, and session history.
macOS support
Remote control with explicit compatibility and Apple privacy-permission guidance.
Team operations
Expanded administration, integrations, and workflows for growing support teams.
Straight answers
Before you join the beta.
What can I use today?
On-demand Windows remote support is available to approved private-beta participants.
Are macOS and unattended access available?
Not yet. Both are in active development and will be introduced to beta participants when they are ready to test.
What does unattended access mean for ScreenViewer?
An IT team enrolls and authorizes a device once, then approved technicians can reconnect without someone being present. Enrollment, technician access, revocation, and session accountability are part of the product design—not afterthoughts.
How will Mac setup work?
Remote control on macOS requires Apple privacy permissions. The Mac beta will include clear setup guidance and will publish exact compatibility and deployment requirements before release.
Who is the beta for?
Internal IT teams, independent technicians, and managed service providers who regularly support Windows users and want to help shape Mac and unattended workflows.
Private beta
Help build the remote-support tool you want to use.
Join IT professionals testing ScreenViewer on Windows and shaping unattended access, macOS support, and the workflows that come next.
Request beta access Or write to hello@screenviewer.ioWindows on-demand available · Mac + unattended in development