Build lil-terminal

Every download is one small self-extracting lil.php. Bare Core installs only the core; presets can also carry setup.lil, which installs the selected modules from the official repository after the first start.

License

Personal noncommercial use is free. Commercial and organizational use includes a 40-day evaluation and then requires a deployment license.

Review licensing and pricing →

Quick download

Bare core

Core only; authorization adds its key and required kill module.

++Files & archives

Files, metadata, editing, transfer, checksums and archives.

Quick builds use Base UI, authorization, this language and Latest. The package completes its first setup automatically; change the default admin password before normal use.

Customize build

Choose a working profile, language, interface, authorization and version strategy.

Toolkit
Build

Latest resolves module versions during setup. Locked records exact versions in setup.lil. Base or Minimal changes only the core interface. Web integration guide

PHP 7.4
Legacy build

Connect the web-terminal after downloading

The selected web profile changes only how the terminal is opened from your site. Command execution still happens inside the same authorized lil-terminal core.

01

Standalone

Open lil.php directly. No changes to the site template are required.

https://example.com/lil.php
Details in FAQ →
02

JavaScript integration

Add lil.js once with defer. The terminal can then be opened from any page with the web-terminal shortcut.

<script src="/lil.js" defer></script>
Details in FAQ →
03

Protected PHP integration

Include the generated PHP gateway on the server. No terminal markup is exposed until the private activation URL enables the current session.

<?php if(is_file($f=$_SERVER['DOCUMENT_ROOT'].'/.<generated-id>/web.php')) require $f; ?>
Details in FAQ →

The protected directory name and token are generated independently for every download. They reduce discovery but do not replace password authorization or HTTPS.

Web integration guide → · Open the full FAQ →