MTCode DirectLink uses a signaling-assisted peer-to-peer architecture. The platform coordinates authentication, authorization, service discovery, and connection setup, while application data flows directly between endpoints over an encrypted P2P channel.
The platform has three core components: a Platform Server hosted at MTCodeAI.com for authentication, server registration, authorization, and connection signaling; MTCode Server, which runs on the computer hosting your services; and MTCode Portal, which runs on each user’s computer and maps authorized remote services to local ports.
MTCode DirectLink — servers on your private network become accessible to invited users anywhere
Hosted at MTCodeAI.com. Handles administrator and user authentication, server registration and authorization, and connection signaling. It does not relay application data; its role is limited to coordinating connection setup so that a direct peer-to-peer channel can be established between MTCode Server and MTCode Portal.
Runs on the computer that hosts your services. It authenticates with the platform using the administrator account, registers selected local server ports, and establishes direct encrypted data channels with corresponding MTCode Portal instances. Learn more →
Runs on each user’s computer. It signs in with the user account, discovers authorized services, and maps each one to a local port so remote services appear as if they are running locally. Learn more →
When a user signs in to MTCode Portal, it retrieves the list of servers the user is authorized to access. When a connection is initiated, the platform coordinates setup through a signaling process, enabling MTCode Portal and the remote MTCode Server to establish a direct peer-to-peer channel — even when both are behind NAT routers with no public IP.
Once the connection is established, the platform is no longer part of the data path. Application data flows directly between the two endpoints and is end-to-end encrypted. MTCode does not process or store application-layer data.
This differs from reverse-proxy and tunneling services such as ngrok or Cloudflare Tunnel, which route traffic through an intermediate relay server. That extra hop can introduce latency and throughput limitations, and traffic becomes subject to the provider’s infrastructure and data policies.
It also differs from mesh VPNs such as Tailscale and ZeroTier. Mesh VPNs connect entire devices into a shared private network. Without careful access-control configuration, multiple services on each computer — such as SSH, databases, or administrative interfaces — may become reachable by other participants.
There is also a multi-owner access challenge. When a user needs to reach services managed by different people—such as colleagues, collaborators, or clients—each environment is typically administered independently. Access may require separate configuration, coordination, or identity management across multiple networks, with no unified interface.
With MTCode DirectLink, a user has one account and one application — MTCode Portal — to access all authorized services from multiple administrators simultaneously. Access is granted at the individual service level, rather than exposing entire computers or networks.
Follow our step-by-step guide to publish your first server or connect to a remote server in minutes. No credit card required.