Webinoly is a GPL-3.0, Shell-based command-line tool that turns a fresh Ubuntu server into a production LEMP stack — NGINX, MariaDB or MySQL, and PHP — in a single step, built for PHP and web developers who run their own servers from the terminal.

What it is

Webinoly is a provisioning and management layer for Ubuntu servers that assembles a complete LEMP stack and then exposes the everyday operations of that stack as terminal commands. It sits in the Linux server-administration ecosystem, alongside the components it installs and configures: NGINX, MariaDB or MySQL, PHP-FPM, Redis, and Certbot for Let's Encrypt certificates. The stack can be deployed whole in one step, or installed as individual packages when only part of it is wanted.

The concrete problem it solves is the manual, file-by-file assembly of that stack. Rather than editing NGINX server blocks, wiring PHP-FPM, issuing certificates by hand, and tuning a FastCGI cache separately, an operator runs a small set of commands and gets a configured server. The same command surface covers the tasks that usually follow a deployment: creating sites, adding HTTP authentication, configuring a reverse proxy, cloning a server for migration, and reading logs in real time.

Key capabilities

• One-step stack provisioning through curl -sSL qrok.es/wy | sudo bash, which builds the full LEMP stack, with individual packages available separately.
• Site creation commands such as sudo site example.com -wp, which provisions a WordPress site, alongside WordPress-specific options for subfolder installs, an external database, multisite, and domain mapping.
• Free TLS certificates via Let's Encrypt and Certbot, with configurations that reach an A+ grade on the Qualys SSL Labs test.
• A performance layer built from FastCGI Cache and Redis Object Cache, with HTTP/3 support.
• Access control through HTTP Authentication, managed with sudo httpauth -add, plus custom header management.
• Reverse proxy support for application servers written in Java, Node, React, and Vue.
• Operational tooling: full site and server cloning and transfer for backup and migration, a real-time log viewer, a redirection manager, and SMTP support.

Who uses it and how

• Operators of small single-server deployments, since the stated minimum is 512 MB of RAM on arm64 or x86_64 running Ubuntu 24.04 or 26.04.
• WordPress-focused teams that need multisite, domain mapping, subfolder installs, or an external database without hand-writing NGINX configuration.
• Developers running Node, React, Vue, or Java application servers behind the reverse proxy while NGINX handles TLS termination and caching.
• Teams moving a site or an entire server to new hardware using the cloning and transfer tools rather than a manual rebuild.
• Bilingual teams, as the documentation is maintained in both English and Spanish.

Getting started

Installation is a single shell command: curl -sSL qrok.es/wy | sudo bash, which installs Webinoly and builds the stack. From there, sudo site example.com -wp creates a first WordPress site and sudo httpauth -add adds authentication.

How it compares

No comparable or paid products are named in the facts provided for this entry, so Webinoly stands alone in this registry on that basis. Its distinguishing characteristics as recorded here are its GPL-3.0 licence, its terminal-first interface, and its focus on a single Ubuntu server rather than a managed or hosted service.

When to use it — and when not

Choose Webinoly when the target is a single Ubuntu 24.04 or 26.04 server and the operator is comfortable owning the stack: MariaDB or MySQL, PHP-FPM, Certbot certificate renewal, Redis, and SMTP for mail all become that operator's responsibility to run and maintain. It is not a fit for anyone on a different distribution, since the requirements name only Ubuntu, nor for teams that want a control panel or a managed platform rather than commands. The repository README is a short summary that defers the details to the external documentation site, so evaluating specifics means leaving the repository, and the project's issue count is small enough that community support rather than a large maintainer team should be assumed.

</a></p>

# Install Webinoly and build the stack
curl -sSL qrok.es/wy | sudo bash

# Create your first WordPress site.
sudo site example.com -wp

# Authentication
sudo httpauth -add