Lanyard is a Mac menu-bar app that connects development ports between Macs on the same network. Rather than sending a database URL or setting up a tunnel, a teammate shares a port on their Mac and it appears to you as a localhost address: if Ada shares Postgres, you connect to localhost:5432 exactly as if the database were running on your own machine. The app is built for developers working together on the same local network who need to use each other's databases, caches, queues, API servers and web dev servers without deploying anything or exposing services to the internet. Lanyard is free, requires macOS 15 or later, and is available on the Mac App Store as well as a direct download (version 2.1).
Development services live on the Mac that runs them. A Postgres database, a Redis cache, a message queue or a dev server is normally reachable only from that machine, so a teammate who needs your database has to be handed a connection string, a dump, a deployed staging environment, or a tunnel that pushes the service beyond the local network. Lanyard's premise is that a teammate's dev stack should simply appear on your localhost. Two Macs on the same network pair once, and from then on a shared port behaves like a local address that can be pasted into a client, a browser or a .env file. The app states plainly that it works on your local network or VPN and is not an internet tunnel, and that shared ports are reachable on localhost only and never re-exposed.
Getting started takes three steps. Open "Pair a Mac" on both machines: each shows a 6-digit code, and if the codes match you confirm on both. Then share a port by picking Postgres, Redis, a dev server, or by typing any TCP port; a share can be paused with one click. Finally, connect as usual: on the other Mac the shared port appears as a localhost address, and you click to copy it into your client or .env file. Pairing is done once, after which the workflow is simply localhost.
Instead of sharing one port at a time, Lanyard can share a whole project. You can put a project's database, cache and API into an environment and pause or resume them together, and the other Mac sees them under the same heading. Several ports can be selected at once, or you can import a compose.yaml, docker-compose.yml or lanyard.yml and share the ports it publishes as one environment. Ports that cannot work through Lanyard, such as UDP ports or ports open only inside a container, are listed with the reason so you know why they are excluded.
Lanyard recognises 31 common services by name and shares each on its usual port with one tap, showing the ones already running on your Mac first and telling the other side what it found, such as "Postgres 16.4" or "RabbitMQ 3.13". Anything else that speaks TCP takes a name and a port number. You can add hints to a shared port — the database name, the user, and a note like "ask me for the password" — so the other Mac can copy a full connection string such as postgresql://ada@localhost:5432/shop, copy a .env line, or open the port in your database client or browser; hints are never for passwords. For Kafka, Cassandra and Pulsar, which send clients to the address the server advertises, Lanyard tells you what to set when you share one.
Lanyard also plugs into the rest of the Mac. Shortcuts and Siri can copy a port's address, get its connection string, open it, or turn a share, an environment or all sharing on or off. Spotlight lets you search for a port another Mac shares with you by its name or the Mac's name and open it in Lanyard, with the index staying on your Mac. lanyard:// links can copy, open and pause — for example lanyard://copy/PostgreSQL copies localhost:5432 — and never turn sharing on, because any web page can open one. Control Center (macOS 26) can host Lanyard Sharing in the menu bar so you can pause or resume everything without opening the panel. On macOS 26 with Apple Intelligence, "Explain this problem" uses only the on-device model to say what a port that isn't answering likely means and what to check, sending nothing anywhere. Notifications can tell you when a Mac first uses one of your ports, when a port you were using stops, and when a Mac comes back, and each can be turned off.
Sharing is restricted by design. Each Mac has its own key, and pairing pins the other Mac's key after you compare codes on both screens, so nobody can sit in the middle. You decide who gets what: a port can be limited to some paired Macs, or shared for an hour or until midnight, and you can see who is connected and disconnect them. A log on your Mac shows which Mac used which port, and sharing can pause by itself when you are off your trusted Wi-Fi networks. Everything travels over TLS with keys only those two Macs hold, and each connection gets its own short-lived key, so traffic recorded today stays unreadable even if a Mac's key is stolen later; unpairing a Mac disconnects it immediately. Other devices can see that a Mac runs Lanyard, but not which ports you share and they cannot reach them. There is no account, no relay and no server of Lanyard's own; the direct download asks the site once a day whether a newer version is out, which can be turned off in Settings.
Overall, Lanyard's approach is peer-to-peer on the local network: two paired Macs hold their own keys, ports are mapped to localhost addresses, and the underlying service does not need to listen on all interfaces because Lanyard connects to it on the sharing Mac's own localhost, so services bound to 127.0.0.1 work and never need to be opened to the network. If the port you need is already used on your Mac, Lanyard picks the next sensible one (for example localhost:25432), tells you, and keeps it the same next time; you can choose your own with "Change local port…" in the port's menu. If the Macs cannot see each other, you can pair by address and type the address shown in the other Mac's pairing window, with TCP ports 46310 and 46311 open on any firewall.
The benefit is that a shared dev dependency feels local. You paste a localhost address into your client, browser or .env file and keep working, while the owner of the service controls which Macs may use each port and for how long. Nothing has to be deployed, no account is created, and no third-party server sits in the path. Ports appear and pause on demand, environments let a database, cache and API move together, and connection strings or .env lines can be copied without retyping credentials — while the content notes that hints are never for passwords, since Lanyard protects traffic in transit, not the service itself.
Concrete workflows follow directly from the panel: a frontend developer points their app at a teammate's API or dev server that appears on localhost; a developer testing migrations connects to a colleague's Postgres on localhost:5432; a team imports a docker-compose.yml and shares the database on 5432 and the API on 8080 together as an environment named for the project; someone sharing Kafka, Cassandra or Pulsar reads the advertised-address guidance before handing out the port; and when a network blocks device discovery, the pair-by-address flow in the pairing window gets the two Macs connected anyway.
Lanyard is aimed at Mac-based developers, small teams and teammates who work on the same local network or VPN, including those on guest or office networks that stop devices from seeing each other. It requires macOS 15 or later and runs as a menu-bar app; version 2.1 connects to Macs still on 2.0, though both should be updated to get forward secrecy, and Settings marks Macs running the older version. It replaces the older Dev Tunnel Share, so both Macs need the new version. Pricing is free.
The app is candid about its limits: it is not an internet tunnel and works on your local network or VPN; a shared port is open to every paired Mac until you limit it, so you should pair only with Macs you trust; trusted networks go by the Wi-Fi name alone and are not a security boundary; and a Mac still on Lanyard 2.0 gets no forward secrecy. What it can share is anything that speaks TCP, from databases and caches to API and web dev servers.
In short, Lanyard turns "a teammate's dev stack" into localhost addresses on your own Mac: paired with a 6-digit code, encrypted between the two machines, scoped by per-port access rules and time limits, and kept entirely on your local network with no account and no server.