Build. Brand. Deploy. β One Panel to Rule Them All.
π WUZEN is a powerful web-based control panel that lets you generate custom, signed Android APKs in minutes β no Android Studio, no complex builds, no tears.
- β¨ What Is WUZEN?
- π Features
- βοΈ Prerequisites
- π¦ Installation
- π§ Configuration
- π₯οΈ Accessing the Panel
- π± Building Your First APK
- π Security
- π Troubleshooting
- π€ Contributing
---
WUZEN Application Builder is a self-hosted, Node.js-powered web panel that allows anyone β even beginners β to generate custom branded Android APKs directly from a browser interface.
No coding knowledge required. Just configure, upload your logo, hit Build, and download your APK.
Browser β WUZEN Panel β Build Script β Signed APK β
| Feature | Description |
|---|---|
| π§ One-Click APK Build | Generate APKs from a simple web form β no terminal needed |
| π¨ Custom Branding | Upload your own logo, set your app name |
| π WebView Integration | Wrap any URL into a native Android app instantly |
| π Signed APK Output | All builds are signed and ready for installation |
| β‘ Fast Builds | Optimized build pipeline powered by apktool + apksigner |
| π Live Build Logs | Watch your APK compile in real-time via the log panel |
| π₯οΈ Web-Based Panel | Accessible from any browser on your network |
β οΈ Before you begin, make sure your server or VPS is running Ubuntu/Debian Linux.
Windows is NOT supported natively. Use WSL2 or a Linux VPS.
You'll need the following installed:
| Tool | Version | Why It's Needed |
|---|---|---|
| nvm | Latest | Manages Node.js versions cleanly |
| Node.js | v24 LTS | Runs the WUZEN web panel |
| OpenJDK | 17+ | Required by APK tools (Java dependency) |
| apktool | 2.9.3+ | Decodes and rebuilds APK files |
| apksigner | via Android Build Tools | Signs APKs so they can be installed |
| PM2 | Latest | Keeps the panel running in the background |
git clone <[your-repo-url](https://github.com/sunimakgoho-arch/WUZEN-MYTHOS-EDITION.git)>
cd <WUZEN-MYTHOS-EDITION>β Best for beginners. The build script handles most of the setup automatically.
# Step 1: Configure your server settings FIRST (required)
nano json/config.json
# Step 2: Give the script execute permission
chmod +x build.sh
# Step 3: Run the builder
./build.sh
β οΈ Do NOT skip Step 1. The panel will not work correctly without configuringconfig.jsonfirst.
Use this method if the quick start fails or you want full control over each component.
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
source ~/.bashrcVerify:
nvm --versionnvm install 24
nvm use 24
node --version # Should output v24.x.xsudo apt update
sudo apt install openjdk-17-jdk -y
java -version # Should output openjdk 17.x.x
β οΈ Do NOT useapt install apktoolβ the apt version is often outdated and will cause build failures.
# Download the latest apktool JAR
wget https://bitbucket.org/iBotPeaches/apktool/downloads/apktool_2.9.3.jar -O apktool.jar
# Download the Linux wrapper script
wget https://raw.githubusercontent.com/iBotPeaches/Apktool/master/scripts/linux/apktool -O apktool
# Give execute permissions
chmod +x apktool
# Move both files to system path
sudo mv apktool.jar /usr/local/bin/apktool.jar
sudo mv apktool /usr/local/bin/apktoolVerify:
apktool --version
β οΈ Do NOT useapt install apksignerβ it may be outdated or broken on many systems.
# Install dependencies
sudo apt install unzip wget -y
# Download Android command-line tools
wget https://dl.google.com/android/repository/commandlinetools-linux-latest.zip
# Extract into the right folder structure
mkdir -p $HOME/android/cmdline-tools
unzip commandlinetools-linux-latest.zip -d $HOME/android/cmdline-tools
# Set environment variables (add these to ~/.bashrc for persistence)
export ANDROID_HOME=$HOME/android
export PATH=$ANDROID_HOME/cmdline-tools/cmdline-tools/bin:$ANDROID_HOME/platform-tools:$PATH
# Accept licenses and install build tools
yes | sdkmanager --licenses
sdkmanager "build-tools;34.0.0"π‘ Tip: Add the
exportlines to your~/.bashrcfile so they persist after reboot:echo 'export ANDROID_HOME=$HOME/android' >> ~/.bashrc echo 'export PATH=$ANDROID_HOME/cmdline-tools/cmdline-tools/bin:$ANDROID_HOME/platform-tools:$PATH' >> ~/.bashrc source ~/.bashrc
Verify:
apksigner versionnpm installPM2 keeps your panel running even after you close the terminal or reboot.
npm install -g pm2
# Start the panel
pm2 start index.js --name "wuzen-panel"
# Auto-restart on system reboot
pm2 startup
pm2 save
β οΈ This step is required before running the panel. Skipping it will cause connection errors.
Open the configuration file:
nano json/config.jsonFind the def section and update these two values:
"def": {
"host": "YOUR_SERVER_IP_OR_DOMAIN",
"port": "3000"
}| Field | What to Put Here | Example |
|---|---|---|
host |
Your VPS IP address or domain name | 192.168.1.10 or yourdomain.com |
port |
The port the panel will run on | 3000 |
Example (local test):
"def": {
"host": "localhost",
"port": "3000"
}Example (VPS/production):
"def": {
"host": "203.0.113.45",
"port": "3000"
}Save and exit: Ctrl+X β Y β Enter
Once the panel is running, open your browser and go to:
http://YOUR_HOST:3000
First-time login:
- Enter your activation key when prompted
- Log in with the default password:
Password: WUZEN
π΄ IMPORTANT: Change the default password immediately after your first login. See Security below.
Follow these steps inside the WUZEN panel:
Step 1 β Click "Build APK" in the panel
Step 2 β Upload your App Logo (PNG recommended, 512Γ512px)
Step 3 β Enter your App Name
Step 4 β Set the Host & Port for the app's backend
Step 5 β Enter the WebView URL (the website/app URL to wrap)
Step 6 β Click "Build" and wait
Step 7 β Scroll down to the Logs section
Step 8 β Download your signed APK β
β³ Build time is typically 1β5 minutes depending on server performance.
Do not close or refresh the browser while building.
π¨ These steps are critical if your panel is accessible over the internet.
- Change the default password (
WUZEN) immediately after first login - Do not expose the panel publicly without proper authentication
- Use HTTPS in production (set up a reverse proxy with Nginx + Let's Encrypt)
- Restrict access by IP using a firewall (e.g.,
ufw) if possible - Keep dependencies updated regularly
Basic firewall setup (optional but recommended):
sudo ufw allow 22 # SSH
sudo ufw allow 3000 # WUZEN Panel
sudo ufw enableπ΄ Port already in use
lsof -i :3000 # Find what's using port 3000
kill -9 <PID> # Kill that process
pm2 restart wuzen-panelπ΄ Permission denied on build.sh
chmod +x build.sh
./build.shπ΄ Java not found / Java errors
java -version # Check if Java is installed
sudo apt install openjdk-17-jdk -y # Reinstall if missingπ΄ apktool: command not found
Re-run the manual apktool install steps. Make sure both files are in /usr/local/bin/:
ls /usr/local/bin/ | grep apktoolπ΄ apksigner not found after installation
Make sure your environment variables are set:
source ~/.bashrc
apksigner versionIf still missing, re-run the sdkmanager "build-tools;34.0.0" step.
π΄ npm install fails
nvm use 24 # Make sure you're on the right Node version
node --version # Confirm v24.x.x
npm install # Retryπ΄ Panel not loading in browser
- Check PM2 is running:
pm2 status - Check your config.json host/port match what you're visiting
- Check firewall isn't blocking the port:
sudo ufw status
Contributions are welcome! Here's how to get involved:
- Fork this repository
- Create a feature branch:
git checkout -b feature/your-feature - Commit your changes:
git commit -m 'Add your feature' - Push to the branch:
git push origin feature/your-feature - Open a Pull Request
Please open an Issue first for major changes so we can discuss the approach.
This project is licensed under the MIT License β see the LICENSE file for details.
Built with β€οΈ by the WUZEN Team β 2026
If this project helped you, consider giving it a β β it helps more people find it!

























