Uplink

Uplink is a command line tool for sharing a local web app, deploying it, and attaching a domain without leaving the terminal. It packages those jobs into one npm command so a developer or coding agent can move from a service running on localhost to something another person can open. There is no dashboard to navigate and no browser handoff in the main workflow. That makes it especially relevant when an agent is doing the work, since the same shell that starts an app can also expose it, inspect it, and manage where it lives. It can be installed globally through npm or run directly with npx, so trying the command doesn't require adding a project dependency.

The first part of the product is a public HTTPS tunnel. Point Uplink at any local port and it returns a temporary address under x.uplink.spot. Guest access is created automatically, so a quick preview doesn't require an account or an authentication detour. A guest can keep one tunnel active for 24 hours, which is enough for a review link, a webhook test, or a short demo. Once the tunnel exists, the CLI can list it, report statistics, stop it, or manage an alias. That also makes it possible to check the state of a tunnel before an automated test or share its address with another step in a development workflow. The useful idea isn't just tunneling by itself. It's that every step can be expressed as a stable command that another program can call and understand.

Uplink also covers lightweight hosting. It can set up and deploy Next.js, Vite, and static projects, then list an app, inspect its status and logs, or remove it from the same interface. Setup accepts the project path and an application name, which makes the action explicit in a scripted run. A developer doesn't have to switch from a local sharing tool to a separate deployment panel when a prototype is ready to persist. Email verification unlocks those hosted features while preserving a tunnel created as a guest. The result is a fairly direct path from local experiment to deployed application, with fewer context changes during a coding session.

Domain handling is the other substantial piece. Uplink provides one inventory for domains spread across GoDaddy, Cloudflare, Hostinger, Namecheap, DreamHost, and cPanel based hosts. The cPanel route covers shared hosting services that expose compatible access, so the domain view isn't limited to modern developer platforms. It can connect a supported provider, search or list domains, attach a hostname to a hosted app, and verify the DNS setup. That is useful for an agent that has finished building a site but would otherwise need a human to click through a registrar. It is also handy for developers whose domains are scattered among providers and who would rather work through one predictable interface.

The CLI has been shaped around automation rather than merely wrapping a human interface. JSON mode keeps structured results on standard output while sending logs and errors elsewhere. Stable exit codes distinguish usage, authentication, network, and server failures. Those details let an agent tell the difference between a malformed command, expired credentials, a connection problem, and a service error without scraping prose. Tokens can be read from standard input instead of appearing in the process arguments, and commands are available in noninteractive forms. Humans still get an interactive menu, but agents using Cursor, Claude Code, Codex, Windsurf, or another shell based workflow can operate it without pretending to be a browser user.

This focus makes Uplink a good fit for developers who regularly need to show work in progress, test callbacks against a local server, or let a coding agent ship a small web project. It is narrower than a full cloud platform and deliberately avoids a graphical control plane. That simplicity is part of the appeal when the task is straightforward, though teams that depend on visual project administration or broad framework support may still want their existing hosting service. The public repository and MIT licensed CLI also make the command contract visible, even though the hosted tunnel and deployment service remains the product behind it. Its small public community and focused framework list are worth weighing if it would become critical infrastructure.

Access is freemium. Guest and email login are free, while Pro is listed at $9 per month. Guest access includes one active tunnel for 24 hours, and aliases and custom domains depend on the account plan. The site doesn't present a large matrix of quotas, so buyers with heavier deployment or traffic needs should confirm the current limits before standardizing on it. Free access is still enough to see whether an agent can create and manage a tunnel reliably before a team pays for persistent naming. For quick agent driven previews and small app deployments, the low setup burden is the clearest reason to try it.