Machine names
Each machine is reachable by its name under mesh.cryptomeshvpn.com, for example pikvm.mesh.cryptomeshvpn.com. Rename a machine from the Machines page.
Every phone, computer and gateway on your private network.
Connect in the CryptoMesh VPN app on your phone, or add a PiKVM or Linux computer with a join key.
| Machine | Addresses | Version | Tags | Last seen | Actions |
|---|
Reach chosen web apps and domains through connector devices in your organization.
Stable names for what your machines run. Add hosts, approve them, and reach each service by name from any device.
Services on your devices that anyone on the internet can open.
Devices you share with other CryptoMesh VPN accounts, and devices they share with you.
Names and name lookups for the devices on your private network.
Each machine is reachable by its name under mesh.cryptomeshvpn.com, for example pikvm.mesh.cryptomeshvpn.com. Rename a machine from the Machines page.
Members, roles and invitations of a shared CryptoMesh VPN directory. Roles are decided by the server; this page shows the latest state it knows.
A directory of accounts with fixed roles: owner, admin, network admin, member and auditor. Owners manage everything, admins manage members, auditors and network admins, network admins edit the network policy and devices, auditors read policy and audit logs, members see the organization, their own role and their own devices.
Members join from the CryptoMesh VPN app: Network tab, Switch network. A new device is listed under Devices as pending until a network admin approves it. Rejecting or removing a device, or suspending or removing a member, ends that access on the next control sweep (about a minute).
Organizations do not grant Cloud access or move subscriptions or personal nodes.
An invitation is issued to a principal ID and comes with a secret that is shown once. When invitation email is set up, CryptoMesh VPN can email the link and secret to an address you enter; otherwise copy the link and share it yourself. Only the recipient's signed-in account can redeem it, and only once.
Who can reach what on your networks.
What the policy must allow and must deny. Every test runs before a save; a failing test blocks it.
Groups, hosts, IP sets and tags that the access rules refer to.
Built-in selectors every policy can use. They follow membership and roles automatically and cannot be edited.
The organization policy as HuJSON. Preview checks it and runs the tests; Save makes it the current version.
Every change to your networks: who made it, when, to what, and whether it worked.
Opt-in connection summaries for an organization's devices, their retention, and where they stream.
Your account, this network's identifiers, allowances and feature previews.
How people sign in to your organization, how they join, and how long a console session lasts.
Device approval, network lock, key expiry and update preferences for your devices.
Whether the console editor may change the organization policy, and which external client maintains it.
Credentials that let workloads and apps act for your organization, never beyond the role that granted them.
Check the app and what it asks for before you allow it. Only allow apps you trust and expected to see.
Signed JSON events for an organization, delivered to your HTTPS endpoints.
Where CryptoMesh VPN sends notices about your account, configuration problems and security issues.
Your personal plan, and an organization's plan, seats and invoices (owners and billing managers).
Join keys for devices that cannot sign in, and credentials for automation and CI.
Administrator view across every account.
| Machine | Account | Addresses | Home network | Last seen |
|---|
Run this on the device within 10 minutes, then paste the one-time key when it asks. The key works once.
One-time key
Install CryptoMesh VPN, sign in with this account, then tap Connect under CryptoMesh VPN network.
Redirecting to sign-in…