← Back to Documentation

Security and going to production

<TextField> needs PHP 8.4 and nothing else. No Composer packages, no build step, no external service to configure. The less there is to install, the less can break between your machine and the server.

The first time you open the panel, there's no default password to remember or change. You create the administrator account on the spot: username, email address and password (8 characters minimum). The password is stored as a salted hash, never in plain text. Later logins check that hash with a constant-time comparison, and repeated failures are locked out for a growing delay, which makes brute-forcing the password impractical.

Two settings matter when a site is ready to go live, both in Settings › System. Developer mode lets you change the data structure (files, fields, flows). You need it while building a theme, and you should turn it off before the site goes public: the panel then refuses those actions, even from a hand-crafted request. The cache keeps a copy of each page so it can be served without being rebuilt. Every save in the panel clears it, so the site stays fast and your changes show up right away.

Anything that writes to disk (saving a field, uploading a file, renaming a page) goes through the same session check and a CSRF token, with a per-install cookie marked HttpOnly and, on an HTTPS site, Secure. Every redirect the panel issues is checked against the current host first, so a crafted link can't send a logged-in admin off to another domain.

None of this is new. These are the precautions any small admin panel should take. The difference is that they apply to every action, not only to the ones someone remembered.