Master
Expanded plan for active projects.
CMS, online stores, development, SSH, and higher load.
Included
- 4 GB Disk Space
- 20 domains
- 60 sites
- 60 databases
- 60 mailboxes
- 60 FTP users
- Free Let's Encrypt SSL certificates
- SSH access
- One month free
Deploy a modern PHP application on prepared hosting: a full SSH shell, Composer and Git, Node.js for frontend builds, a custom site document root and the same PHP version for the site, the console and cron. Works for Laravel, Symfony, Yii and any Composer application — bring your own repository and deploy your project.
Pick a PHP version per site; it is identical for the web server, the SSH console and cron jobs.
Besides MySQL 8.0 with phpMyAdmin you also get PostgreSQL — a rarity on shared hosting.
nvm with any Node version, npm, yarn and pnpm via corepack, plus a global Composer.
Master and Expert plans with SSH and developer tooling — cheaper and simpler than a VDS.
Frameworks
The hosting targets applications structured like a modern PHP project: your own repository, Composer dependencies, a public directory separated from the code. The list is open-ended — anything installable with composer install works.
artisan commands, scheduler via cron, Vite builds, storage:link, migrations — plus a ready-made environment preset at checkout.
bin/console, the public directory as the web root, Composer dependencies, cron for periodic commands.
The web directory as the document root, yii console commands, runtime directories with proper permissions.
And any other Composer application without a specific framework — the environment is universal.
Boxed products with license checks and web installers are a different story: check the requirements with our support before ordering.
Any subfolder of the project can be set as the site document root — public for Laravel and Symfony, web for Yii, or anything else. Source code, configuration and dependencies stay above the document root, out of the browser’s reach.
project/ ├── app/ ├── config/ ├── vendor/ ├── storage/ ├── .env ← outside the web root └── public/ ← document root └── index.php
Master and Expert plans include a full shell, not just a file manager. The console PHP version matches the site’s, so composer install and framework console commands run without surprises.
A global Composer is available right away: install, update, dump-autoload — with the project’s platform requirements checked.
Clone a private repository over an SSH deploy key and update the project with git pull. Or skip the console entirely: the hosting panel has a “GitHub import” module.
php in the console is the same version as the site. artisan, bin/console and yii run as intended.
tar, unzip, rsync, ln, curl and SSH keys for login — migrate and deploy your project with standard tooling.
git pull composer install --no-dev --optimize-autoloader npm ci && npm run build php artisan migrate --force php artisan optimize
Node.js on hosting is for building assets — Vite, Webpack or Mix. Install the Node version you need via nvm; npm is bundled, yarn and pnpm are enabled through corepack. A classic PHP project does not need a permanently running Node server: the build runs as a command and produces static files.
nvm install --lts corepack enable npm ci npm run build
If your project needs a permanently running Node.js process (SSR, a WebSocket server), that is a VDS scenario.
Cron jobs run at one-minute granularity with the PHP version you need — enough for the Laravel scheduler and periodic Symfony commands. Queues on shared hosting work in a basic mode: cron regularly starts a worker that drains pending jobs and exits.
A single schedule:run cron line every minute — the application’s whole internal schedule works.
queue:work --stop-when-empty via cron: emails, notifications and background jobs with roughly a minute of latency.
Permanent worker processes, Supervisor, Horizon and real-time processing belong on a VDS, not shared hosting.
We deliberately do not promise “full queues” on shared hosting: long-lived processes are restricted there. For small and mid-size projects the cron mode is enough.
Separate databases and users are created per project; dumps can be imported via the console or phpMyAdmin.
The primary DBMS with phpMyAdmin, multiple databases and users, and CLI dump imports.
A full PostgreSQL for Laravel and Symfony projects — rare on shared hosting.
pdo_sqlite is in place — for small applications, tests and local tooling.
file and database drivers for cache, sessions and queues. There is no Redis server on shared hosting — it is available on a VDS.
Checkout option
On Master and Expert plans you can enable the “Prepare a framework environment” option at checkout. We configure the account to a “git clone and go” state: matching PHP versions for the site and the console, the document root pointed at the public directory, a database with credentials, Node.js LTS and a deploy script.
PHP 8.4 for web and CLI, docroot → public, a MySQL database and an .env boilerplate, Node LTS with corepack, laravel-deploy.sh and cron lines for the scheduler and the queue.
For Symfony, Yii and any Composer application: your choice of PHP version and public directory, a database, Node LTS and a universal deploy script.
Enable the “Prepare a framework environment” option in the cart and pick a preset.
Once the environment is ready you get an email: SSH, database, paths. Progress is visible in the client panel.
git clone your repository, composer install, run migrations — or use the ready deploy script from the home directory.
Plans
Two plans fit PHP applications and frameworks — Master and Expert: only they include SSH, Composer, Node.js and the “framework environment” option. For CMS sites that need no console there are simpler plans on the regular hosting page.
All plans include a free Let’s Encrypt SSL certificate with auto-renewal, per-site PHP version choice and support that answers to the point.
Classic hosting targets sites administered through a panel: CMSs, site builders, ready-made scripts. A framework needs a console and build tooling — those come with the Master and Expert plans.
| Feature | Start / Optima | Master / Expert |
|---|---|---|
| CMS sites (WordPress, Joomla…) | Yes | Yes |
| SSH access with a full shell | No | Yes |
| Composer and Git in the console | No | Yes |
| Node.js, npm, asset builds | No | Yes |
| Custom document root | Yes | Yes |
| Cron jobs | Yes | Yes |
| “Framework environment” option | No | Yes |
| Process memory / limits | Basic | 1 GB, up to 100 processes |
For a CMS site with no console needs Start or Optima is enough — frameworks need Master or Expert.
Shared hosting deliberately does not try to be a “miniature VDS”. If your project needs Redis, permanent queue workers, Horizon, a WebSocket server, custom system services or root access — take a VDS: you fully control the stack there, and we can help with the setup.
We can move a working project for you: files, database, domain and SSL — turnkey and without downtime. If you prefer to migrate yourself, we will outline the steps and verify the result. Contact support after ordering — we will agree on timing and access.
FAQ
Yes. The document root can point at any project subfolder — public, web or another one. Code, .env and vendor stay above the web root and are unreachable from the browser.
Composer is installed globally and available right after you log in over SSH: composer install, update and require work without extra setup. No need to install it yourself.
Yes. The console provides a PHP CLI of the same version as the site, so Laravel, Symfony and Yii console commands run normally — manually and via cron.
The same one selected for the site. We align the versions for web, SSH and cron when preparing the environment — the classic “site on 8.4, console on 7.4” problem does not happen here.
In basic mode — yes: cron runs queue:work --stop-when-empty every minute, so jobs are processed with about a minute of latency. Permanent workers and Horizon do not run on shared hosting — they need a VDS.
There is no Redis server on shared hosting — it cannot be offered safely on a shared machine. Use the file or database drivers for cache and sessions; if your project specifically needs Redis, host it on a VDS.
Yes. Node.js installs via nvm (any current version), npm is bundled, yarn and pnpm are enabled through corepack. Memory limits are enough for Vite and Webpack builds.
Yes, PostgreSQL 16 — alongside MySQL 8.0 with phpMyAdmin. The pdo_pgsql and pdo_mysql extensions are enabled.
Yes. Generate an SSH key on the hosting, add it to the repository as a deploy key — and clone over SSH. For GitHub there is an even simpler path — the “GitHub import” module in the hosting panel: a public repository by URL, a private one via a token or deploy key, with branch and site directory selection. There is no out-of-the-box webhook auto-deploy; update with git pull or a deploy script.
Yes, within the plan’s site limit. Each site has its own document root and its own PHP version.
Yes, we can migrate it turnkey: files, database, domain and SSL. Or we will outline the steps if you prefer to migrate yourself.
The standard framework set: mbstring, intl, openssl, pdo_mysql, pdo_pgsql, pdo_sqlite, curl, fileinfo, tokenizer, xml, ctype, zip, gd, imagick, bcmath, sodium, opcache and more. If your project needs something else — write to support and we will enable it where technically possible.
Pick Master or Expert, enable the “framework environment” option — and get an account ready for git clone and composer install. Not sure whether shared hosting fits your project? Write to support: we will tell you honestly whether a shared plan is enough or you need a VDS.