
Remote desktop, inside the network
Staff and partners use their own RDP, VNC and SSH clients, with no remote desktop exposed to the internet.

Two usual ways in, two trade-offs
An exposed remote desktop
A forwarded RDP or VNC port to the office PC. It is simple to set up, and it is exactly what scanners on the internet look for.
A remote-control tool
Their agent on every machine you want to control, and one screen at a time. The file share, the database and the SSH session need a detour.

In the network, with the clients you have
- 1
One device in the network
Awacino runs on the office PC itself or on another device in the network: a Mac, a PC or a server with the unattended client, also with nobody logged in.
- 2
Checked before connecting
The member signs in with the company account. Our server checks the role, the assigned devices and, with 2FA on connect, a fresh second factor, then introduces the two devices.
- 3
Direct, then your own client
The two devices connect directly, end-to-end encrypted. The laptop gets a SituIP in the office network, and the remote desktop opens in the client the member already uses.

Remote desktop is one service among many
Remote desktop
RDP, VNC or SSH with the clients staff already use. On Windows, mstsc is already installed.
Files and databases
SMB shares, web interfaces, PostgreSQL, MySQL and SQL Server by their usual addresses.
Smart terminal
A browser terminal for company devices with plain-language commands, and no open SSH port.
Smart terminal
The office PC keeps its address
The member's laptop gets a real address in the office network. The office PC, the file share and the database answer at the addresses in the office documentation, so saved connections and bookmarks keep working.
There is no subnet router to set up and no route for an admin to approve before it works.

What changes for the IT team
The forwarded remote desktop port can go
Nothing in the office waits for the internet; the device there dials out. One less port facing the internet.
Machines with nobody there
The unattended client runs headless with no admin rights and keeps its network reachable, also after a power cut and with nobody logged in.
Servers & always-onA code for the IT partner
A Beam-in code reaches exactly what you choose in one network: the whole network, one device, or one port on a device - owned by the first device that redeems it. Several networks? Use one code per network - side by side in the app. Pause it or revoke it; a revoked code is refused at once.
Beam inRoles decide what is reachable
READ users see only the devices assigned to them; the role decides which office devices a member can reach.
A second factor per connection
With 2FA on connect, a stolen password alone does not open a connection to a company device.
Every connection recorded
Who, which device, when, from where, with or without a second factor - in a tamper-evident audit log.
2FA on connect comes with the Security package, roles with the Management package; the audit log comes with every company plan.

Classic remote access and Awacino
| Exposed RDP / remote-control tool | Awacino | |
|---|---|---|
| Facing the internet | A forwarded RDP or VNC port, or the tool's agent | Nothing; the device in the network dials out |
| On the target machine | Its remote desktop open to the world, or the tool's agent on every machine | Its built-in RDP or VNC; Awacino on one device in the network |
| Setup and upkeep | An agent on every computer, licences per seat / channel - or a forwarded port per machine to watch | One app or one small client per network; each device signs in with the user's account or a Beam-in code; nothing to configure on the router or per device |
| The client | Any RDP client, or the tool's own app | The RDP, VNC and SSH clients staff already use |
| What is reachable | One screen at a time | The whole network, one device or one port - one code per network, several codes side by side - chosen per code and per role |
| Check per connection | A password at the remote desktop, or the tool's login | Company sign-in, role and optional 2FA on connect, before every connection |
| Outside help | A shared password or an extra account | A Beam-in code, switched off when the job is done |
| Record | Logs on each machine | One audit log for every connection |
| Licensing | Often per user or technician | Per user; only Beam-in devices count, not the devices you reach through them |

Questions IT teams ask
Do we need remote-control software on the target machine?
No. The target needs its own remote desktop switched on, RDP or VNC. Awacino runs on one device in that network - the PC itself or another one that stays on.
Can an IT partner reach only one machine?
Yes. When you create a Beam-in code you choose what it may reach. A Beam-in code reaches exactly what you choose in one network: the whole network, one device, or one port on a device. Several networks? Use one code per network - side by side in the app. Pause it for the weekend or revoke it for good.
Does the remote screen pass through Awacino's servers?
No. Screens, files and commands go device to device, end-to-end encrypted. Our servers carry sign-in and the introduction of the two devices.
Is the server reachable after a restart?
The unattended client keeps a server's network reachable, also after a power cut and with nobody logged in.
Open the office PC in your own client
Install Awacino on one device in the office network, beam out from a laptop and open your usual remote desktop client. Or let us show you first.