Share one port on your computer at its own address, like agents--you.openvibe.website. Only the people you pick can open it, signed in with OpenVibe. No router settings, no open ports, no app to install: one file and Node.
Download ov-connect.js once and run it with your share's key and port. It opens one outgoing connection to OpenVibe, so it works behind any router, at home or on a phone hotspot, and it reconnects by itself after sleep.
Sign in to start$ curl -fsSLO https://connect.openvibe.website/ov-connect.js $ node ov-connect.js --key ovc_… --port 8080 Connected. https://agents--you.openvibe.website → localhost:8080 GET / → 200 (14 ms)
Your agent portal, a dev server, a home dashboard: open its address on your phone over 5G. It is real HTTPS, so the microphone, the camera and WebSockets work. Live streams (server-sent events) stream.
Only you, or you and the people you name. Change it any time and everyone already in is asked again. Your app is told who each visitor is, so it can greet them by name.
The share page is also an API, with your OpenVibe token. Your app receives X-OpenVibe-User and X-OpenVibe-Subject on every request, and never the gate's own cookie.
curl -X POST https://connect.openvibe.website/api/v1/shares \
-H "Authorization: Bearer $OV_TOKEN" -H "Content-Type: application/json" \
-d '{"label":"agents","port":8790,"mode":"owner"}'curl https://connect.openvibe.website/api/v1/shares -H "Authorization: Bearer $OV_TOKEN"OV_CONNECT_KEY=ovc_… node ov-connect.js 8790Nothing but answer requests for your share on the one port you gave the client, on localhost. The client never opens a connection anywhere else, and you can read all of it: it is one file.
People you allow, after they sign in with OpenVibe: only you, or you and the people you name. "Anyone signed in" is open to OpenVibe staff until the abuse check is in. Changing who can open a share signs everyone out of it at once.
Not yet. A public address can be abused for phishing, so public shares come with the abuse check and openvibe.website's entry in the Public Suffix List. Until then every visitor signs in.
The request as the browser sent it, with Host set to localhost:<port>, the share's address in X-Forwarded-Host, the visitor's address in X-Forwarded-For, and who they are in X-OpenVibe-User and X-OpenVibe-Subject. Cookies your app sets stay on your share's address.
Five open shares per person, 64 requests at once per share, 1,200 requests a minute per share, 100 MB per request body, and 10 GB a day across your shares. Nothing is stored: requests pass through.
It is part of your OpenVibe account: the people you let in are OpenVibe people, no separate login, no install beyond one file. TCP and UDP shares (game servers), custom domains, a private mesh between your machines and durable webhooks are the next steps on the plan.
Connect is the "your machine" half of openvibe.website. The other half builds and hosts sites.