100ms Integration for Video Conferences on Your Website

Integration of 100ms for Video Conferences on Your Website

Typical problem: you embedded a Zoom iframe, but participants complain about delays, interface customization is impossible, and scaling is limited. 100ms solves this via an SDK with full control. 100ms — WebRTC-platform with React SDK, ready-to-use UI components, and flexible pricing. The key feature is Rooms and Templates: you create a template in the dashboard (role settings, recording, quality), then create rooms based on it. This eliminates manual rights management and allows scaling video conferences to hundreds of participants without overloading the backend.

We use 100ms to embed video conferences with full control: custom roles, recording, UI customization. No iframe hacks or Zoom limitations. If a hundred users on your site are trying to join a conference simultaneously, 100ms handles it with Rooms and Templates. Our clients save on average $5000 on developing their own WebRTC solution by switching to 100ms.

What Problems Does 100ms Solve?

100ms efficiently manages roles: you create a template with roles like host, guest, viewer. Each participant receives a token with the corresponding role. Cloud recording of conferences is enabled in the template, webhooks notify about start and end. WebRTC ensures real-time communication with minimal latency — confirmed by load testing. Roomkit allows you to override the interface to match your brand — colors, element layout, custom buttons.

Why Is 100ms Better Than a Custom WebRTC Solution?

Custom WebRTC requires implementing STUN/TURN servers, signaling, room management, and tokens. 100ms provides everything out of the box: a ready backend for creating rooms, token generation, and monitoring. This reduces development time by weeks and lowers the risk of errors. According to our data, integrating 100ms is 3 times faster than developing a custom WebRTC solution. The cost per video minute in 100ms starts at $0.004, significantly cheaper than alternatives (Twilio ~$0.008, Agora ~$0.007). Thus, you save both time and money.

How Does the Integration of 100ms on Your Site Work?

We build a server-side API for creating rooms and generating tokens. The client SDK (React) connects to the room and manages audio/video streams. Below are the key steps.

Creating a Room and Getting a Token

npm install @100mslive/roomkit-react @100mslive/react-sdk 

// On the server — Management Token for API import jwt from 'jsonwebtoken'; function generateManagementToken(): string { return jwt.sign( { access_key: process.env.HMS_ACCESS_KEY, type: 'management', version: 2, iat: Math.floor(Date.now() / 1000), nbf: Math.floor(Date.now() / 1000), }, process.env.HMS_APP_SECRET!, { algorithm: 'HS256', expiresIn: '24h' } ); } // Create a room async function createRoom(name: string): Promise<string> { const mgmtToken = generateManagementToken(); const response = await fetch('https://api.100ms.live/v2/rooms', { method: 'POST', headers: { 'Authorization': `Bearer ${mgmtToken}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ name, template_id: process.env.HMS_TEMPLATE_ID, // from 100ms Dashboard }), }); const room = await response.json(); return room.id; } // Get an App Token for a participant async function getAppToken(roomId: string, userId: string, role: string): Promise<string> { const mgmtToken = generateManagementToken(); const response = await fetch('https://api.100ms.live/v2/auth-token', { method: 'POST', headers: { 'Authorization': `Bearer ${mgmtToken}`, 'Content-Type': 'application/json', }, body: JSON.stringify({ room_id: roomId, user_id: userId, role, // role from Template: 'host', 'guest', 'viewer' }), }); const { token } = await response.json(); return token; } // API endpoint app.post('/api/video/join', authenticate, async (req, res) => { const { sessionId } = req.body; let session = await db.videoSessions.findById(sessionId); if (!session.hmsRoomId) { const roomId = await createRoom(`session-${sessionId}`); session = await db.videoSessions.update(sessionId, { hmsRoomId: roomId }); } const isHost = session.hostId === req.user.id; const token = await getAppToken(session.hmsRoomId, req.user.id, isHost ? 'host' : 'guest'); res.json({ token }); }); 

