Wormkey.runBeta

Share your localhost in one command. No account. No dashboard. Just a link.

npm i -g wormkey

wormkey http 3000

Default: t.wormkey.run. Your app stays on your machine.

Quick start

1. Start your app (e.g. port 3000)
2. Run wormkey http 3000
3. Share the printed URL

Next.js / React

Add the overlay component to your layout for owner controls.

import { WormkeyOverlay } from "wormkey";

export default function Layout({ children }) {
  return (
    <>
      {children}
      <WormkeyOverlay slug="YOUR_SLUG" />
    </>
  );
}

Optional config

# optional overrides
WORMKEY_CONTROL_PLANE_URL=https://wormkey-control-plane.onrender.com
WORMKEY_EDGE_URL=wss://t.wormkey.run/tunnel

Owner overlay demo

See the control bar that tunnel owners get. Toggle to preview.

Owner overlay (script tag)

Or load the overlay script directly. Optional.

<script defer src="https://t.wormkey.run/.wormkey/overlay.js?slug=YOUR_SLUG"></script>

Why Wormkey

Share what you are building without opening your whole machine.

Wormkey only connects the public URL you create to the local port you choose. The tunnel disappears when it expires or you close it.

TLS at the edge

Visitors connect over HTTPS. Wormkey terminates TLS at the edge before forwarding traffic through your authenticated tunnel.

Outbound-only connection

The CLI opens the connection from your machine. You do not need to expose a router port or accept unsolicited inbound connections.

Expiry and access control

Sessions expire automatically. Owners can close tunnels remotely, restrict access, pause traffic, and use short-lived scoped tokens.

Limited local reach

Wormkey can reach the hostname and port you explicitly expose. It does not gain general access to your files, shell, other ports, or local network.

What Wormkey can see: HTTP requests and responses that pass through the tunnel, plus session metadata needed to route and control it. What it cannot see: unrelated files, terminal activity, source code, or services you did not expose.