PS Cloud Services in Kazakhstan: WordPress and Plesk backup

Who PS Cloud Services may suit

This profile is based on published offers and documentation. No new hosting benchmark or support test was performed for this translation.

Plans, prices and renewals

Prices retain the market, currency and billing period described in the French source. Translation does not update a commercial quote. Confirm the final price, taxes and options before ordering.

Languages and support

Website and documentation

Russian, Kazakh and English verified for the range.

Control panel

Plesk with a documented Russian interface. Other account and Plesk languages to confirm.

Support

Technical tickets continuously available. Handling languages beyond those of the consulted channels to confirm.

PS Cloud Services in Kazakhstan for keeping an exportable copy

PS Cloud Services offers Plesk shared hosting in Kazakhstan with WordPress support. The provider documents backups created by the team and infrastructure copies managed on its side. This distinction affects the plan. Copies created by the team and stored in the account space consume quota. A fictional Almaty association prepares to leave with a site already close to the limit.

The association wants to retain its documents, database and ability to restore pages elsewhere. It measures active data and files that would coexist during backup. The exercise compares an oversized local package with a fictional quota, writes the package outside the counted volume and compares recovered contents with original file hashes. It illustrates the decision to make before creating an export file beside the active site.

This profile distinguishes shared hosting from WordPress administration. It describes the offer in tenge, the Almaty location named in the SLA, installation in Plesk and the different deadlines to record. To choose, the association examines actual space during export and the ability to open the copy at a separate destination.

Read prices in tenge and renewal terms

On November 10, 2026, the shared-hosting page advertised a starting price of 427 KZT per month. The detailed table is loaded separately. The available public record does not verifiably link that 427 KZT to a reference, resources and a total amount to debit. Calculating 5,124 KZT for twelve months at the same rate gives an arithmetic equivalent. It is not an advertised annual price. Request the reference accepting a MariaDB database, its quota, minimum term and amount actually payable initially.

The contractual offer states that rates are expressed in tenge and include applicable taxes and contributions. The provider’s 2026 tax notice states a VAT change from 12 to 16% on January first. It separately prices creation and extension of a .KZ or .ҚАЗ domain at 9,590 KZT for one year including VAT. The association lists domain, hosting and any backup destination on separate lines. It checks the amount breakdown and billing profile in its quote.

The SLA describes prepayment of the following period and possible automatic renewal from the console with a positive balance. The contract permits price-list revision. The public entry price therefore does not fix the next payment. The provider advertises a seven-day trial. The SLA also describes a refund on request within the first fourteen days of initial use, credited to the account balance. Check how this provision applies to the association’s payment method and profile.

Verify shared hosting and the Almaty location

This shared-hosting SLA dated August 13, 2026 names the Almaty center at 117 Makatayev Street in the Lotos business center. Other group facilities do not establish them as destinations for this range. The backup passage does not describe the exact location of infrastructure copies. The association must obtain that detail if location requirements also apply to recovery data, then record the location of the copy it exports itself.

The service is shared. It supplies disk space, processor, memory, databases and mailboxes according to the reference. The limits guide details six Standard plans. XS, S and M provide 1, 2 and 5 GB SSD with 256, 512 and 768 MB RAM respectively. L, XL and XXL advertise 12, 25 and 50 GB SSD with 1,024, 1,536 and 2,048 MB RAM. All six advertise one virtual core up to 2.1 GHz. The Premium range starts at 10 GB NVMe, 1,024 MB RAM and two cores up to 5 GHz. These references do not link the starting price to a precise plan.

The guide also specifies five simultaneous PHP or CGI processes per site, thirty-two simultaneous processes per plan and ten simultaneous MySQL connections per user. It also lists unavailable PHP process-launch functions. A backup plugin relying on system commands or prolonged compression warrants a trial with fictional files before migration.

The page advertises a Let’s Encrypt certificate, accessible logs, DNS manager and FTP file access. It describes traffic and aliases separately from computing quotas. Storage must cover active data and temporary export files. On an account hosting several names, record the share occupied by each site and mailboxes before choosing a plan. A single overall limit may be reached even if each site works individually.

Define WordPress in Plesk, languages and AI

The PS Cloud Services getting-started guide describes installation from Plesk’s WordPress section. The operator chooses the path, site language and version to install, among other settings, and can configure the database and automatic updates. The page describes MariaDB for MySQL sites. The SLA assigns code maintenance and updates to the customer and excludes on-demand software configuration from the base service. The installer facilitates startup. For the association, a member retains responsibility for plugins, restoration and result verification.

Sales pages exist in Russian, Kazakh and English, among other languages. The Plesk guides consulted are in Russian, and the provider describes Plesk with a Russian interface on its panel presentation page. Available account languages and written-support languages remain to be confirmed. The contract distinguishes continuous technical ticket support from information assistance during published hours. The contact page also publishes sales-service hours and local numbers.

The provider documents cloud instances with GPUs for machine learning. That is another product. Shared-hosting sources document neither AI site creation nor generation credits integrated into the WordPress plan. The association can therefore evaluate hosting on available installation, export, storage and maintenance. It treats any generative service under separate cost and data-storage terms.

Distinguish provider backups from customer copies

Guidance for preparing a targeted restore. — Illustration by BlogPasCher.Open full-size illustration ↗

