this post was submitted on 24 May 2026
820 points (98.1% liked)

Selfhosted

60177 readers
855 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

Hey everyone,

We've built an open-source, privacy-preserving alternative to Ring cameras using a Raspberry Pi Zero 2W (called Secluso). It uses end-to-end encryption to send videos from the camera to a mobile app, which is available both in Google Play Store and Apple App Store. We also support Obtainium for people that do not wish to use Google Play.

We've put in a lot of effort to make it easy to set up! You can set up our camera on your own Pi in less than 5 minutes with minimal technical expertise using our easy-to-use GUI deploy tool. Here are our setup guide and open source release.

The image shows a Pi in an official Raspberry Pi enclosure that you can use for your camera. We've also been working on a HAT for the Pi to add night vision, audio, temperature monitoring for safety, all in a compact form factor. You can see the HAT and an enclosure for the whole camera in the photo.

We've been working on this for almost 2 years now, and we look forward to we look forward to seeing what you all think! If you're interested in our efforts in general outside of DIY, our main website with our pre-built offering is here: click to see our website

you are viewing a single comment's thread
view the rest of the comments
[–] jkaczman@lemmy.zip 5 points 1 month ago* (last edited 1 month ago)

I understand your concern. The way we designed the deployment tool was under the assumption people would be using a freshly-deployed cloud single-use server for it (as we assume they have no technical knowledge).

I'm not sure if a container is foolproof. There have been multiple CVEs in the past allowing processes to escape containers through kernel vulnerabilities. Although, I'm happy to put containers on our to-do list if this will help.

As for what the proper solution should be for advanced users, I personally am not sure. I'd need to research that further. We do try to provide things such as reproducible builds, which means if you build the code yourself using our reproducible build script, they'll match byte-for-byte against our released artifacts. This at least guarantees that it was built from our repository's code, although it does not guarantee the code itself is safe.

I think something that will help here is our planned third-party security audit, which hopefully will be sometime this summer.