Default-deny access rules
Grant users, groups or devices access to specific subnets and ports. Everything else is blocked, and an explain tool shows why.
Members sign in, register their device and reach only the private networks their group rules allow. Now in public beta.
Beta Public beta, open to everyone. Features and limits may change before general availability.
Capabilities
Each person reaches only the subnets and ports their group rules grant.
Grant users, groups or devices access to specific subnets and ports. Everything else is blocked, and an explain tool shows why.
Use a Yeap account, password, TOTP, passkey or your LDAP directory. Each device is registered to a member and admins can disable it.
Internal names resolve from your private zones or your own DNS servers. Public domains keep using the device's resolver.
A Connector in each site dials out, so no inbound ports are opened. Two Connectors for one subnet act as primary and standby.
Connect offices and data centres to each other, and let members' devices reach one another under the same rules.
Clients connect to the closest gateway and switch when it fails. Tunnels fall back from UDP to HTTPS on port 443 when UDP is blocked.
Admin changes and sign-ins are audited. Flow logs record each connection's user, device, destination and verdict, with CSV export.
Members can send internet traffic through our gateways: 10 GB per user each month, at a limited speed.
Pricing
Up to 50 users
50 users free, then per user
Only users beyond the free allowance are billed.
How it works
Open Yeap Access in the console. Your team gets its own address and admin console.
Run a Connector in each office or data centre and approve the subnets it announces.
Members install the client, enter your team address and sign in.
Specifications
| Status | Public beta |
|---|---|
| Clients | Android and Linux. Windows client in testing; iOS and macOS not supported yet. |
| Sign-in | Yeap account, password, TOTP, passkey, LDAP |
| Encryption | WireGuard Noise IK. Sign-in fields encrypted with HPKE. |
| Transport | UDP, with automatic fallback to QUIC and TLS on port 443 |
| Gateways | US West, Hong Kong, Tokyo and Europe; the nearest is chosen automatically |
| Addressing | 100.64.0.0/10 by default, IPv6 ULA, your own subnets |
| Overlapping subnets | Mapped (NAT) on the Connector |
| Public egress | Free, 10 GB per user per month, rate limited |
| Logs | Audit log, flow logs with CSV export |
| Administration | Web admin console at your team address, admin and read-only roles |
FAQ
Yes. It is in public beta and open to everyone: open Yeap Access in the console to create your team. Features and limits may still change during the beta.
A traditional VPN puts a device on the whole network. Yeap Access denies everything by default and only opens the subnets and ports each user, group or device is granted.
No. Connectors only make outbound connections.
Each team gets a number of users free. Only users beyond that are billed, per user per month. The plans above show the current price.
Android and Linux clients are available now. A Windows client is in testing, and iOS and macOS are not supported yet.
Yes. Free public egress gives each user 10 GB a month at a limited speed. In split mode, public traffic stays off the tunnel.