React Component with Roomkit

import { HMSRoomProvider, useHMSActions, useHMSStore, selectIsConnectedToRoom, selectPeers, selectLocalPeer, HMSPeer, } from '@100mslive/react-sdk'; function VideoConference({ authToken, userName }: { authToken: string; userName: string }) { return ( <HMSRoomProvider> <VideoRoom authToken={authToken} userName={userName} /> </HMSRoomProvider> ); } function VideoRoom({ authToken, userName }) { const hmsActions = useHMSActions(); const isConnected = useHMSStore(selectIsConnectedToRoom); const peers = useHMSStore(selectPeers); const localPeer = useHMSStore(selectLocalPeer); useEffect(() => { hmsActions.join({ authToken, userName, settings: { isAudioMuted: false, isVideoMuted: false } }); return () => { hmsActions.leave(); }; }, [authToken]); if (!isConnected) { return <div className="flex items-center justify-center h-64">Connecting...</div>; } return ( <div> <div className="grid grid-cols-2 gap-4 p-4"> {peers.map(peer => ( <PeerTile key={peer.id} peer={peer} /> ))} </div> <div className="flex gap-3 justify-center p-4"> <button onClick={() => hmsActions.setLocalAudioEnabled(!localPeer?.audioEnabled)} className="p-3 rounded-full bg-gray-800 text-white"> {localPeer?.audioEnabled ? '🎤' : '🔇'} </button> <button onClick={() => hmsActions.setLocalVideoEnabled(!localPeer?.videoEnabled)} className="p-3 rounded-full bg-gray-800 text-white"> {localPeer?.videoEnabled ? '📹' : '📷'} </button> <button onClick={() => hmsActions.leave()} className="p-3 rounded-full bg-red-600 text-white"> Leave </button> </div> </div> ); } function PeerTile({ peer }: { peer: HMSPeer }) { const videoRef = useRef<HTMLVideoElement>(null); const hmsActions = useHMSActions(); const videoTrack = useHMSStore(selectCameraStreamByPeerID(peer.id)); useEffect(() => { if (videoRef.current && videoTrack) { hmsActions.attachVideo(videoTrack.id, videoRef.current); } return () => { if (videoRef.current && videoTrack) { hmsActions.detachVideo(videoTrack.id, videoRef.current); } }; }, [videoTrack]); return ( <div className="relative bg-gray-900 rounded-xl overflow-hidden aspect-video"> <video ref={videoRef} autoPlay muted={peer.isLocal} playsInline className="w-full h-full object-cover" /> <span className="absolute bottom-2 left-2 text-white text-sm bg-black/50 px-2 rounded"> {peer.name} {peer.isLocal && '(you)'} </span> </div> ); } 

What Is Included in the Integration?

Backend API: server endpoints for creating rooms, generating tokens, and managing templates. React components: connecting Roomkit, customizing UI to match your brand. Template setup: creating templates in the 100ms dashboard with desired roles and recording options. Testing: stability check with simultaneous connections of 50+ participants. Documentation: API description and deployment instructions. Post-support: consultations after integration.

Comparison of 100ms with Other WebRTC Solutions

100ms wins in customization and ease of integration, and holds a mid-range price position. We help choose the optimal solution for your tasks.

Stages of 100ms Integration

Timeline

Integration of 100ms with room creation, tokens, and React component — 2–3 days. With roles, recording, and webhooks — 4–5 days. Contact us to discuss your project details.

Why Choose Us?

Our team has over 5 years of experience in web development and integration of WebRTC solutions. We guarantee stability of video conferences under load and provide technical support after implementation. Certified specialists keep code up-to-date and track SDK updates. Core stack: React, TypeScript, Node.js, 100ms SDK.

Get a consultation — we will evaluate your project and offer the optimal solution for video conference integration. Get a consultation on 100ms integration. Contact us to discuss the details.