Free is the room itself. Pro adds meeting length, recording, SmileDrive storage, file sharing, notes, the meeting assistant and appointment booking; Developer adds the API. Every number below is read from the same table the server enforces at runtime, so the plan you pick is the plan you get.
For everyday conversations
Free
For professionals who meet all day
$12 /month
For teams and organizations
$24 /month
Video infrastructure for your product
$99 /month
Prices, limits and room sizes above are read live from the plans table and the media layer, which is the same source the server enforces at runtime — so what you see is exactly what the server will allow. Media server (SFU) — up to 50 people in one room.
Four products share one account: Meetings for the video room, SmileDrive for the cloud storage recordings and uploads land in, Appointments for the public booking page you publish, and — on the Developer plan — the Verification API for KYC and KYB checks. Free is the room alone — chat, reactions, waiting room, screen sharing and raise hand. Pro adds everything around the meeting: unlimited length, recording, file sharing, shared notes and voice notes, the meeting assistant, attendance, live captions, SmileDrive and appointment booking pages. The numbers in the cards above are per product: meeting length and room size are the rooms, storage is SmileDrive, and API calls and verification checks come off the API allowance.
The server enforces the limit as the room heartbeats: at 40 minutes the meeting is closed with a message in the call, and everyone can start a new one. There is no countdown that only exists in the browser.
Yes, and in two separate ways. On Pro and above, the host can record the meeting locally from inside their browser: the call is composited into one video and saved straight to the host's own computer, with everyone in the room told when it starts. Nothing is uploaded by that step — the file is yours, on your machine.
If you want the file to live on the server instead of your laptop, the host can upload it to SmileDrive when the recording ends — that is how a recording becomes something your whole workspace can reach, with folders, share links and per-file history. It needs the installation to have a storage bucket configured, and it is announced in the room when it happens.
Fully server-side cloud recording, where the call is captured without a host doing anything, additionally needs a capture service connected by whoever runs the installation. When any of this is unavailable we say so plainly, and a recording is never shown as ready unless a real file exists. We never show a placeholder player.
No. Guests can join from a link with just their name, unless the host requires everyone to sign in.
Up to 50 people per room today. The media server (SFU) is enabled, so rooms scale to 300 participants, and the plan entitlement is what you actually get.
Direct connections work on most home and office networks. A TURN relay is not configured yet, so on a network that blocks peer-to-peer traffic a call cannot connect; TURN is the infrastructure item the roadmap puts first.
One quota is shared by SmileDrive and the meeting recordings uploaded into it, so a byte is a byte wherever it lives. Uploaded recordings, files you upload yourself and files your API sends all draw on the same pool, and the server refuses an upload that would cross the limit rather than silently dropping it. The storage figure in each card above is that limit.
The Developer plan adds API keys, webhooks, the JavaScript SDK and embedded meetings, metered by monthly API calls. Per-key rate limits are shown in the developer portal.
It also includes the verification API: submit an identity or business document and Smile Cast brokers the check to a licensed provider, records the result against your workspace and returns it with a reference you can look up. Checks are metered against a monthly allowance, an unconfigured provider returns an error rather than a made-up verdict, and a sandbox key runs the same code path against deterministic test data so nothing ships untested. See what the API returns.
