Laragon is licensed Windows software for running local web application stacks. It manages web servers, databases, and language runtimes through a desktop interface. PHP, Node.js, and Python projects can share that environment, while profiles separate stacks that need different component versions.
Server controls
The main window provides Start All and Stop All commands, alongside individual service controls. Laragon manages these processes through its own orchestration rather than Windows services. Preferences determine which services participate and which ports they use. Startup options can launch Laragon with Windows and start the selected services automatically.
Web, Database, Terminal, and Root buttons open the corresponding working destinations. The interface also identifies a service that another process already runs, including that process’s path.
Projects from templates
Quick app takes a project name and a template, then creates a local project. Its configuration combines several ways to obtain application files: WordPress uses an archive, while Laravel and Symfony entries invoke Composer commands. A blank template creates an empty project instead.
The template file also controls automatic database creation. After creation, Laragon offers commands to explore the project folder or visit its local site. An existing project name triggers an error rather than silently replacing that directory. The separate Clone command starts from an existing project and includes database cloning.
Local hostnames
Projects live beneath a configurable document root. With automatic virtual hosts, placing a project folder there and reloading Apache creates a corresponding local hostname. Laragon writes the matching hosts-file entry and Apache virtual-host configuration. A hostname pattern controls the address, such as app.test.
Hosts-file restrictions can temporarily disable this automation. Local HTTPS has its own interface switch and certificate generation. A separate command adds laragon.crt to the Windows trust store. For sharing a local project, the Ngrok integration creates a tunnel and copies its link to the clipboard.
Component choices
Laragon can manage Apache or Nginx and accommodate additional language runtimes and database servers. Component menus provide version selection. Adding another component directory beneath its bin folder extends the environment without replacing the entire stack.
Tools > Quick add offers packages through a configurable list of download addresses. Its entries cover runtimes, servers, database tools, and other development utilities. PHP also has an automatic update option that detects and adds newer releases.
Profiles group environments with different component versions. Users create a named profile and switch profiles through the menu, rather than selecting every component again individually.
Database work
The database controls create a database by name and change the MySQL root password. A retrieval command copies the root password to the clipboard. Laragon also provides menu access to phpMyAdmin for browser-based database work.
Automatic backup copies the data directory on a configurable schedule. Backup all databases runs an on-demand database backup, and the backup-folder command opens the resulting destination.
Mailpit capture
Laragon configures PHP and Mailpit together for local mail testing. When an application calls PHP’s mail function, Mailpit catches the message for inspection. The email button opens Mailpit’s web interface. Mailpit must run before this capture workflow can operate.
Terminals and custom processes
The Terminal button opens Cmder. Tools > PATH > Add Laragon to PATH exposes bundled PHP, Node.js, and Python to other terminals, editors, and IDEs. Laragon updates those paths when users change a service version or profile.
Procfile entries extend process management with user-defined commands. Each entry can name a working directory, supply environment variables directly, or load them from an environment file. The autorun option launches the command when Laragon starts. A companion configuration places custom commands in the Tools menu.
The complete Laragon folder remains portable between locations and computers. Moving that directory carries the local environment together, including its project and configuration folders.