The SLA describes two copy families. Infrastructure backups are retained for the last fourteen calendar days, with three full and up to eighteen incremental copies. Their volume does not count toward the customer quota. The PS Cloud Services Plesk guide mentions three weeks for administrator copies and likewise cites three full and up to eighteen incremental copies. An incremental point is not an additional day. For planning, use the contractual text’s fourteen days and record dates actually available in the panel. Retention observed on the operation date is a separate fact.

User-initiated copies are disabled by default according to the guide. Customers can schedule them, and local backups they create occupy plan space. In Plesk, open Информационная панель, then Резервное копирование и восстановление. The guide indicates downloading from the list, optional password protection and selecting elements to restore, including files, databases, email and DNS zones. Before deleting a full copy to free space, identify incremental points depending on it. The guide states that their deletion is linked.

The sales page states that an external destination can be used. Confirm authorized options in the customer panel and local space required during creation or transfer. A remote location may receive a copy at the end even though creation still uses temporary space. Check this sequence with a small package. External storage, credentials, encryption and key custody are the customer’s responsibility. An exported file must also be readable when account access is interrupted. After suspension for nonpayment, the SLA provides thirty days of retention and possible file deletion from the thirty-first day. This provision has a different scope from normal copy rotation.

Practice a backup with a nearly full quota

Run EXERCICE-PS-CLOUD.cjs from the “Prepare your site” ZIP folder with Node.js and supply a new working path on D:. The delivered result was obtained with Node 22.16.0. The script uses a theoretical quota of 1,048,576 bytes, with 921,600 declared already occupied. It writes two fictional files on the working disk. A poorly compressible binary of 147,456 bytes represents a media file. A small SQL file represents a database export. The quota is a calculation constraint. Test directories are on the same physical drive, and the space named outside quota is a logical destination in the model.

The exercise’s gzip package weighs 148,390 bytes for this dataset and environment. The script compares that size with the remaining 126,976 bytes. Keeping both the active site and package on the counted volume would raise the total to 1,069,990 bytes. It lacks 21,414 bytes before any additional margin. The program rejects that strategy. A control containing only compressed SQL fits the fictional quota. This control checks the size comparison. It is not a sufficient backup of this site.

The second route writes the package into the model’s external folder, opens it, restores both files to another folder and compares their SHA-256 hashes with the originals. Source files remain readable. The test provides two separate pieces of evidence: package space required and ability to recover component bytes. The package format is specific to the exercise. It simulates neither a Plesk archive nor import into MariaDB, and hash comparison does not verify that WordPress opens. In a real rehearsal, import the database onto an isolated site, check URLs and open media before validating migration.

node .\EXERCICE-PS-CLOUD.cjs 'D:\CODEX_STORAGE\tmp\ps-cloud-essai-01'

Organize transfer and keep exit practical

On the real account, record occupied space in Plesk and available per-service details. Note media, logs, databases, mailboxes and archives remaining on the account. To estimate the peak, add elements coexisting at each stage. Depending on the method, an export may generate an SQL file, an archive and decompressed files. Measure each element on a copy or with a representative sample, then retain headroom for site writes. If the calculation exceeds quota, choose another location or free space only after opening another copy of the affected elements.

The PS guide describes export through Файлы > Архив > Добавить в архив, then downloading. For the database, open Базы данных and use Экспортировать дамп. The export can be saved in a folder and downloaded. A file created in account space must enter the peak calculation. When quota is tight, transfer files in batches using the available mechanism and check the SQL production path. Record size before and after each step, open the package and protect files containing secrets. If the procedure fails, stopping must leave the site and last already-reviewed copy intact.

PS Cloud Services advertises inbound migration of up to three sites, with files, databases and some zone settings covered. Up to ten mailboxes may be moved without their correspondence. Treat messages as a separate task and record who must import or retain them. For exit, open components at the destination before shutting down the old service. Check plugins, attachment links and a test form with external sending disabled. Keep evidence of the first load and copy identifiers, then separately coordinate any DNS change.

Decide before starting migration

For the Almaty association, useful functions are the WordPress installer, Plesk exports, infrastructure copies and documented limits. Choose the plan from a record specifying disk volume, the right to create a MariaDB database, minimum term and next payment amount. With 427 KZT per month advertised at entry level, the evidence file must still establish which plan meets these conditions. If copy retention is decisive, request confirmation of the oldest point and verify that it can be downloaded.

Decide between methods using the measured peak. If a complete package remains below quota with the planned margin, download it, open it elsewhere and remove the temporary archive after verification. If the peak exceeds the limit, use a route independent of the counted volume and measure its temporary requirement. The small control SQL package does not replace media. Validating transfer requires a complete copy, its hashes and successful WordPress loading on the target. Recovery outside the account must be possible with keys accessible to authorized people.

If failure occurs, suspend transfer and keep the source accessible. Record which file or stage reached the limit. Check the result before restarting space-consuming archive creation. If changing domain or hosting, retain previous values and test the destination privately until the database, media and business functions respond. The migration file is complete when the team has identified the last healthy copy and can repeat restoration even after the original account closes.

Prepare your site

• 25 WordPress backup tools by recovery need
• WordPress prerequisites unmet: check PHP and MySQL or MariaDB
• WordPress migration, staging and imports: choose the right tool
• Download the quota-calculation exercise