FORPSI: Linux, WP Ready, AI and WordPress limitations

Who FORPSI 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

English and Czech consulted; separate Slovak/Polish/Hungarian offers.

Control panel

FORPSI administration and menus documented in Czech/English; private session not tested.

Support

Technical support and phone advertised as nonstop; sales/billing on business days 8–16 according to contact page. French not established.

Choose between Linux and WP Ready

Official FORPSI logo. Provider identification; no test result or account interface is depicted.

FORPSI sells several product families that can host WordPress. This profile concerns plans on the Czech website of INTERNET CZ, a.s., with prices in Czech crowns. The Slovak, Polish and Hungarian variants must not be merged with this table. The site also offers servers and cloud services: their dedicated resources and commitments are not automatically included in shared hosting.

General-purpose Linux suits an administrator wanting to install WordPress, access files and manage a database. WP Ready instead provides a prepared WordPress site with an AI creation assistant. Its guide explicitly excludes FTP and direct database access. This choice reduces installation work but requires checking how to retrieve a complete export or perform a specific technical operation.

These differences matter more than the WordPress label alone. An independent team may prefer Linux access; a beginner may appreciate WP Ready’s prepared site if its features and exit process match the project. No account, installation, AI trial or performance test was carried out for this profile.

Linux prices: first year and subsequent years

The Linux table observed on November 3, 2026 presents Easy at 32.50 CZK excluding tax per month for the first year, then 65 CZK. Advanced displays 55 CZK, then 150 CZK; Professional 160 CZK, then 450 CZK. The promotion is advertised for new orders, on the base service and for the first year. It therefore does not prove a discount on options or an existing subscription.

The FAQ specifies annual billing. Monthly equivalents do not mean monthly payment. By multiplication, initial base budgets total 390, 660 and 1,920 CZK excluding tax for twelve months; subsequent years total 780, 1,800 and 5,400 CZK. These are calculated totals from the table, with no invoice or checkout verified. Renewal can cost substantially more than entry, particularly for Professional.

Local columns also display tax-inclusive prices, for example 39.33 CZK for promotional Easy and 78.65 CZK afterward. They do not alone determine tax treatment for a customer in France. Residency, customer status and the final invoice remain to be checked. This profile does not convert crowns into euros: conversion would introduce another variable and could obscure the amount actually charged.

Sites, databases and email: separate limits

Easy includes one site, Advanced up to three and Professional up to ten. Advertised subdomain counts are five, fifteen and fifty respectively. Disk and traffic are presented as unlimited. This does not mean each domain has an independent server or that multiple sites can consume shared package resources without restriction.

The plans provide one, three and ten SQL databases, each with 5 GB of space. A 5 GB database is a separate limit from web disk space. A store or site with extensive histories must measure its database before transfer. The Linux table specifies a PHP memory_limit of 1,024 MB, maximum execution time of 900 seconds and file upload limit of 128 MB. The first parameter is a PHP limit; it is not an amount of physical memory dedicated to the account.

Email advertises unlimited mailbox numbers with 1 GB per mailbox initially. Gigamail increases their space. Additional-space and maximum-size columns must therefore not be treated as an automatic allocation to every mailbox. A project using substantial email must price the required extensions, migration and conditions for restoring message contents.

Free SSL also depends on the domain

The commercial page presents a free DV certificate, but its guide details several conditions. FORPSI must be the domain registrar; the domain holder and hosting holder must match. FORPSI DNS is also required, except for the stated Hosting Basic exception, and no other SSL service may already be active on the relevant service.

The Actalis certificate described in the guide covers the main domain and certain package subdomains. Aliases and a subdomain with its own hosting are not automatically covered. The private key is not exportable and the certificate is used on FORPSI shared hosting. These restrictions matter for a team wanting to retain its registrar, use external DNS or move to another operator.

The current guide specifies validity of 199 days since March 15, 2026, with conditions checked again before renewal. Transferring the domain or making an incompatible DNS change can therefore remove the certificate benefit. The migration budget and schedule must account for this before switchover. A certificate encrypts the connection; it does not replace WordPress maintenance or access controls.

First approach: install on existing Linux hosting

This workflow concerns existing Linux hosting, an authorized empty destination and an identified MySQL database. The domain must point to FORPSI. A trial must not overwrite an existing site; check the destination before opening the installer. This procedure does not describe WP Ready.

1. In the account, open Webhosting, select the service, then Instalátor and Otevřít installer aplikaci. In English, the guide specifies Installer, then Open installer application. Choose WordPress, then Install.
2. Enter the intended domain and directory. Leave the directory empty only for an empty root intended for this installation. Use HTTPS once the certificate is valid; if there is a certificate error, have it fixed before transmitting credentials.
3. Enter the database and SQL credentials supplied for this service. The SQL server must use its actual name, not localhost by default. Choose a personal WordPress administrator, a strong password and an accessible address; save these credentials in a secure manager.
4. Review the settings and start installation. The expected result is a summary with the site and administration addresses. Check login, the HTTPS URL and media without sending a real form or order to try the site.
5. If installation fails, record the error and check the destination and credentials before retrying. Keep the original site intact. To remove a trial, identify only its files and tables; do not delete a shared database or another installation’s resources.

WP Ready: prices, AI and more restricted access

WP Ready displays 60 CZK excluding tax per month for the first year, then 120 CZK; WP Ready & e-mail displays 72, then 132 CZK. The guide ties the billing period to the associated domain’s expiry. These monthly amounts therefore do not establish the first invoice: ask for the start date, deadline, duration actually billed and separate domain cost. No contractual annual total is inferred for WP Ready.

Both variants present 50 GB of web storage and a 5 GB database. The guide advertises preinstalled WordPress, automatic updates and prepared plugins. It specifies no FTP or direct database access. The variant without email must not be sold as including an email service.

