You’re right that Bastille has an existing userbase, but for us it mostly comes down to team size and priorities.
We’re a very small team working on Sylve -- 2 people, one full-time (Me) and one part-time who used to work on frontend but not so much anymore since his work is mostly completed, so we have to be selective about what we spend time on. In practice, we build features that Alchemilla (my company) can use internally, and some of that work was also funded by the FreeBSD Foundation where it aligned with our use cases, like jail and bhyve management.
We’ve also continued adding things we find useful outside of that funded work, like Samba Shares, Downloader utility, WoL (Wake on LAN), and even upcoming features like PF and WireGuard into the GUI.
With Bastille, the issue is that we’ve never really used it ourselves, so supporting it properly would mean spending time learning Bastille, understanding its codebase and model, and then figuring out how to integrate it in a meaningful way. For a team our size, that’s a pretty big investment.
Especially when there are other areas like Podman and the broader container ecosystem; where we think the userbase is larger (think Docker) and the overlap with our goals is stronger.
So it’s not that we think Bastille is unimportant, just that it’s hard for us to justify prioritizing right now. If someone from the community wanted to work on that direction, we’d definitely be open to looking at it.
), dass man sich um dessen Zukunft in absehbarer Zukunft keine Sorgen machen muss. 
