SolutionsEmbedded calls
Calls that live inside your product
Your app already knows the customer. Vasl is the picture and the sound: a room that exists for that appointment, a recording if the contract requires one, and no one else’s logo on the call.
Publish
Encoders, cameras, browsers and mobile apps open the session.
Vasl
One server you run transcodes, records, authorizes and fans the stream out.
Play
Interactive viewers stay on WebRTC. Broader audiences take HLS from the same publish.
Workflows
Sessions teams embed
Onboarding
A specialist walks a new customer through the product. The call opens from your app and ends when the appointment does.
Design and document reviews
Share a screen, mark the moment, and keep the recording next to the project if you want it.
Support escalations
When chat is not enough, open a room for that ticket. The recording can attach to the case.
Hiring panels
A candidate link that expires. Reviewers watch the recording later, on your storage.
Hybrid rooms
A camera in a meeting room can join the same session as people on laptops.
Your identity
Who may enter is your decision. Vasl checks the token you issued.
On this workload
How Vasl is tuned here
Your product, your call
Customers should not leave your site to finish a meeting. Embed playback and publish, and keep the calendar where it already is.
- Web and mobile SDKs
- Rooms created by API
- Tokens that expire with the appointment
- HLS if most people are only watching
Record only when you mean to
Some sessions must be kept. Most should not. The switch is yours, and the file does not have to leave your network.
- Recording on or off per room
- Files on storage you run
- Webhooks into the ticket or the project
- Self-hosted or a private cloud
Why teams choose Vasl for Video Conferencing
- No third-party meeting brand
- Rooms tied to your records
- Recording you can decline
- SDKs for the app you ship
Same server