The email card mentions five mailboxes and a maximum size of 10 GB, while a note describes an initial 1 GB with expansion through Gigamail. This relationship must be clarified before promising five included 10 GB mailboxes. Cache features and prepared plugins also do not demonstrate a free license for every commercial use or complete application support.

Create with AI without confusing generation and validation

The WP Ready guide describes an assistant that starts on first WordPress access. The user supplies a business description; the tool suggests a structure, text and layout. The Site Assistant menu, called Asistent webu in the Czech documentation, then allows site adjustments. The commercial page also advertises page creation, a conversational assistant and content or image generation.

The selected sources do not establish exact quotas, models used, all data-processing conditions or continuity of these features after departure. Distinguish content retained in WordPress from services the assistant calls. No generated result or response quality was tested here.

According to the guide, Reset site restarts the assistant but deletes existing content. It is therefore not a preview button. Before considering it, have a complete recoverable copy and avoid working on the active site. On a copy, protect access and disable messages, payments and synchronization. Generation must be reviewed before publication, particularly prices, promises and contact information.

Backups: file rotations and SQL history

The Linux FAQ describes three file rotations in backups-forpsi: a daily copy replaced after midnight, a copy replaced on Monday and another on Thursday. This is not a history of thirty versions or uniform daily retention for two weeks. Databases are advertised as backed up every morning, with the oldest available copies around fourteen days old.

The restoration guide allows file retrieval and database reimport, but consistent states must be selected. A file copy alone does not restore orders or articles stored in the database. The page also distinguishes email-account configuration backups; this does not prove a recoverable history of every message.

Customer recovery is documented; support intervention is advertised from 500 CZK, estimated according to the time required. Final cost and tax must be confirmed. Check that copies exist and their dates before needing them. An advertised backup does not prove a specific point is still available for your incident; also keep an independent copy you can actually access.

Second approach: retrieve before restoring

This workflow concerns Linux hosting with file and SQL access available. The guide uses an FTP client to download the www directory from /backups-forpsi/backup-daily/. Start by also preserving the site’s current state and an SQL export, even if faulty: it may contain more recent data. Check failed transfers before considering the download complete. The local archive must remain protected.

The guide then suggests renaming the active directory instead of deleting it immediately, then restoring backed-up files. This operation interrupts or changes production; an initial check on an isolated copy is preferable. Before making that copy executable, protect access and disable email, payments and synchronization. Database credentials can be found in service details under SQL or in wp-config.php. The webmysql.forpsi.com panel allows export and import through phpMyAdmin.

The old tutorial illustrates complete table replacement. This operation must not be blindly applied to a database shared by several applications. Prefer an authorized empty database for the test copy, adapt its configuration so it never connects to the active database, then verify that files match the SQL backup. For one missing file, limiting recovery to that file may avoid an unnecessary full restoration. The expected result is a functioning WordPress site with the correct data state. Rollback uses the preserved current files and export; new orders received since the backup must be handled separately. No deletion or import was performed here.

Migration: documented plugin and quoted assistance

The FORPSI WP Migration Tool guide requires WordPress administrator access and a token obtained through an authorized request. After tool installation, its menu accepts the token, checks components and allows selection of files to transfer. The guide advises against including old archives produced by other backup tools. Transfer continues even if the browser closes; subsequent changes are not automatically included.

For a store, the guide provides for maintenance mode to avoid orders missing from the copy. If activity must continue, assisted migration must organize transfer of new data. A technician then deploys the backup and coordinates switchover. Keep the old service and its DNS records until pages, email and essential workflows are validated.

The assistance page advertises free service for simple static HTML sites and charges for special requirements, with a displayed rate of 500 CZK excluding tax per thirty minutes in its detailed workflow. Another presentation abbreviates this rate. Obtain a confirmed price; free migration for every WordPress site is not established. The tool helps transfer but replaces neither an independent copy nor acceptance testing.

Languages, support and location

The website and several articles have English and Czech presentations. During consultation, some English support URLs returned Czech content. A team depending on entirely English documentation must anticipate this difference. French support availability is not established, and private-panel languages were not tested. English pages alone do not prove admission of every foreign customer: for a French address, have eligibility and invoicing confirmed before arranging transfer.

The contact page advertises nonstop technical support and a customer line. Billing and sales information have separate hours, listed as 8 to 16 on business days. Continuous availability is not a guaranteed resolution time. The site highlights its own Czech data center; the selected sources do not assign a precise contractual region to every copy or establish a universal restoration commitment.

Mentions of cache, hardware and attack protection describe advertised features. No speed gain, response time or availability rate was measured. Significant resource or continuity needs must be assessed against commitments of the service actually selected.

Departure and decision criteria

The shared-hosting cancellation guide describes Webhosting, domain selection, then Service cancellation beside the expiration date. The form specifies the arrangements; termination occurs at expiry. It also mentions handling after nonpayment, but failing to pay is not a controlled exit method. It leaves reminders and must not serve as a data-preservation strategy.

Before any closure, export required files, databases and messages, then verify the new destination. A plan including a domain requires distinguishing hosting termination from retaining registration. The shared-hosting cancellation guide does not establish all rules for domain-linked WP Ready. For WP Ready, obtain the full file and database export procedure, any fees and time frames before subscribing. For FORPSI SSL, whose private key is not exportable, arrange a new certificate at the destination before switchover.

Linux is the clearest choice for someone seeking documented technical access. WP Ready may suit a guided AI-assisted launch, provided its limited access is accepted and portability is established. The budget must account for subsequent years, email options, the domain and interventions. These points, rather than a promise of unlimited storage, determine suitability for the project.