# RaspAP: a Debian wireless router web GUI, installed with one curl command

> RaspAP wraps hostapd, dnsmasq and lighttpd in a PHP web interface for Raspberry Pi and other Debian-based boards. It is the fastest path to a working access point, and it is a configuration layer, not a router OS.

**RaspAP/raspap-webgui** — The easiest, full-featured wireless router setup for Debian-based devices. Period.

- Repository: https://github.com/RaspAP/raspap-webgui
- Website: https://raspap.com/
- Stars: 5,225 · Forks: 846
- Language: PHP
- License: GPL-3.0
- Published: 2026-09-23 · Updated: 2026-09-23 · Language: en
- Canonical page: https://hysenlabs.com/projects/raspap-raspap-webgui

## What RaspAP actually solves, and for whom

A Raspberry Pi with a wireless adapter can be an access point, but getting there by hand means editing hostapd.conf, writing a dnsmasq range, giving the wlan interface a static address, and making sure the services come back after a reboot. RaspAP exists to collapse that work into an installer and a browser interface. The README describes it as "feature-rich wireless router software that just works on many popular Debian-based devices", and the repository topics list the components it drives: hostapd, dnsmasq, lighttpd, plus armbian, kali-linux and orangepi alongside Raspberry Pi.

The audience is narrow and practical. Someone who wants a travel router, a lab AP, an IoT gateway or a small hotspot and is comfortable on a Debian shell. The README points to pre-built Raspberry Pi OS Lite images for 32-bit and 64-bit ARM, which removes the guesswork for the most common board. If you already run a router OS with a hardware switch and a vendor support contract, RaspAP is not competing for that slot.

## The stack underneath the dashboard

RaspAP is a PHP application served by lighttpd. The top level of the repository shows the shape of it: index.php as the entry point, app/ and includes/ for application code, ajax/ and api/ for the browser-facing endpoints, config/ for the files the UI writes, installers/ for the setup scripts, locale/ for translations, and plugins for user extensions. package.json names the front-end build as gulp with jQuery and the startbootstrap-sb-admin-2 theme, and the project title there is "RaspAP WiFi Configuration Portal".

That layout tells you what kind of tool this is. The web GUI does not route packets itself. It writes configuration for hostapd (the access point), dnsmasq (DHCP and DNS), and the Debian networking layer, then restarts those services. When something misbehaves, the failure usually lives in one of those daemons, not in the PHP. The default AP network is documented as 10.3.141.1, which is also the address you reach the interface on after installation. Optional pieces sit on the same pattern: WireGuard, Tailscale and OpenVPN support, SSL certificates, ad blocking, captive portal integration, themes and multilingual options are listed as included features, each backed by a service RaspAP configures rather than replaces.

## Installing RaspAP and reaching the login page

The README gives two routes. The recommended one is the pre-built image: download the 32-bit or 64-bit Raspberry Pi OS Lite image with RaspAP preinstalled from the latest release page, flash it with Raspberry Pi Imager or balenaEtcher, boot, and the AP plus the most popular optional components are already active. The alternative is the Quick installer on an existing compatible OS. Start from a clean Raspberry Pi OS release, update it, and reboot:

```bash
sudo apt-get update
sudo apt-get full-upgrade
sudo reboot
```

Set the WiFi country in raspi-config's Localisation Options with `sudo raspi-config`. Skipping this is a common reason an AP refuses to come up, because the regulatory domain is unset. Then run the installer from the device's shell prompt:

```bash
curl -sL https://install.raspap.com | bash
```

The README states that the installer accepts command line arguments, documented at docs.raspap.com/quick/, to customise the installation or add optional helper tools. After either route completes, the wireless AP network is configured with IP address `10.3.141.1`. Point a browser at that address from a client joined to the new AP and the dashboard loads, with the WiFi client, hotspot, adblock, WireGuard and system pages shown in the README screenshots. The README does not document the default credentials in the excerpt available here; check the project documentation before exposing the interface.

## Where RaspAP is the wrong tool

RaspAP manages services on a general-purpose Linux host. It does not replace the kernel's forwarding path, and it does not give you the hardware offload or the switch fabric of a purpose-built router. If you need to push hundreds of megabits through NAT while running a VPN tunnel, a Pi will be the bottleneck, and no setting in the web GUI changes that. The README makes no throughput claims, and none should be assumed.

