AlohaCam FAQs
Alohacam is a video streaming solution for embedded devices, powered by our WebRTC native library – AlohaRTC.
The awesome team over at Lanikai Labs. You can check us out here!
Just click here and then click "Create an account". It's as easy as that!
Alohacam currently supports all Raspberry Pi development boards. We'll let you know as we release support for more development boards (looking at you, Jetson Nano!) – so stay tuned.
Short answer: Security is our top priority. Alohacam uses WebRTC, and the entire interaction is encrypted. This means that (unlike some IoT solutions) only you can view your Alohacam!
Longer answer: We use client side SSL/TLS encryption. The Alohacam install script will auto-generate a certificate for your device. This certificate never leaves your device – we don't store it or have access to it – and you can even use your own. When a connection to your device is initiated, your browser will create a dynamic certificate (through DHE key exchange) that is valid only for that session. Both certificates use X.509 standards. We designed these security measures to ensure that only you will be able to view your Alohacam!
Alohacam is powered by a WebRTC native library. The video you're seeing is from the hardware-accelerated H.264 byte-stream.
By using WebRTC to power Alohacam, we have brought the required bandwidth down to about 1MB/s.
Alohacam supports a single viewer at a time, but we're looking into multi-viewer support!
You'll need a Raspberry Pi development kit, a Raspberry Pi camera module, a real email address, and a sense of adventure! You can sign up for Alohacam here and view the step-by-step guide here.
We're glad you like Alohacam! We're not planning a public release of our code base, but you can check out our documentation (and run a local network analysis!) to see how we've built it.
Excellent – we can't wait to hear it! Send us a note at [email protected]!
Here's a step-by-step guide to walk you through the setup process. If you're still running into issues, shoot us an email at [email protected]!
Whoops! No worries – just run rm cert.pem
on your device to clear the original certificate. Now you should be able to re-add it! Reach out to us at [email protected] if you're still having issues.
We know no one reads these, but just in case...
Privacy Policy
Terms of Service