How a leading security solutions provider cut vendor lock-in with a 50% faster IoT streaming backend
A leading locks and security solutions provider in India relied on external vendors for both security camera hardware and software. This limited the company's control over its camera ecosystem and made it harder to scale or integrate different hardware. Flentas addressed the dependency at the backend layer, building a vendor-agnostic IoT platform on AWS. The new architecture enabled communication between cameras and mobile applications across hardware while replacing traditional client-server video streaming with peer-to-peer streaming. The result was 50% faster real-time video streaming performance, along with a backend that gave the company greater flexibility over its security camera ecosystem.
Vendor lock-in limiting flexibility and scale
The company's security camera ecosystem depended on external vendors for both hardware and software. This created a dependency on proprietary systems and limited how much control the company had over the underlying technology.
No standardized IoT backend
There was no common backend layer that could facilitate communication between mobile applications and different cameras.
Limited streaming architecture
The company needed a more scalable approach to video streaming that could move away from traditional client-server networking.
Hardware flexibility
The backend needed to support camera hardware without tying the platform to a single vendor's software stack.
A vendor-agnostic IoT backend built on AWS-managed services
Flentas focused on separating the IoT backend from individual hardware vendors. The goal was to create a common communication and video streaming layer that could work across the company's camera ecosystem.
- 01
AWS IoT Core was used to establish direct communication between mobile applications and cameras, creating a standardized IoT backend.
- 02
For real-time video, Amazon Kinesis Video Streams with WebRTC enabled peer-to-peer streaming between cameras and mobile applications. This replaced the traditional client-server model and reduced the additional latency associated with routing video through a central server.
- 03
Backend administration and device management were handled through Spring Boot REST APIs deployed on AWS Fargate. This provided managed container infrastructure without requiring the company to operate dedicated servers.
- 04
Security was built into the platform using Amazon Cognito for user authentication and OAuth-based API access. MQTT Pub/Sub services were used to support security policy enforcement.
Faster streaming, lower infrastructure overhead, and greater flexibility
The new backend gave the company greater control over its IoT platform while improving the performance of real-time video streaming.
50% faster streaming performance
Moving from traditional client-server networking to peer-to-peer streaming improved real-time video streaming performance by 50%.
Reduced infrastructure costs
AWS-managed WebRTC services reduced the need to maintain custom streaming infrastructure.
Greater vendor independence
The standardized IoT backend allowed the platform to communicate with camera hardware without depending on a single vendor's proprietary software stack.
Improved security management
MQTT Pub/Sub services supported security policy enforcement across the IoT environment.
Scalability
AWS-managed services and containerized backend components provided a foundation that could scale with the security camera ecosystem.
Faster time to market
The new architecture enabled faster deployment of security solutions while giving the company greater control over its technology stack.
Built on the AWS IoT stack
Where this fits
Industry 4.0
Explore Industry 4.0Ready to build IoT infrastructure that isn't locked to a single vendor?
Talk to an AWS-certified architect about your own IoT platform.

