OpenVibe.Services
You are looking at revision 2, not the published revision 3.
Imported, written with AI assistance. Imported from the OpenVibe repository README and STATUS files at the cited commits, summarised with AI assistance; originally by OpenVibers. Not yet reviewed by a person.
OpenVibe.Services is the developer platform of the OpenVibe network, serving https://openvibe.services on port 4930 (service id services). It is alpha. Its README describes it as "one console for projects and apps over OpenVibe.Network".
What it does
It shows and forwards what the signed-in person asks for, with that person's own OpenVibe.Network token: projects, members, apps, credentials, capability grants and quotas; a per-project usage page from Network's rollups; project export as JSON and a full archive as a zip; OAuth and webhook tools that speak signature v2 only; and Media and Events playgrounds. Its merged resource index reads each authority with its own token and merges the pages, naming any authority it could not read.
It also sends control requests to the service that holds a resource, which decides:
- project resources: an admin can suspend, resume, stop or delete them (watches, event subscriptions, Actor tasks, Media objects, Space sites, Zone zones);
- a person's own resources, on "Your resources": they can stop or resume their robot, archive a chat room, suspend or resume a restream, and delete a paste.
Every request is idempotent and audited. An agent's sensitive request waits for its owner's approval. Secrets are shown once and never stored. Everything is server-rendered and usable without JavaScript.
What it does not do yet
The developer portal moved here from OpenVibe.Codes on 2026-10-08, when its production data was nil, so nothing was copied. The playgrounds have never been used on production; the one end-to-end run used curl and is not a committed, repeatable check. Not built yet: Billing sandbox, Chat bot and Realtime playgrounds, a CLI and scaffolding, templates, and a third-party consent screen. Governance material is in drafts pending owner review.
How it fits the network
Services depends on OpenVibe.Network for identity, projects and the registry; on OpenVibe.Events for the outbox relay and the Events playground; and on OpenVibe.Media for uploads and the archive. It never copies another authority's data, and it never fetches a URL a developer types.
Runtime and status
Node 22 and Express 4, PostgreSQL 18 (ov_services) and Valkey 9, unit openvibe-services.service on 127.0.0.1:4930. STATUS.json records the stage as "alpha" and the service deployed. License: AGPL-3.0.
Sources
- OpenVibe.Services README (commit 9bf5051), retrieved
The developer platform of the OpenVibe network: one console for projects and apps over OpenVibe.Network
- OpenVibe.Services STATUS.json (commit 9bf5051), retrieved
serving https://openvibe.services (the Sites placeholder left on 2026-10-08).
Inspect these sources (retrieval times, where each was first cited, what changed between revisions)