[Beta / Open source] Switch CFW web configurator: flexible & automated bash setup & stateless URI config sharing

[u/arelive]

I have developed a modern, stateless web configurator for building clean Nintendo Switch CFW and Homebrew packages.

Why another configurator? I wanted something flexible, stateless, fully transparent, and easy to share.

Features:

• Automated bash script generation: generates a transparent, human-readable bash script to fetch and unpack chosen components directly on your SD card.
• Clean Homebrew stack: modular selection for base, system modules (sys-clk, SaltyNX, etc), overlays (Tesla/Ultrahand, Status Monitor, FPSLocker, etc), Homebrew (App Store, DBI, AIO, JKSV, EdiZon, Breeze, Linkalho, etc), theming (NXThemes, Themeezer), streaming (Moonlight, Akira), and emulators (RetroArch, PPSSPP, melonDS).
• URL parameter state management: all configuration choices are stored directly inside the address bar (URI). You can share custom build setups via a single URL without needing an account or server database.
• Atmosphere 1.12.0 & HOS 23.0.0 ready: updated with support for the newest firmware and Atmosphere builds.

Usage Instructions:

1. Visit https://brewdeck-theta.vercel.app on your PC (best viewed on desktop screens for now, mobile responsive layout is coming soon).
2. Select the revision of your Switch, HOS version.
3. Select desired software.
4. Configure the launch, CFW, security, selected plugins, overclock, and appearance.
5. Download the generated setup script and place it on your SD card root.
6. Execute the script to apply your custom build.

Note: backup your SD card before modifying system files! Keep your Nintendo and emuMMC directories intact!

Known temp issue: MissionControl, ldn_mitm, and uLaunch are currently finicky on HOS 23.0.0 / AMS 1.12.0, as I discovered through trial and error. We will need to wait for upstream updates from their respective maintainers for full compatibility.

This is not low-effort AI slop - it's a properly architected web app. Over the past year, I spent a ton of time digging into Hekate and Atmosphere internals, reading their documentation, and studying custom firmware config structures. I used AI strictly as an execution tool, directing the agent on exactly where every file, sysmodule, and payload needs to go.

Links & Source:

• Live app: https://brewdeck-theta.vercel.app
• Source code: https://github.com/arebaka/brewdeck

Feedback and PRs are welcome!

[u/CarpaMagica]

Thank you for prompting this