local.link

Philosophy

In 1980, computers were for people who understood every part of the hardware and software; Apple packaged them so anyone could get started. Running your own infrastructure today is the same: so fragmented that a typical use means learning a dozen tools and gluing them together. Local Link is the package: your agent, on any harness, any model and any machine.

Local first, cloud second

Your computer is the data center. Your AI, your files and your models run there. The cloud is the fallback, for when your computer is off or isn't enough, never the default: your files go to your clouds as copies you can check, and your agent runs on your computer, not ours.

One console

lnk is the console to that data center. You learn one tool, with a few commands for each part, instead of the dozen tools underneath. Every command has the same shape, lnk <part> <command>, whether you're starting your AI, backing up a folder, serving a model or opening a tunnel.

Swappable engines

Everything under the console is an existing product that Local Link runs for you: OpenClaw and Hermes for your agent, rclone and your clouds for your files, Ollama and the other runtimes for your models. Each can be swapped without learning its replacement. lnk agent use hermes changes the program that is your agent, and your model, your files and your phone come along.

So "that already exists" is never a reason not to include something. The product that exists is the engine; not having to learn it, and being able to swap it, is the point.

Invent little

Local Link builds only the small pieces where the engines don't fit together, never a rebuild of an engine:

Safe by default, the whole engine underneath

Each part shows the few commands you need, and they're safe by default: your agent starts sandboxed, a tunnel asks who may reach it, push never deletes. The full engine stays one command away for whoever wants it: lnk bucket rclone is all of rclone. Local Link is never less than what it runs.

Yours

Your data center is yours. Your cloud keys stay on your computer, your files go only to the clouds you connect, and Local Link's server logs nothing about the requests to your tunnels.