
How a company connection works
Checked on our server, then a direct encrypted path between the devices.
Powered by
- Cloudflare
- PlanetScale
- AWS
- Stripe
- Apple
- Flutter
- GitHub
- Ubuntu
- Docker
- Kubernetes
- Helm
- HashiCorp Terraform
- PostgreSQL
- Raspberry Pi
- bunny.net
- Anthropic
- OpenRouter
- ElevenLabs

Three steps, every time
Sign in. The member signs in with the company account: with your identity provider when company sign-in is on, otherwise with password and second factor.
Policy check. 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.
Direct path. Both devices dial out; our servers introduce them and step aside. The data flows directly, end-to-end encrypted, also behind CGNAT and on mobile networks.

And what they do not
What we process
Accounts, device names and addresses, who connected to which device and when (the audit log), and the signalling that introduces two devices.
What does not pass through our servers
Screens, files, databases, commands and anything else that flows between your devices. It goes device to device, encrypted end to end.

The parts
SituIP
A real address in the target network, so existing tools work unchanged.
Read moreAwacino API
Members, Beam-in devices, Beam-in codes, access and the audit log from your own tools - and with Terraform.
Read moreIdentity & audit
Company sign-in with your identity provider, a second factor per connection, the company key and the audit log.
Read moreAutomate
Projects, schedules and AI-assisted automation across company devices.
Read moreSmart terminal
A browser terminal with plain-language commands, no open SSH port.
Read more
Roll it out
Read the full security page
Architecture, data protection, sub-processors and how to report a vulnerability.