Turbo

Turbo is a fast web server that pairs the engine with a real-time visual control panel, so you can host multiple sites and manage their configuration through a browser instead of hand-editing files. It's aimed at anyone running a VPS or bare-metal box who wants nginx-style capability without living in config syntax, and it runs on both Linux and Windows. The whole thing ships as a single self-contained binary written in Go, with no runtime to install alongside it, and the source lives at github.com/okzgn/turbo-go. There's no fixed limit on how many sites or subdomains a single instance can carry, so one box can hold as much as it has room for.

The core idea is that the things you normally tweak in a text file live in a web admin panel that applies changes live. You point a browser at /admin on your server, sign in with credentials you control, and manage domains, certificates, and routing from there. The panel is meant for real-time edits, and it closes idle sessions after a minute of inactivity as a small safety measure. Default admin credentials ship as a starting point, and you can set them along with the site directory through the TURBO_USER, TURBO_PASSWORD, and TURBO_DIR environment variables, so changing them is the first thing you'll do after install.

The panel is organized around the pieces you actually manage. General settings let you change the admin login and the site directory, request-timing controls cover how long the server spends reading headers, processing a whole request, writing a response, and holding a connection open, and a rate-limiting section caps request frequency per IP address. Size limits guard the maximum URI length, header size, and content body, each answering with the matching HTTP status when a request runs over. Site management lets you add a site as localhost, an IPv4 address, or a multilevel domain with wildcards, and each subdomain gets its own indexes, MIME types, headers, rewrites, and preprocessors, so a single server can hold sites that behave nothing alike.

On the routing and delivery side, Turbo handles multilevel domains and subdomains, alias addresses, redirects between the root and www forms, and URI rewrites that can do dynamic keyword replacement without a redirect, plus custom MIME types and HTTP headers by file extension. SSL is wired to Certbot, so you can create, manage, and delete certificates, cover wildcards, and turn on automatic HTTPS redirection, with renewals handled for you rather than left to a cron job you forget about. Multiple programming languages are supported through CGI-based preprocessors, so dynamic sites aren't limited to static files, and you can cap upload sizes or even replace a site's content by uploading files straight from the panel.

The point of all this is to keep the common web-server chores in one place. Instead of editing a config file, reloading the server, and hoping you didn't fat-finger a directive, you make a change in the panel and it takes effect, and Turbo writes the whole configuration to a file in your sites directory so it survives a restart. Optional logs record rate-limit denials and general visits in separate files, or fall back to stdout if you'd rather not keep them on disk. For someone running a handful of sites on a single box, that turns a fiddly, error-prone routine into a few clicks, without having to memorize a particular server's configuration language just to get TLS, redirects, and rewrites working.

Because it's a single self-contained binary, setup is light. On Linux it targets 64-bit x64 and ARM64 systems with systemd and expects common tools like nano and wget, and on Windows it runs on Windows 10 or Server 2016 and newer, 64-bit only, with administrator rights and PowerShell. The downloads are tiny, around 6 MB on Linux and 8 MB on Windows, published on GitHub with SHA256 checksums, and the project lists a modest 128 MB of RAM as a recommended minimum, so it's comfortable on small instances. You download the executable, set permissions or open ports 80 and 443, optionally register it as a service, on Windows through a wrapper like WinSW or NSSM, and start it, and from then on the panel does the rest.

Turbo suits developers and system administrators who manage a few sites and want SSL, redirects, and rewrites handled from one place rather than scattered across config files and cron jobs. It's less of a fit if you need the plugin ecosystem, tuning depth, and long track record of a server like nginx or Apache. The project uses a dual license, an open-source build under the GNU Affero General Public License v3 and a separate commercial license for proprietary use through the maker's contact page. It's currently at version 2.3 release candidate, so it's usable today while still stabilizing toward a final release, and the site is largely written in Spanish, which is worth knowing before you dig into the docs.