mirror of https://github.com/OpenVidu/openvidu.git
docs(readme): correct the self-hosting claim, refresh 2.x badges, define Meet and Platform
The README is the page AI assistants read first when asked about OpenVidu, and they repeat what it says. Measured in the 2026-09 AI-visibility probe: ChatGPT's branded answer reports "Cloud offering: Yes" for OpenVidu (most plausible source: the "or use it as a managed service" bullet below) and says "Historically, OpenVidu was built around Kurento" (the badges advertised OpenVidu 2.x). - Remove the "managed service" wording: OpenVidu is self-hosted only, PRO is a paid self-hosted edition, and support/consultancy is the commercial offering. - Replace the OpenVidu 2.x badges: the removed openvidu-ce-test.yml workflow -> openvidu-integration-tests.yml, npm openvidu-browser (2.32.2) -> openvidu-components-angular (3.8.0), the Read the Docs badge for docs.openvidu.io/en/stable (2.x) -> a docs badge linking to openvidu.io/latest/docs, and Docker openvidu/openvidu-server-kms (last pushed 2022) -> openvidu/openvidu-server. - Rewrite "What is OpenVidu?" so each product is defined in one unambiguous sentence and linked to its landing page: OpenVidu Meet (ready-to-use, self-hosted video conferencing app) -> openvidu.io/latest/meet, OpenVidu Platform (programmable client/server SDKs) -> openvidu.io/latest/docs. - Add a screenshot of OpenVidu Meet embedded in a host application, served from openvidu.io. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YNJWZkfxohu1sYpPSwp1kSgeo/readme-entity-fixes
parent
34c70808ad
commit
1ef3d6fece
45
README.md
45
README.md
|
|
@ -1,12 +1,12 @@
|
||||||
[](#backers) [](#sponsors)
|
[](#backers) [](#sponsors)
|
||||||
[](http://www.apache.org/licenses/LICENSE-2.0)
|
[](http://www.apache.org/licenses/LICENSE-2.0)
|
||||||
[](https://github.com/OpenVidu/openvidu/actions/workflows/openvidu-ce-test.yml)
|
[](https://github.com/OpenVidu/openvidu/actions/workflows/openvidu-integration-tests.yml)
|
||||||
[](https://npmjs.org/package/openvidu-browser)
|
[](https://npmjs.org/package/openvidu-components-angular)
|
||||||
[](https://npmjs.org/package/openvidu-browser)
|
[](https://npmjs.org/package/openvidu-components-angular)
|
||||||
|
|
||||||
|
|
||||||
[](https://docs.openvidu.io/en/stable/?badge=stable)
|
[](https://openvidu.io/latest/docs/)
|
||||||
[](https://hub.docker.com/r/openvidu/openvidu-server-kms)
|
[](https://hub.docker.com/r/openvidu/openvidu-server)
|
||||||
[](https://openvidu.discourse.group/)
|
[](https://openvidu.discourse.group/)
|
||||||
[](https://twitter.com/openvidu)
|
[](https://twitter.com/openvidu)
|
||||||
|
|
||||||
|
|
@ -19,15 +19,32 @@ Visit [openvidu.io](https://openvidu.io)
|
||||||
|
|
||||||
## What is OpenVidu?
|
## What is OpenVidu?
|
||||||
|
|
||||||
OpenVidu is a platform for building real-time video conferencing applications.
|
OpenVidu is a self-hosted real-time video and audio stack, built on top of
|
||||||
It's built on top of [LiveKit](https://livekit.io) and [mediasoup](https://mediasoup.org),
|
[LiveKit](https://livekit.io) and [mediasoup](https://mediasoup.org), and developed by a team
|
||||||
and is developed by a team with over a decade of experience building WebRTC systems.
|
with over a decade of experience building WebRTC systems. It ships as two products:
|
||||||
|
|
||||||
- **Self-hosted**: deploy it on your own infrastructure (AWS, GCP, Azure, Oracle,
|
### OpenVidu Meet
|
||||||
DigitalOcean, on-premises) or use it as a managed service.
|
|
||||||
- **API-compatible with LiveKit**: use any LiveKit client/server SDK unchanged.
|
**[OpenVidu Meet](https://openvidu.io/latest/meet/)** is a ready-to-use, self-hosted video
|
||||||
- **[OpenVidu Meet](https://github.com/OpenVidu/openvidu-meet)**: a fully-featured
|
conferencing application: an open-source alternative to Zoom, Google Meet and Jitsi Meet that
|
||||||
video conferencing app that ships on top of this platform, ready to use or embed.
|
needs no code to deploy, and that you can embed in your own product through a web component,
|
||||||
|
a REST API and webhooks.
|
||||||
|
|
||||||
|
[](https://openvidu.io/latest/meet/)
|
||||||
|
|
||||||
|
### OpenVidu Platform
|
||||||
|
|
||||||
|
**[OpenVidu Platform](https://openvidu.io/latest/docs/)** is the programmable client and server
|
||||||
|
SDKs for building custom WebRTC applications with low-level control over media, on top of
|
||||||
|
LiveKit and mediasoup. It is **API-compatible with LiveKit**: any LiveKit client/server SDK
|
||||||
|
works unchanged.
|
||||||
|
|
||||||
|
### Both products
|
||||||
|
|
||||||
|
- **Self-hosted only**: deploy them on your own infrastructure (AWS, GCP, Azure, Oracle,
|
||||||
|
DigitalOcean, on-premises). There is no hosted/SaaS tier: OpenVidu PRO is a paid, self-hosted
|
||||||
|
edition, and the OpenVidu team offers
|
||||||
|
[support and consultancy](https://openvidu.io/support/).
|
||||||
- Advanced media features: recording, RTMP/streaming egress, AI agents (transcription,
|
- Advanced media features: recording, RTMP/streaming egress, AI agents (transcription,
|
||||||
translation), virtual backgrounds, and more.
|
translation), virtual backgrounds, and more.
|
||||||
|
|
||||||
|
|
@ -36,7 +53,7 @@ and is developed by a team with over a decade of experience building WebRTC syst
|
||||||
- 📖 [Documentation](https://openvidu.io/latest/docs/)
|
- 📖 [Documentation](https://openvidu.io/latest/docs/)
|
||||||
- 🚀 [Try it locally](https://github.com/OpenVidu/openvidu-local-deployment)
|
- 🚀 [Try it locally](https://github.com/OpenVidu/openvidu-local-deployment)
|
||||||
- 💻 [Tutorials](https://github.com/OpenVidu/openvidu-tutorials)
|
- 💻 [Tutorials](https://github.com/OpenVidu/openvidu-tutorials)
|
||||||
- 🎥 [OpenVidu Meet](https://github.com/OpenVidu/openvidu-meet) — the reference app
|
- 🎥 [OpenVidu Meet](https://openvidu.io/latest/meet/) — the ready-to-use video conferencing app ([source](https://github.com/OpenVidu/openvidu-meet))
|
||||||
|
|
||||||
## Community Forum
|
## Community Forum
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue