The 2024 BigBearCasaOS Brave tutorial still points to a maintained app, but the container image and version have changed. The current BigBear catalog lists Brave as kasmweb/brave, while Kasm itself now publishes newer stable and rolling image tags.
This is a browser delivered through KasmVNC in a container. It is not the same as installing Brave directly on the CasaOS host.
The BigBear Brave App Is Still Present
The current BigBear app catalog still lists Brave with the Kasm image. BigBear is a third-party app source maintained independently, so its app definitions can change separately from CasaOS itself.
Use Current Kasm Image Guidance
The current Kasm Brave image documents standalone access through HTTPS on port 6901 and shows that newer image tags are available than the version in the BigBear catalog.
Do not blindly replace the image tag in the BigBear app without checking whether its environment variables and persistent profile paths are compatible.
Persist the Browser Profile Deliberately
A container browser can lose bookmarks, extensions and session state when recreated unless the expected profile/config data is persisted. Verify the BigBear appโs current volume mappings before treating it like a desktop browser.
The self-hosted app guide is useful for understanding why browser containers can use more memory than lightweight server apps.
Do Not Expose the KasmVNC Port Publicly Without Protection
A remote browser session can contain credentials, downloads and authenticated web sessions. Keep the interface on a trusted network or put deliberate authentication and remote-access controls in front of it.
Bottom Line
The old tutorial remains a valid discovery path, but use the current BigBear app definition and Kasm image documentation. Treat Brave as a browser-in-a-container service with its own HTTPS port, persistent profile needs and remote-access security boundary.