The second limitation is lifecycle. The installer writes into system configuration directories and enables services. The README's contents list covers installation, supported operating systems, Docker, plugins and translations, but it does not document uninstall or rollback. If you install RaspAP on a machine you also use for other things, you are changing its networking stack, and reversing that is a manual exercise in the files under installers/ and config/. The project does ship a Docker container, which is the cleaner option when you want the interface without committing the host.

Third, the interface is a control surface over daemons that can be edited outside it. Hand-edit hostapd.conf and the GUI's view of the world may diverge from what is actually running. That is inherent to the design, not a bug, but it means RaspAP suits single-operator devices better than shared infrastructure.

## RaspAP compared with OpenWrt

The obvious alternative is OpenWrt, and the difference is architectural rather than cosmetic. OpenWrt is a complete Linux distribution built for routers: its own package manager, its own configuration system (UCI), its own web interface, and a build system that targets specific router hardware. RaspAP is an application layer on top of Debian. It inherits Debian's package management and update path, which is familiar, and it inherits Debian's general-purpose networking stack, which is not tuned for routing.

In practice this means the choice follows your hardware. If you have a supported router, OpenWrt gives you a system designed for that job, with VLANs, firewall zones and a configuration model that survives upgrades. If you have a Raspberry Pi, an Orange Pi or an Armbian board already running Debian, RaspAP turns it into an AP without reflashing anything and keeps the rest of the Debian environment available. The other comparison worth naming is plain hostapd plus dnsmasq with no GUI at all. That is less work to maintain and less to break, and it is the right answer if you set the AP up once and never touch it again. RaspAP earns its place when you change settings often, or when the people changing them are not shell users.

## Licence, maintenance and the cost of upgrading

RaspAP is GPL-3.0, stated in package.json and in the repository's LICENSE file. For most users of a self-hosted AP this changes nothing. It matters if you plan to redistribute a modified RaspAP inside a product: GPL-3.0 carries source disclosure and licence compatibility obligations, and this article is not legal advice, so read the licence text and take your own counsel before shipping anything derived from it. The project also runs an Insiders sponsorship tier, linked from the README badge; nothing in the README states what that tier changes about the licence, so treat it as a funding channel rather than a licence variant until the documentation says otherwise.

Maintenance looks current rather than dormant: the last push to master was on 2026-09-19, and releases 3.5.5, 3.5.4 and 3.5.3 landed on 2026-07-07, 2026-05-30 and 2026-03-23 respectively. The upgrade cost is the part to plan for. The pre-built images are regenerated with each release, so a fresh flash is the low-friction path. On an existing install, the Quick installer is the documented mechanism, and because it writes into system configuration, an upgrade is not a package swap you can trivially reverse. Back up the files under config/ before running it.

## Conclusion

Adopt RaspAP if you want a Raspberry Pi or similar Debian board acting as a wireless access point with DHCP, VPN and ad blocking configurable from a browser, and you accept that you are managing a set of Debian services rather than flashing a router firmware. Skip it if you need line-rate routed throughput, VLAN segmentation or a vendor-supported appliance; a dedicated router platform is the better fit there. Before committing, verify on your own hardware that the onboard wireless adapter supports AP mode, and read installers/ to see exactly which files the installer touches, because the README does not document how to remove them.

## FAQ

### How do I set up RaspAP?

Either flash a pre-built Raspberry Pi OS Lite image with RaspAP preinstalled from the latest release page, or start from a clean Raspberry Pi OS install, update it, set the WiFi country in raspi-config, and run the Quick installer with curl -sL https://install.raspap.com | bash. After setup the AP network uses the address 10.3.141.1.

### How do I completely remove RaspAP?

The README does not document an uninstall or rollback procedure, so there is no supported removal command to quote. The installer writes into system configuration and enables services, which means reversing it is a manual exercise in the files under installers/ and config/; the Docker container avoids committing the host in the first place.

### What are the key differences between RaspAP and OpenWrt?

OpenWrt is a complete Linux distribution built for router hardware, with its own package manager and configuration system. RaspAP is an application layer on top of Debian that configures hostapd, dnsmasq and lighttpd, so it keeps the Debian environment intact and targets boards like the Raspberry Pi rather than dedicated routers.

## Sources

- [License: GPL-3.0](https://github.com/RaspAP/raspap-webgui/blob/master/LICENSE)
- [Project website](https://raspap.com/)
- [RaspAP/raspap-webgui on GitHub](https://github.com/RaspAP/raspap-webgui)
- [README](https://github.com/RaspAP/raspap-webgui/blob/master/README.md)
- [Releases](https://github.com/RaspAP/raspap-webgui/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/raspap-raspap-webgui