Questions and answers

A website engine in PHP. It installs on ordinary hosting by unpacking an archive, and from then on everything is managed from the panel: updates, modules, appearance — no editing of files. It suits a company site, news, a catalogue, a forum, a shop: all of these are modules, and anything you do not need is switched off with one button.

PHP 8.2 or newer and MariaDB 10.4+ or MySQL 8.0+. No SSH, Composer or Node required. Ordinary shared hosting is fine.

The interface comes in seven languages: English, Russian, Ukrainian, Norwegian, Polish, Swedish and Lithuanian (since release 0.9.8). The language is chosen from a list in the site header; every record has its own language and address.

The engine ships as source code, and on your own site you may read and change it, and write your own modules and themes. You may not pass it on to others or sell it under your own name — the details are in the licence agreement.

Yes, in full: every bundled module, every theme, the panel, the installer — with no time limit. A licence key only unlocks updates of the engine and the modules, and support. You can try it before buying.

Updates of the engine and the modules from the panel, downloading archives on this site, and support on the forum — for the whole term of the licence. The key goes into the panel under "Settings → General → Updates → Licence key".

One domain together with its subdomains. A fresh key is tied to nothing: it is claimed by the first site that comes for an update. A second site needs a second key. Moving to another domain — write to us and we will release the key.

Nothing dramatic: the engine keeps working, nothing is switched off or locked. Only updates of the engine and the modules from our server stop arriving. Renewing brings them back.

In the shop on this site. After purchase the key is sent by e-mail to the address you gave and is shown in your profile; enter it in the panel of your site. Questions about buying — support@nex1on.com.

Unpack the archive on the hosting and open the site in a browser. The installer first asks for the installation code from the file storage/install-code.txt (open it by FTP), then asks for the language and country, checks the server, asks for database access, creates the owner's account and offers to choose what kind of site it is: the kind decides which modules are switched on at once. After that the site is ready; if the kind did not fit, undo it in “Modules”.

From the panel: "Updates → Engine". The engine finds out about a new version itself, with the "Review and update" button shows a check screen (what is new, whether the server fits, whether you changed engine files), and "Update" then goes step by step with percentages: it downloads the archive, checks its signature, makes a database backup and a restore point, replaces the files and updates the database. If the site stops answering after the files are replaced, the previous version comes back by itself; it is worth keeping the recovery key the page shows. The full procedure is in the topic "How to update NEX1ON properly".

"System → Diagnostics → Database backups": a backup is made by a button and on a schedule (settings "every how many days" and "how many to keep"). Before an update the engine makes a backup itself. Backups can also be sent off the server, encrypted — "Copies off-site" (S3 storage or WebDAV). You restore a backup on the "Database backups" page: choose the file, type its name and confirm with your password.

Move the files and the database, then adjust config/database.php. The engine is not tied to a domain: it builds addresses from the name it was reached by. If the site updates by key — write to us so we release the key from the old domain.

The modules of the distribution already lie in the modules folder together with the engine: "System → Modules" → "Install and enable". A module that is not in the distribution is put into modules as files or taken from "Add-ons" (the "Install" button downloads the archive from our server and verifies the fingerprint). There is no upload of a module archive through the panel — and there will not be, it is a security hole.

Its pages, menu item, blocks and settings disappear from the site; the data stays in the database. Enable it — everything comes back. Only deleting a module removes its data, and for that you have to type the module's name by hand.

"Appearance": theme, colours, fonts, corner rounding, block placement, menus and the home page are edited from the panel without touching style files. Values are stored separately for each theme, so switching back and forth loses nothing. Your own theme need not copy the engine's templates: it changes only what it wants to.

Yes. The module:new command makes a skeleton: manifest, routes, migrations, permissions, translations. A module hooks into the engine through events and needs no changes to the core. Check it before release with module:check. Questions — in the forum section "Module development".

On the forum: the studio answers there, and the answer stays for others. There is a section for each module in the "Modules" category. How to report a bug so it gets fixed quickly — in a separate topic.

Passwords are stored as hashes, there is two-step sign-in, guessing attempts are limited, files in the media library are rebuilt, nothing runs in the uploads folder, modules cannot be installed by uploading an archive. "System → Diagnostics → Security" shows it all as a list with links to where to fix things. Report a vulnerability to support@nex1on.com, not on the forum.

Only when checking for updates: the domain, the engine version, the PHP version and the licence key. No site content, no visitor data. The check can be switched off: "Settings → General → Updates → Check for updates → never".