
Network access without a gateway
Devices dial out and connect directly, so nothing in the company network waits for the internet.

The VPN gateway is the exposed part
Remote access to a company network usually means something inside it that accepts connections from the internet.
A gateway to run
A VPN appliance or server sits at the edge of the company network. It has to be bought, patched, renewed and kept reachable from the internet.
An inbound port
Whatever waits for connections from outside can be found and tried. The gateway that protects the network becomes the target.
Configuration per client
Profiles, routes and subnets are handed out to every user, and a second address plan has to be kept in line with the real network.

Checked, introduced, then direct
- 1
Both ends dial out
A device in the company network - a PC, a Mac or a server with the unattended client - and the member's laptop or phone both connect outbound to Awacino. Nothing is opened on the firewall.
- 2
Policy check
The member signs in with the company account. Before the connection starts, our server checks the member's role, the devices assigned to them and, with 2FA on connect, a fresh second factor. A failed check refuses the connection and is written to the audit log.
- 3
Direct, end-to-end encrypted
Our servers introduce the two devices and step aside. The data flows directly between them, end-to-end encrypted, also behind CGNAT and on mobile networks. It does not pass through our servers.

A real address, not a parallel network
When a member beams out, their device gets a SituIP: a real address in the target network, often leased by that network's own router. A laptop in a hotel gets 10.20.0.47 in the office network 10.20.0.0/24; the ERP at 10.20.0.10 and the file share at 10.20.0.20 keep their addresses.
If the connecting device's own network uses the same range, it gets a private 100.64.x.x address instead.
- Visible in the router's lease table like any other client
- No subnet router and no route to approve
- Documentation, bookmarks and connection strings stay valid

Every connection is checked
Company sign-in
Microsoft Entra ID, Google Workspace, Okta or any OIDC or SAML 2.0 provider, with SCIM provisioning.
Company sign-inRoles
Five roles, from MAIN-ADMIN to READ; READ users see only the devices assigned to them.
Company featuresTwo-step confirmation on connect
A second factor before a connection to a company device starts, once a day per device or every time.
2FA on connectAudit log
Sign-ins, admin actions and every connection, each entry linked to the one before it in a hash chain.
Company key & auditCompany sign-in and SCIM come with the Identity package, 2FA on connect with the Security package, roles with the Management package; the audit log comes with every company plan.

What changes for the IT team
No inbound ports
Devices only dial out. The company network has nothing that answers a scanner on the internet.
No gateway to patch
No VPN appliance to buy, patch, renew and keep reachable. App updates roll out with your MDM.
No client configuration
Staff install the app and sign in with the company account. There are no profiles, routes or subnets to hand out.
Access per device
Each device has its own identity and is registered to the company. A device that is removed no longer gets in.
Access per code
A Beam-in code reaches exactly what you choose in one network - the whole network, one device, or one port on a device - belongs to the first device that redeems it, and is refused at once when revoked. Several networks? Use one code per network - side by side in the app.
Beam inOffboarding in one step
Deactivate a user and their sessions end, live connections close and their key copy is deleted.

VPN gateway and Awacino
| VPN gateway | Awacino | |
|---|---|---|
| In the company network | A gateway or appliance that faces the internet | One device that is already there dials out |
| Inbound port | Yes, on the gateway | None |
| Data path | Through the gateway | Device to device, end-to-end encrypted; not through our servers |
| Addresses | A VPN address plan beside the real network | A SituIP in the network itself |
| Setup and upkeep | A gateway or appliance to patch and monitor; a VPN profile, routes and subnets set up on every client device, redone for every new device | 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 |
| Check per connection | At the gateway login | Role, assigned devices and optional 2FA on connect, before every connection |
| Outside help | A VPN account for the partner | A Beam-in code for exactly what you choose: the whole network, one device or one port - one code per network, several codes side by side; revocable |
| Licensing | Often per person | Per user; only Beam-in devices count, not the devices you reach through them |

Questions IT teams ask
Do we have to open a port on the firewall?
No. The device in the company network and the member's device both dial out; nothing in the company network is reachable from the internet.
Does our data pass through Awacino's servers?
No. Our servers carry sign-in and the introduction of two devices. Screens, files, databases and commands go device to device, end-to-end encrypted.
Do we install Awacino on every machine we want to reach?
No. Awacino runs on one device in the network, a PC, a Mac or a server with the unattended client. With a SituIP, the other machines answer by their usual addresses.
What do we pay for?
Users, Beam-in devices and active Beam-in codes. Beam-in devices count; the devices you reach through them (printers, NAS, PCs in that network) are not counted.
See it on your own network
Install it on one device in your office network and beam out from a staff laptop. For a guided start, book a demo.