this post was submitted on 05 Nov 2025
173 points (91.8% liked)

Selfhosted

60451 readers
885 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
ayyy@sh.itjust.works
curbstickle@anarchist.nexus
curbstickle_lw@lemmy.world
173
Safebox: Open-source framework for managing self-hosted apps (Beta) (lemmy.world)
submitted 8 months ago* (last edited 7 months ago) by drebora@lemmy.world to c/selfhosted@lemmy.world
32 comments fedilink hide all child comments
 

Update: after a longer break, we've released a bugfix for the framework-scheduler component, primarily addressing issues related to the upgrade process. If you’re already using Safebox, you can access the update in the Notifications menu.

Hi everyone, we’ve been working on Safebox, an open-source framework that helps you install, manage, and access self-hosted applications such as Home Assistant, Nextcloud, and Jellyfin ect. Safebox runs on Linux, macOS, and Windows (supporting both x86 and ARM64 architectures, even Raspberry Pi, Banana Pi hardwares also tested). It manages domain and subdomain setup, Let's Encrypt certificates, DNS configuration, and reverse proxy (nginx). It also includes a WireGuard-based remote access feature and a geo-redundant backup system (currently in development). The project is in beta, and we’re looking for people interested in testing and sharing feedback. All information about Safebox and beta testing can be found in our Discord channel. Try it using Docker: docker run --rm -v /var/run/docker.sock:/var/run/docker.sock safebox/framework-scheduler

Then open: http://localhost:8080/

Links: Website: https://safebox.network/ GitHub: https://github.com/safeboxnetwork/framework-scheduler Discord: https://discord.gg/aBP8bz6N8J

We’d really appreciate any feedback or ideas for improvement.

you are viewing a single comment's thread
view the rest of the comments
[–] gyurix@lemmy.world 2 points 8 months ago

I mentioned earlier that your branding seems to emphasize security - but all I’m seeing is mention of existing security features inherent in the software being wrapped. Does your team do additional tuning for security? Do they have experience in infrastructure security, hardening systems, or the like? To be clear I just want to better understand the branding and what is being offered.

Hi, I am one of developers from Safebox and would like to answer your security related questions: you have right, our Safebox platform contains only a HAproxy loadbalancer and Nginx backend proxies to route your domain based TCP packets and does not responsible for security of the 3rd party providers applications. That means Safebox is not more secure as the installed 3rd party applications, because if the application you install isn’t secure or you don’t take care of your passwords, then your data could still be stolen. But it does provide security in the sense that you know where your data is, and you know that it belongs to you.

In addition we plan to develop a 'homeguard' plugin for Safebox to manage accessing the main platform and set individualy permissions via backend proxies to access the deployed 3rd party applications.