A lightweight, zero-dependency video meeting platform featuring direct peer-to-peer WebRTC calls, waiting room moderation, multi-provider OAuth, and local recordings.
🚀 Open Meetspace Live • 💻 GitHub Repository • 🐛 Report an Issue
- Instant & Invite Calls: Start an instant meeting or join any session via a unique code.
- Smart Scheduling: Plan meetings ahead and export calendar invites (
.ics) for Google Calendar, Apple Calendar, and Outlook. - P2P Audio & Video: High-fidelity, low-latency WebRTC streams with screen sharing and integrated live chat.
- Host Moderation: Secure waiting room to admit or deny entries, participant eviction, and remote mute requests.
- Private Browser Recording: Capture sessions client-side directly in your browser library—exportable to WebM/MP4 with zero cloud bandwidth costs.
- Adaptive Dashboard: Clean, responsive workspace with light/dark theme support, calendar views, contacts, and recordings.
- Flexible Authentication: Native email/password sign-in with
scrypthashing, plus optional 1-click Google, Microsoft, and Apple OAuth.
Meetspace separates the control plane (signaling & scheduling) from the data plane (media streaming):
sequenceDiagram
autonumber
actor Alice as Host (Alice)
participant Server as Meetspace Server (Node.js / WS)
actor Bob as Guest (Bob)
Note over Alice,Bob: 1. Room Creation & Waiting Room
Alice->>Server: Create Meeting
Bob->>Server: Request Join with Invite Code
Server->>Alice: Waiting Room Prompt (Admit Bob?)
Alice->>Server: Admit Bob
Server->>Bob: Access Granted
Note over Alice,Bob: 2. WebRTC Signaling (WebSockets)
Alice->>Server: SDP Offer
Server->>Bob: Forward SDP Offer
Bob->>Server: SDP Answer
Server->>Alice: Forward SDP Answer
Note over Alice,Bob: Exchange ICE Candidates (via STUN)
Note over Alice,Bob: 3. Encrypted P2P Media Stream
Alice->>Bob: Direct Audio / Video / Screen Share
Bob->>Alice: Direct Audio / Video / Screen Share
Network Note: Built-in STUN negotiation handles peer-to-peer traversal across standard networks. Restrictive corporate firewalls or symmetric NATs may require a custom TURN relay.
- Node.js 20+ installed.
- Zero package installations (
npm installis not required).
# 1. Clone the repository
git clone https://github.com/vaibhavtevatia7946/meetspace.git
cd meetspace
# 2. Start the native server
node app-server.mjsOpen https://meetspace-vaibhav.vercel.app to test it live, or navigate to http://localhost:3000 when running locally.
Note
Camera and microphone access are modern browser security features that require either localhost or an https:// origin.
Email/password authentication works right out of the box with zero setup. To activate OAuth sign-in:
- Copy
.env.exampleto.env:cp .env.example .env
- Add client credentials from your provider consoles.
- Start the server loading the environment file:
node --env-file=.env app-server.mjs
Register these exact redirect URLs in your provider dashboards:
| Provider | Local Callback URL | Production Callback URL |
|---|---|---|
http://localhost:3000/auth/google/callback |
https://meetspace-vaibhav.vercel.app/auth/google/callback |
|
| Microsoft | http://localhost:3000/auth/microsoft/callback |
https://meetspace-vaibhav.vercel.app/auth/microsoft/callback |
| Apple | http://localhost:3000/auth/apple/callback |
https://meetspace-vaibhav.vercel.app/auth/apple/callback |
Tip
- For production, set
BASE_URLto your live domain:https://meetspace-vaibhav.vercel.app. - Microsoft can use
MICROSOFT_TENANT_ID=commonor a custom tenant. - Apple requires a Sign in with Apple Service ID and private key JWT secret (
APPLE_CLIENT_SECRET).
Meetspace is configured for zero-configuration deployment to Vercel via server.ts and vercel.json.
- Import the repository at vercel.com/new.
- Under Project Settings → Environment Variables, add your
BASE_URL(https://meetspace-vaibhav.vercel.app) and any OAuth keys. - Click Deploy.
Warning
Serverless Storage Notice:
The included JSON file store (data/meetspace.json) is designed for local prototyping. Because Vercel's serverless runtime is ephemeral, local files reset across cold starts and deployments. For persistent multi-instance production, connect a database (e.g., Supabase, Neon, or Redis) and a shared session store. Recordings are saved strictly in the user's browser and do not touch the server.