It is a substantial update that encompasses a list of new features, notable architectural adjustments, as well as various improvements and bugfixes.
In light of this update, Version 7 takes the lead as our primary version, and as a result, we will be deprecating Version 6.
⚠️ Before you update
As you move to the new version 7, consider rebuilding your project from scratch instead of exporting settings from deprecated versions.
We strongly suggest re-building the project, as version 7 has exended system architecture, improved quality of services and many new features that don't have the best compatibility with the older versions.
It's better to rebuild for better results.
How to update
To update to the new Version 7, launch version 7.3 from the AWS Marketplace.
✧ How to launch : step-by-step guide
New features
- Allowed streams for SRT and RTMP streaming
- RTMP URL update
- Simple SSL certificate management
- Simplified domain-name based access
- Stream and re-stream from Files
- File upload, converting and transcoding
- Video Calls that you can stream, record, embed, monetize
- Detailed SRT statistics
- Audio-track selection
- Player Grouping for multilingual streams
- Virtual events with user authorization and Pay Per View monetization
- API Token re-issuing
Enhanced Streaming Security
In the new version, for streaming over SRT and RTMP, you can explicitly define allowed streams, if privacy and security are one of your major concernes.
There are two options how you can restrict allowed streams: by IP address or by stream ID.
💡 Tip:
Leave both of these fields empty if you want to stream via Host and Port or via default Stream ID.
Allow only specified IP addresses
You can explicitly specify IP address allowed to send or receive streams from your servers.

Allow only specified Stream ID
You can specify a particular Stream ID to restrict streaming from all unknown sources.
📚 How to use
- Create identical Stream IDs to publish and receive streams from the same SRT / RTMP server.
This is due to SRT’s and RTMP’s connection mechanism, identical Stream IDs are required to allow both publishing and receiving the stream.
2. Leave both of these fields empty if you want to stream via Host and Port or via default Stream ID.
3. Leave Receiver field empty or make it different from the Publisher, to prohibit the stream from being received from the server.
