Your Files. Your Team. Nobody Else.

Run Nextcloud, Gitea, Immich, Vaultwarden, Paperless-ngx, or another self-hosted collaboration service on a computer you control — and let your team access it securely from anywhere.

⬇ Download Free

🛡 Privacy — End-to-end encrypted. No MTCode infrastructure in your data path.

⚡ Simplicity — No public IP, domain, VPN, or port forwarding.

🚀 Performance — Direct peer-to-peer data path, with no relay hop.

The Problem

Small teams often want the control of self-hosting: client documents, code repositories, photos, passwords, notes, invoices, and internal tools can stay in infrastructure the team controls. But making those services reachable from outside the office is where things become complicated.

A VPS and reverse proxy require system administration. Cloudflare Tunnel and similar services route traffic through third-party infrastructure. Mesh VPNs connect whole devices and require careful access-control design. Port forwarding exposes a public entry point and may not even be possible in offices, campus networks, or shared spaces.

MTCode DirectLink is designed for this middle ground: access to selected services, from anywhere, without exposing the whole computer or putting a relay in the application data path.

What MTCode Does

📁

Drop-in for self-hosted apps

Most collaboration tools listen on a TCP port: Nextcloud, Gitea, Forgejo, Immich, Vaultwarden, Paperless-ngx, OnlyOffice, Penpot, and more. Register that port with MTCode Server — no app modification required.

🎯

Service-level access

Invite users to specific services rather than joining every device into a shared private network. Users access what you publish, not the whole computer.

🌐

One app for all shared services

MTCode Portal shows all services a user is authorized to access, even when they come from different administrators or different host computers.

How It Works in This Scenario

Install your self-hosted app on a computer in your office, studio, clinic, lab, or home.
Install MTCode Server and register the app’s local port.
Invite team members who should have access.
Each user installs MTCode Portal, signs in, and sees the shared service automatically.
Portal maps the remote app to a local address, so users can open it in a browser or compatible client.

Why This Matters

Data control: documents, repositories, and media stay on systems you operate.
No public service endpoint: your app remains inaccessible from the public internet.
No relay bandwidth bill: MTCode coordinates connection setup, but application data is not relayed through MTCode infrastructure.
Simpler access management: invite users by account and revoke access without reconfiguring routers or VPNs.