Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise. Learn more →
Flatpak Alternatives
Similar projects and alternatives to flatpak
-
-
AppSignal
AppSignal knows why the f*#k it crashed. Stop vibe-debugging. Every exception, every backtrace, grouped so you see patterns, not noise.
-
-
-
-
-
-
distrobox
Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
-
-
AppImageKit
Package desktop applications as AppImages that run on common Linux-based operating systems, such as RHEL, CentOS, openSUSE, SLED, Ubuntu, Fedora, debian and derivatives. Join #AppImage on irc.libera.chat
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
flatpak discussion
flatpak reviews and mentions
-
Sovereign Tech Agency invests €500k in Flatpak
It's great that there's more investment being put into Flatpak development. The page mentions adding more granular permissions, which is nice to see. However, another necessary improvement is actually making it possible for software to incorporate these new granular permissions in a backwards compatible manner.
As one example, I maintain a game on Flathub that supports game controllers as an input device. By default, access to game controllers are blocked in the sandbox just like access to any other piece of hardware. The only way to use game controllers is to mark your software as requiring a blanket permission that grants access to all devices connected to the user's system. The Flatpak maintainers realized this is problematic, so a few years ago they added a permission to specifically request access to input devices (https://github.com/flatpak/flatpak/pull/5481). However, because the permissions aren't backwards compatible, and because there's LTS distros under active support with old Flatpak versions released before the permission was added, you aren't allowed to use this permission on Flathub, only the blanket "all devices" permission. As a result, Flathub lists my game as "potentially unsafe" because it "can access hardware devices such as webcams and game controllers" because the only other option was disabling game controllers entirely.
If they figure out a way to implement the new permissions so they can fall back to the broader kind on old Flatpak versions, this would be a massive improvement over the current situation. Otherwise you'll have to wait 10+ years before you can use newly added permissions because the only other option is breaking Flatpak on whatever ancient Ubuntu or RHEL version is still under support.
-
Microsoft Can Track Users via a Windows Device ID
I went to check if Flatpak would protect against this but it seems although it's a wanted feature it's not so straightforward to implement: https://github.com/flatpak/flatpak/issues/4311
-
My fully offline AI-assisted Linux development machine
Docker, Distrobox, Flatpak, and a bit of Homebrew where it makes sense
-
OpenClaw isn't fooling me. I remember MS-DOS
https://flatpak.org/ does this on Linux and someone else already pointed out, MacOS does this with app store apps. I don't like handing control to Apple so I much prefer the FlatPak solution - you get very detailed and fine grained control over what each app can see and it works fairly seamlessly. It's still a bit technical - but not far from being user friendly even for a less tech savvy user.
- Flatpak: Complete Sandbox Escape
-
Slightly safer vibecoding by adopting old hacker habits
> "Create a new user account" is much better advice than "don't use a container".
That wasn't exactly what PunchyHamster was saying. PH was saying that putting it in a container doesn't prevent it from scanning (and attacking) your network... so your IP network security is just as bad when it's containerized as when it's not. Containers/sandboxes can provide filesystem segmentation (except when they don't! [0]), but the way they're typically used, they provide zero network segmentation.
I mention in my comment here [1] that it's useful for whatever isolation mechanism you use (even if it's "just" 'a separate minimally-privileged user') to ensure that programs its spawns are on separate VLANs that your router prevents from talking back to hosts on your trusted VLANs.
[0] <https://github.com/flatpak/flatpak/security/advisories/GHSA-...>
[1] <https://news.ycombinator.com/item?id=47690425>
-
Discovering Fedora: My First Days in an Open Source Community That Actually Lives Its Values
Features Fedora leads. Others follow. Systemd? Fedora pioneered it. Wayland? Fedora adopted it early. Flatpak? Fedora helped develop it.
-
The Holy Grail of Linux Binary Compatibility: Musl and Dlopen
There are things like this.
The things I know of and can think of off the top of my head are:
1. appimage https://appimage.org/
2. nix-bundle https://github.com/nix-community/nix-bundle
3. guix via guix pack
4. A small collection of random small projects hardly anyone uses for docker to do this (i.e. https://github.com/NilsIrl/dockerc )
5. A docker image (a package that runs everywhere, assuming a docker runtime is available)
6. https://flatpak.org/
7. https://en.wikipedia.org/wiki/Snap_(software)
AppImage is the closest to what you want I think.
- 2026 will be my year of the Linux desktop
-
Snap vs Flatpak: Ultimate Guide for 2025
Flatpak Official Website
-
A note from our sponsor - AppSignal
www.appsignal.com | 6 Oct 2026
Stats
flatpak/flatpak is an open source project licensed under GNU Lesser General Public License v3.0 only which is an OSI approved license.
The primary programming language of flatpak is C.