How to use the sPremium toolset with an AI assistant
sPremium is Noiz shared hosting with a developer toolset: a dedicated PHP pool, your choice of PHP version, SSH, Git, Node.js, Ruby and WP Toolkit staging, with scheduled tasks in the Plesk panel. This page explains what each tool is for, gives one worked example, and gives a prompt you can hand to an AI assistant so that it can guide you or do the work with you. Use it as a map; each section links the full how-to.
Last reviewed: 19 October 2026, against Plesk Obsidian and WP Toolkit on Noiz sPremium hosting.
Official Documentation Reference
- Plesk Customer Guide: Git, remote repositories
- Plesk Customer Guide: Node.js
- Plesk Customer Guide: PHP settings
- Plesk Customer Guide: Scheduled tasks
- WP Toolkit (Plesk Customer Guide)
The tools at a glance
| Tool | Where in Plesk | Use it for | Guide |
|---|---|---|---|
| Dedicated PHP pool | Set up by Noiz on every sPremium plan | Your sites' PHP workers are yours alone | This page |
| PHP version and settings | PHP Settings under the domain | Matching what a plugin or application needs | Change the PHP version |
| SSH (limited to your own account) | Hosting & DNS > Hosting | Reading files and logs, and SFTP, for an AI coding tool | This page |
| Git | Git under the domain | Deploying code from a repository | Plesk: Git |
| Node.js | Node.js under the domain | Running a JavaScript application | This page |
| WP Toolkit | WordPress | Staging, cloning, copying data, backups, security | WP Toolkit (Plesk guide) |
| Scheduled tasks | Scheduled Tasks under the domain | Running a job on a timetable | Create scheduled tasks |
The dedicated PHP pool
On sLegacy, sites share one pool of PHP workers on the server. On sPremium, your sites get a PHP-FPM pool of their own, so a neighbour's traffic cannot take the workers your checkout needs. There is nothing to set: it is how your plan is built.
Worked example. A shop runs a large catalogue import every night. On a shared pool the import competes with every other site; on your own pool it competes only with your own visitors.
Ask your assistant: "My WooCommerce shop slows down during a product import. Given that my site has a dedicated PHP-FPM pool, what should I check first, and how do I schedule the import for a quiet hour?"
PHP version and settings
Each site can run the PHP version it needs. Some plugins require a recent version; an older application may need an earlier one while you upgrade it.
Worked example. A plugin update says it needs a newer PHP version. In PHP Settings, you check the current version, switch the staging copy first, test it, then switch the live site.
Ask your assistant: "My site runs PHP 8.2 and a plugin now requires 8.3. Give me a checklist to test the change on a staging copy first, including what to look for in the error log."
Use View the phpinfo() page in PHP Settings to show the assistant the effective settings, after removing anything that looks like a path or a key you would not publish.
SSH
SSH on sPremium gives you a shell limited to your own hosting account, for reading files and logs and for SFTP. For PHP versions, Git, Node.js and WordPress tasks, use the tools in Plesk described below.
Worked example. A page shows a white screen. Over SSH, you read the last lines of the domain's error log and find the plugin that failed.
Ask your assistant: "Over SSH, show me the last 50 lines of my domain's error log, explain the most recent fatal error and tell me which plugin caused it. Do not change any files."
Git deployment
Git keeps every version of your code and deploys a chosen version to the site. Plesk pulls from a repository on GitHub, GitLab or similar, either automatically when you push, through a webhook, or when you click Deploy.
Worked example. You keep a child theme in a private repository. Each push to the main branch deploys it to wp-content/themes/your-child-theme. When a change goes wrong, you deploy the previous commit.
Ask your assistant: "Set up this child theme as a Git repository with a sensible .gitignore, and write the steps to connect it to Plesk's Git with manual deployment to httpdocs/wp-content/themes/my-child-theme."
Node.js
Plesk runs Node.js applications for a domain: you choose the Node.js Version, the Application Root and the Application Startup File, then use NPM install and Restart App.
Worked example. A small booking widget written in Node.js runs on a subdomain such as book.yourdomain.com. After each deployment through Git, you click NPM install and Restart App.
Ask your assistant: "Write a minimal Node.js application that serves a health-check page at /health, with a package.json and a startup file called app.js, ready for Plesk's Node.js panel. Explain each setting I need to enter."
WP Toolkit
WP Toolkit manages each WordPress site from one card: Clone makes a staging copy, Copy Data moves files or database tables between copies, Back up / Restore keeps backups of the site, and the security check shows which recommended protections are missing (Fix security or Check security on the card).
Worked example. Before a major WooCommerce update, you clone the shop to staging.yourdomain.com, update there, test a checkout, then update the live shop.
Ask your assistant: "Give me a step-by-step test plan for a WooCommerce major update on a staging copy: what to update in which order, which pages and payments to test, and what to compare before I update the live site."
Treat WP Toolkit's security measures as you would any change: back up first, apply them on staging, and check the site still works. Some measures cannot be reverted.
Scheduled tasks
Scheduled tasks run a job on a timetable: Run a command, Fetch a URL or Run a PHP script. Run Now tests a task before you rely on it. Noiz's acceptable use policy allows a task to run no more often than every two hours.
Worked example. WordPress normally runs its scheduled jobs when someone visits the site, so a quiet site misses them. You set define( 'DISABLE_WP_CRON', true ); in wp-config.php, and add a Fetch a URL task for https://yourdomain.com/wp-cron.php every two hours.
Ask your assistant: "My WordPress site's scheduled posts sometimes publish late. Explain how to move WordPress cron to a Plesk scheduled task that fetches wp-cron.php, what to put in wp-config.php, and why it should run no more often than every two hours."
Troubleshooting
- A tool is missing from the panel. Your subscription is on sLegacy, which does not include SSH, Git or Node.js, or the tool sits under a different tab in your panel layout. Check your plan in the console.
- A scheduled task does not do what you expect. Check the path to the command, as the Plesk guide explains, and use Run Now to test it.
- A Node.js application will not start. The startup file name or the application root does not match what is in the repository. Check both in the Node.js panel and click Restart App.
If you are on sLegacy
These tools are what sPremium adds to sLegacy. Compare the plans, or ask us which fits your site.
