skip to content

Why this exists.

by Amir · 2026

I'm 21. I study electrical engineering at York University in Toronto. I run a small company called Zedsio. I trade markets with code I wrote. I babysit a fleet of 20 services on my own hardware because I didn't want to rent somebody else's opinion of a server.

I live in the terminal. Most days I close the browser before lunch and don't open it again until the next morning. That is not a personality trait. It is the only way the work gets done.

Somewhere between Termius asking me to log in to paste a command, and Warp streaming my keystrokes to a cloud I did not choose, and VS Code spawning three hundred megabytes of Electron to edit a .env file, I lost patience. Not dramatic patience. Boring, practical patience. The kind you lose when the tool you use a thousand times a day is slower than the task it exists to serve.

The word vev is Old Norse. It means web, as in a thing you weave. Not the web we have now — the one run by five companies and instrumented by all of them. The older one. The one where you made your own cloth because nobody else's fit.

So I wrote this. A terminal. An SSH client. An AI pair that uses the key I already paid for. A way to move a file to another one of my machines without uploading it to anyone. A dashboard for my fleet that I can read in a glance. One binary. Five megabytes. No account.

It is not a startup. It is a workshop. The Founding 500 are the people who buy the first run. After that, it grows or it doesn't, but either way it belongs to the people running it, because the keys are on your disk and the source is under the hood.

If you've been waiting for somebody to build a terminal that respects the graybeard tradition — local, fast, yours — and also knows what year it is — AI, fleet, P2P — this is that.

Try it. If it's not better than what you have open right now, uninstall it. It's 5MB. You'll live.

— Amir
Toronto, 2026
curl -fsSL vev.sh/install | sh