openvidu.io valid
OpenVidu
Self-hosted video conferencing & custom WebRTC: deploy OpenVidu Meet in minutes or build with OpenVidu Platform SDKs.
- Authority
- 46 reach 5 · trust 5 · quality 21 · freshness 15
- Tier
- listed
- llms.txt
- https://openvidu.io/llms.txt
- Sections
- 24
- Links
- 227
- Size
- 59777 bytes
- Popularity rank
- #872877
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-25T18:05:54.237Z
- Last checked
- 2026-10-26T05:22:35.610Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T05:22:34.275Z. Cached copy · Source on openvidu.io
# OpenVidu
> Self-hosted video conferencing & custom WebRTC: deploy OpenVidu Meet in minutes or build with OpenVidu Platform SDKs.
OpenVidu is self-hosted: it runs on infrastructure you control. Two products share this documentation. OpenVidu Meet is a complete video conferencing application, deployed as it is or embedded in your own app; OpenVidu Platform is the LiveKit-compatible SDK layer you build your own real-time application on. The "Optional" section at the end holds legal and acknowledgment pages, and can be skipped when a shorter context is needed.
## Product and pricing
- [Self-hosted video conferencing & custom WebRTC](https://openvidu.io/index.md): Run video conferencing on your own servers. Deploy the ready-made OpenVidu Meet app, or build your own real-time video product with OpenVidu Platform.
- [OpenVidu Meet vs OpenVidu Platform](https://openvidu.io/openvidu-meet-vs-openvidu-platform/index.md): OpenVidu Meet is a finished video conferencing app you deploy; OpenVidu Platform is the SDK layer you build on. Compare both and pick one.
- [OpenVidu vs LiveKit: A Self-Hosted LiveKit Fork](https://openvidu.io/openvidu-vs-livekit/index.md): OpenVidu is a fork of LiveKit — 100% API-compatible, self-hosted only, with the mediasoup engine for 2x performance and Egress/Ingress bundled in.
- [OpenVidu vs mediasoup: Platform vs Raw SFU Library](https://openvidu.io/openvidu-vs-mediasoup/index.md): mediasoup is a low-level SFU library, not a platform. See exactly what OpenVidu already built on top of it — signaling, rooms, auth, recording, API.
- [OpenVidu vs Jitsi: Two Self-Hosted Platforms Compared](https://openvidu.io/openvidu-vs-jitsi/index.md): OpenVidu and Jitsi are both open-source, self-hosted video platforms. Compare architecture, recording, scaling, SDKs and pricing to pick the right one.
- [OpenVidu vs Janus: Platform vs Raw WebRTC Gateway](https://openvidu.io/openvidu-vs-janus/index.md): Janus is a general-purpose WebRTC gateway, not a platform. See exactly what it leaves for you to build — signaling, rooms, auth, recording, API.
- [Pricing: Free COMMUNITY & Pay-Per-Core PRO](https://openvidu.io/pricing/index.md): OpenVidu pricing: COMMUNITY edition free forever, PRO from $0.0006 per core per minute. Transparent, pay only for what you use.
- [OpenVidu support and consultancy](https://openvidu.io/support/index.md): Commercial support and consultancy from the OpenVidu team, plus the community channels where COMMUNITY edition users get help with self-hosting.
- [About the OpenVidu team](https://openvidu.io/about-us/index.md): The engineers and researchers behind OpenVidu, and the open-source and scientific work the project has grown out of.
- [OpenVidu research publications](https://openvidu.io/research/index.md): Peer-reviewed papers and PhD theses on WebRTC media server scalability and quality of experience under load, published by the OpenVidu team.
## Blog
- [How client networks affect WebRTC quality and cost](https://openvidu
…Machine-readable: GET /v1/resolve?q=openvidu.io · GET /v1/domain/openvidu.io · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage openvidu.io, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for openvidu.io:
1. POST https://agentwebmap.com/v1/sites/openvidu.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://openvidu.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/openvidu.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/openvidu.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.