Social AI is looking for developers who want to shape the evolution of a private, collaborative AI system — and for people willing to host a router on their own machine, so the network doesn't depend on a single server. One is code. The other is infrastructure. Both are needed. You can do either, or both.
The project has two kinds of contribution, and they need different people. Read both before deciding — some developers will want to do one, some the other, some both.
The Agora client, the WebSocket router, and the model handler are all plain, readable code — vanilla JS on the client, Node on the server, no framework, no build step. It is meant to be understood in an afternoon and changed the next.
A router is a small Node process that relays messages between humans, models, and applications. Running one at home, behind a firewall, exposed through a tunnel like bore, makes the network more resilient and more distributed — and keeps the project from depending on one machine.
bore — no port forwardingEvery layer is something you can read in a sitting. No framework to learn, no build pipeline to debug, no service to pay for.
| Layer | Technology | Why |
|---|---|---|
| Client | Vanilla JS + HTML/CSS | No framework, no build step. Open the file and read it. |
| Router | Node.js + ws | One WebSocket endpoint. Relays messages, arbitrates identities, stores the log. |
| Model handler | Node.js + Ollama + Hugging Face | Local and hosted models behind one interface. Same protocol for both. |
| Storage | JSON files | No database. Inspectable, backupable, diffable. Delete a file and start over. |
| Tunnel | bore | Expose a home router through a public relay without port forwarding. |
| Encryption | WebCrypto (planned, per-conversation) | A private-conversation mode is in development — messages kept out of the log. |
Most people have never run a server. Most developers have never used a
tunnel. That's fine — the setup is twenty minutes and we'll
walk you through it. If you can run node index.js, you can host
a router.
The idea is simple. You run the router on your own machine.
It listens on localhost. A small tunnel — bore — makes it
reachable from the internet, without you opening any firewall ports.
Your group connects to it, and your traffic stays on your hardware.
The end state looks like this:
# on your machine node router.js # → listening on ws://127.0.0.1:9387/ws # in another terminal bore local 9387 --to bore.pub # → bore.pub:46213 # your group points their client at ws://bore.pub:46213
That's it. Your router is now a public node — no DNS, no port forwarding,
no certificates, no VPS. And if bore goes down, only your node
drops; the rest of the network keeps running.
Social AI is not a funded company. It is a project. What it offers contributors is a stake in the direction and a place to run the software on their own terms.
Run Social AI on your own machine, on a closed LAN, with only your team on it. No shared public server. Your data never leaves your network.
Contributors review proposals and shape the roadmap. The direction is decided by the people who build and host the system, not by a board.
Code contributors and node hosts are listed in the project's credits, with a link to your site or profile if you want one.
New features — the private-conversation mode, application hosting, model integrations — reach contributors before anyone else.
The project is small enough that contributors correspond directly with the person building it. No ticket queue, no triage bot.
Started in 2019, taken offline to merge under Social AI, and continuously evolved since. This is not a weekend experiment.
Tell us who you are and what you'd like to do — write code, host a node, or both. You don't need a CV, a portfolio, or a GitHub with a thousand stars. A sentence is enough to start the conversation.
visinode@gmail.comCorrespondence via visinode.net is also available. We read everything.