Awacino ZeroTrust Company Network

Customer servers without an open remote login port

Every server dials out; your customer reaches it by code. Exposed SSH (remote login) and RDP (remote desktop) ports disappear from the internet.

The situation

A remote login port open on every server

Hosting and cloud providers - and the small companies and developers who rent a server and run it themselves.

Brute force, all day

Every virtual server ships with SSH or RDP open to the internet: constant login attempts, fail2ban, key hygiene, support tickets after break-ins.

Jump hosts and VPNs per customer

Bastion hosts and VPN gateways cost money and setup - and still face the internet.

Shared keys

The customer's team and their freelancers share keys or passwords.

How it works

The server dials out, the customer beams in

  1. 1

    The server runs Awacino

    The Linux installer, the Docker image (linux/amd64, linux/arm64) or, on Kubernetes, the Helm chart (each node a Beam-in device), registered with a one-time setup code; it only dials out.

  2. 2

    The customer gets a code

    A Beam-in code per person and server - or member accounts for a company. SSH, remote desktop, the database or the web admin by its address, end-to-end encrypted - or the smart terminal in the browser with no open port 22.

  3. 3

    Revoke in one step

    The code is owned by the first device that redeems it; switching it off refuses the next connection.

hosted server remote login no port 22 open database by its address web admin by its address smart terminal in the browser Beam-in code your customer Beam in direct · end-to-end encrypted · no inbound port
What you gain

Less attack surface for both sides

The client, the codes and the terminal.

Dials out only

Nothing on the server is reachable from the internet.

Own identity per server

Each device is registered with its own identity.

No open remote login port

The smart terminal and the customer's own SSH client go over the direct connection.

Admin rights when allowed

Per server you decide whether the terminal may switch to administrator access.

Per person, per server

A Beam-in code each - counted while active, revoked in one step.

An EU company

Awacino is made by a company in Germany; every access is in the audit log.

Your network traffic goes directly between your devices - never through our servers.

Automation

Provisioning at scale

From your own tools: the Awacino API and the Terraform provider.

Cloud-init line

Install the client with a one-time setup code when the server is created.

The Awacino API

With the connection API: users, servers, setup codes and invitations - and Beam-in codes and access grants per customer, with an end date, plus the live connections of every server.

Terraform provider

A new server and its customer's Beam-in code in the same terraform apply - members, codes and access as code.

Partner console

A tenant per customer, created by your platform.

Comparison

Awacino and the usual ways in

The direct path, with a code per customer and server.

AwacinoBastion / jump hostCloud provider VPN (per network)TailscaleTeleportCloudflare Tunnel
Admin port on the internetNoneThe bastion's SSHThe VPN gateway's portNoneThe proxy (one, hardened)None
Agent on the serverUnattended client / DockerNone (SSH)NonetailscaledTeleport agent (reverse tunnel to the proxy)cloudflared
Data pathDirect between customer and server, never via our serversVia the bastionVia the gatewayDirect when possible, else relaysVia the Teleport proxyVia Cloudflare
Per-person access, revocationBeam-in code per person and server, revoked at onceKeys on the bastionVPN usersAccess rules per user or tagShort-lived certificates, role-based accessAccess policies
Automation for a hosterCloud-init line, Awacino API and Terraform provider (with the connection API), partner console (a tenant per customer)ScriptsProvider APIAPI, auth keys, TerraformAPI, TerraformAPI, Terraform
Setup and upkeepOne app or one small client per network; each device signs in with the user's account or a Beam-in code; users and codes managed in one place; nothing to configure on the router or per deviceA hardened server to patch and monitor; SSH keys per personA VPN gateway per network to configure, plus a VPN profile on every client deviceA client on every device, plus a subnet router to set up for devices without the clientAn agent per server plus the proxy (self-hosted or cloud) to runcloudflared per network, plus hostnames and access policies in the dashboard

Competitor facts: vendor pages and Awacino market research, November 2026.

What we offer

What we offer server providers

Each server with Awacino is one Beam-in device. The packages add what a provider needs.

Awacino API · connections

Every new server gets access without an open port

Your platform creates a Beam-in code per customer and server - the whole network, one server or one port, with an end date - and revokes it in one call.

API Access · Terraform provider

Provisioning in your pipeline

Setup codes, members, Beam-in codes and access grants from your own tools or with the Terraform provider: one apply per new server.

Management

One user per customer and server

Each customer reaches only its own servers - access per member and server, with an end date.

Compliance

Every access logged for your customers' audits

A 12-month audit log with export and an auditor role: who reached which server, when and for how long.

Security

Two-step confirmation before every connection

An authenticator app or a passkey before a customer reaches a server.

Fleet

Fleet offer

Hundreds of servers, one contract: we make you an offer for your fleet.

Fleet offer - talk to us
Questions

Asked by hosters

Do we still need the remote login port open?

Not for the customer's access: the server dials out and the smart terminal or the customer's own SSH client goes over the direct encrypted connection. Your own rescue console stays.

Can we provision it automatically?

Yes - with the Awacino API and the Terraform provider: a setup code and a cloud-init line per server, Beam-in codes for your customers through the connection API, members and their access.

Does customer traffic pass Awacino?

No. Your network traffic goes directly between your devices - never through our servers.

What does it cost?

Fleet offer - talk to us: we make you an offer for your servers.

Close the remote login port for your customers

Tell us about your platform; we plan the rollout with you.