Knowledge Base
Frequently Asked Questions
Authoritative answers regarding hosting compatibility, architectural choices, security boundaries, and licensing policies.
What is Encrypt CMS and how does it differ from WordPress or Node-based CMSs? ↓
Encrypt CMS is a modern, installable content management system built with native PHP 8.2+, MySQL/MariaDB PDO, server-rendered templates, and vanilla JavaScript. Unlike heavy JavaScript or containerized platforms, it requires zero Node.js processes, build tools, or root access on production. Unlike legacy CMS platforms, it features strict PDO prepared statements, Ed25519 asymmetric licensing, automated rollback updates, and a decoupled architecture.
Can Encrypt CMS run on shared hosting like 20i StackCP or cPanel? ↓
Yes, absolutely. Encrypt CMS was specifically engineered for shared hosting compatibility, including 20i StackCP, cPanel, Plesk, and standard Apache/Nginx web servers. It operates within standard shared hosting memory limits (128 MB+) and requires no special daemon processes.
Do I need Node.js, npm, or Composer on my production server? ↓
No. Encrypt CMS ships with a built-in PSR-4 autoloader (App\Core\Autoloader). You do not need Node.js, npm, Vite, or Composer on your production hosting account. Deployment requires only uploading the release archive and extracting it into your web root.
Is Encrypt CMS Core free to use? ↓
Yes. The Encrypt CMS Core (content management, full-page editor, media library, users, roles, native SEO, system health, and core security updates via CoreUpdateService) is completely license-free. Only commercial add-ons and premium ecosystem extensions require licensing verification through the Central License Server.
How does the Central Licensing System (CLS) work for extensions? ↓
The Central License Server (CLS) uses Ed25519 asymmetric cryptography. When activating a commercial license, the CMS receives digitally signed tokens verified against a local public key trust store. Status is securely cached locally for 48 hours.
What happens to my website if the licensing server is offline or unreachable? ↓
Your website will continue running normally. Encrypt CMS features an authorized 14-day offline grace window. If the licensing server is unreachable when the 48-hour local cache expires, commercial features remain fully active for 14 days, preventing transient network outages from interrupting live sites.
How does Encrypt CMS prevent SQL injection and security attacks? ↓
All core database interactions strictly use parameterized PDO prepared statements with emulation permanently disabled (PDO::ATTR_EMULATE_PREPARES => false). User input is never concatenated into SQL strings. The CMS also implements cryptographically random CSRF tokens, brute-force rate limiting, context-aware HTML entity escaping ($e()), and directory traversal (Zip Slip) defenses.
How do in-dashboard updates work? ↓
Administrators can check for updates in Admin > System > Updates. Downloaded update packages are verified against authoritative SHA-256 checksums before any file extraction occurs. The system creates an atomic pre-update backup and automatically rolls back if file extraction or manifest verification fails.
How can I request a license for commercial extensions or client projects? ↓
You can submit your contact details via the "Request License" button found in the navigation bar, footer, and dedicated page CTAs. Our team reviews submissions and guides you through commercial addon deployment.
Have a specific architectural or licensing question?
Our team is available to discuss custom enterprise requirements, hosting compatibility, and extension specifications.