OVHcloud for WordPress in France: plans and recovery

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

French sales pages consulted.

Control panel

Customer area documented in French. Managed hosting provides a choice of WordPress administration language.

Support

French workflow documented. Hours, channels and scope vary by level. Human support not tested.

Choose between Web hosting and managed WordPress

Official illustration of the OVHcloud Web Hosting offering. — OVHcloud

The first choice at OVHcloud is identifying who will operate the installation. With Web hosting, you have space for files and one or more databases, depending on the plan. You can install WordPress from the customer area, then manage its settings, themes and plugins. Managed Hosting for WordPress has a different panel and its own creation, import and update functions. Steps using the Web hosting FTP and Databases tabs correspond to the first route.

For a first site in France, start with the actual need. If you want a brochure site with email addresses for an association, count mailboxes and database size before choosing a subscription. If someone must maintain several WordPress sites, compare the time spent checking each update and preparing rollbacks. If migrating a site, measure files and the database separately and record PHP and software versions before comparing tiers. A test copy may consume a second database and additional space.

This revision’s French sales data was recorded on November 10, 2026. It separates initial price, renewal, term and taxes. Starting amounts on Web cards correspond to twelve months, while the managed WordPress card displays a monthly price and a two-month offer whose details remain to be clarified. To measure project cost, add domain renewal and services still billed elsewhere. The described procedures rely on the host’s help documentation.

Starter, Perso and Startup for a site or a few projects

In the French Web price table on November 10, Starter costs €1.59 excluding VAT per month, with €1.91 including VAT displayed monthly and €19.08 excluding VAT over twelve months. Advertised renewal is €2.59 excluding VAT per month. The plan contains 1 GB of files and a 250 MB database. For an existing WordPress site, measure image directories, hidden files and the database’s logical size. A compressed SQL file may look small while representing a larger volume after import. If the site is already close to the limit, leave room for logs and its next update.

Perso and Startup are displayed at €2.99 excluding VAT per month, €3.59 including VAT monthly on the card, or €35.88 excluding VAT for twelve months. Their published renewal is €5.99 excluding VAT monthly. Perso advertises 100 GB SSD, fifteen sites, five databases of 1 GB and ten mailboxes of 5 GB. Startup also presents 100 GB SSD, five databases of 1 GB and ten mailboxes of 5 GB, plus maxima of 1 vCore and 1 GB RAM. If planning public WordPress and a clone, count both databases and their data. The Mes sites tab can hold several domain associations. Each association must still point to the root and database of the installation it serves.

Compare tiers over two periods of equal length. For example, at the published renewal rate of €5.99 excluding VAT, twelve months would represent €71.88 excluding VAT and other services. The displayed monthly VAT-inclusive amount is rounded. To establish an annual VAT-inclusive budget, use the period total at the applicable rate and the invoice for any options. An eligible domain free in the first year then follows its own renewal price.

Pro and Performance according to the missing resource

Pro is displayed at €1.99 excluding VAT per month and €2.39 including VAT monthly on the card. The initial offer corresponds to €23.88 excluding VAT for twelve months and displayed renewal to €9.99 excluding VAT per month. Twelve months renewed at that rate would represent €119.88 excluding VAT. At the recorded prices, the promotion makes Pro cheaper than Perso for the first term. If both plans meet the need, also compare a second twelve-month cycle at the displayed renewal rates. This projection gives €107.76 excluding VAT for Perso and €143.76 excluding VAT for Pro over twenty-four months, excluding domain and options. It assumes the rates and cycle apply throughout the period. The order summary remains necessary to establish the bill.

The Pro tier consulted advertises 1 vCore, 2 GB RAM, 250 GB storage and ten databases of 2 GB. It also displays SSH access and one hundred mailboxes of 5 GB. The reference Performance card states 2 vCores, 4 GB RAM, 500 GB, twenty databases of 2 GB and one thousand mailboxes of 5 GB. It displays €6.99 excluding VAT or €8.39 including VAT per month for the first term, or €83.88 excluding VAT for twelve months, and €19.99 excluding VAT monthly on renewal. The range includes other configurations. Record the exact tier when comparing capacity or price.

A store with several simultaneous processes may need additional resources. First identify the limiting factor. An already saturated 2 GB database calls for a different choice from insufficient image storage. Record error times, running tasks and database volume. If difficulties occur during a product import, compare a smaller import on a copy with the corresponding logs. Keep these measurements to explain why the new plan would solve the identified problem.

What the managed WordPress service changes

The single-site managed WordPress plan displays €9.99 excluding VAT and €11.99 including VAT per month, 10 GB NVMe and 40,000 visits per month. The recorded page mentions two free months. The associated term, amount immediately due and separate renewal price have not been established. The ten-site plan displays €69.99 excluding VAT and €83.99 including VAT monthly, 50 GB NVMe and 300,000 monthly visits advertised for the plan. For a single site, use the corresponding card. Clarify how visits and overages are counted before inferring capacity.

In the managed service, open Mes sites, then Créer un site for an empty installation. Enter the administrator’s address, password, PHP version and administration language. Follow the status from Création to Actif in Mes sites, or details in Opérations. The guide describes a technical URL usable before associating your own domain. Check that URL’s visibility and restrict access if it contains working data. After acceptance testing, associate the intended domain and verify HTTPS access and canonical URL settings. Keep the ability to return to the original domain before cutting off the source.

The November 9 documentation describes updates applied first to a cloned environment and deployment conditional on automated checks. Then check project-specific actions, such as registration, shipping calculations or a private area. The documentation advertises managed backups. Their frequency, retention and restoration workflow are not established here for the single-site plan. Mailboxes are purchased separately. For an association needing five addresses, add their price and quota to the plan cost before comparing with Perso, whose card advertises ten mailboxes of 5 GB. Also check who can retrieve messages if a mailbox or the contract is deleted.

Install WordPress in one click on Web hosting

Log in with an account authorized to manage hosting and the domain. In Web Cloud, then Hébergements, open the correct service. In Mes sites, associate the domain or subdomain with its root folder. If a version of the site is already visible, prepare a new empty root and separate database. Keep the existing folder and its association in place during preparation. Check PHP-version compatibility and the presence of .ovhconfig in the FTP root according to the guide’s prerequisites. If the domain is still with another provider, record its DNS zone before choosing automatic configuration.

In Modules en 1 clic, choose to add a module, then WordPress and the prepared domain. Check the displayed installation directory. Advanced mode lets you select the database and supply its parameters when that variant suits the need. Test database login credentials before launching the module and keep them out of shared notes. After the installation message, open the homepage, an internal URL and WordPress administration. Check the certificate and confirm that all three respond on the intended domain.

If the module fails, record the domain, root, database and message. Check initial conditions before another attempt. A partial attempt may have created files or tables. Preserve existing elements and use an empty working destination if the scope is ambiguous. For an existing public site, keep its DNS and association pointing to the old root until acceptance testing. The Web guide describes initial module installation. Theme and plugin operations still need to be organized for the site concerned.

PHP, technical access and organizing several projects

OVHcloud documents environment settings and the .ovhconfig file for Web hosting. Before changing PHP version, record the existing configuration and verify compatibility of WordPress, the theme and plugins. Test the change on a copy when a suitable environment is available. Keep a copy of the previous setting. If a page returns an error after the change, restore the starting value, then examine the log for the precise action that fails.

The Pro table advertises SSH and several FTP accounts. Check your plan’s access before preparing migration or automated deployment. SSH on Web hosting serves operations authorized in that space. If your site needs a particular system service, check its availability in the selected contract. For several people, assign separate access according to the task and revoke temporary access once transfer is complete.

Mes sites associates domains with their directories. The host’s term Multisite refers to this organization. A WordPress multisite network, by contrast, is configured within WordPress. Before installing a second project, record the first project’s root and database. Reserve a separate database when quotas allow, so recovery can be separated. For several clients who need to leave the service independently, also examine who controls domains, exports and billing.

Migrate WordPress and retain a rollback option

For Web hosting, export files and the database at the source, then record PHP settings, DNS location and email destination. Prepare a dedicated folder in Mes sites and an empty database at OVHcloud. Transfer files through the available secure access, then import SQL into this database. In the destination wp-config.php, set DB_NAME, DB_USER, DB_PASSWORD and DB_HOST to the new database values. Check that the copy uses its own access and that its images and pages open. If you need to change domains for acceptance testing, use a tool that can update serialized data.

On managed hosting, the documented route is Mes sites, then Importer un site. Prepare the source administration URL, a temporary administrator account if possible, and an independent export. Choose the elements to import and follow Opérations. The documentation mentions a timeframe of up to 48 hours. It also notes that anti-bot protections can prevent connection. Arrange the necessary opening within an authorized scope during the planned window, then restore protection and revoke transfer access. If this scope cannot be secured, retain the source and use a recovery method that respects your access controls.

On both routes, verify the target before pointing the domain to it. On a store copy, use the sandbox and disable outgoing messages, stock synchronizations and production webhooks. Check a deep page, the certificate, login and a business workflow. Plan a final synchronization of writes or a freeze window. Record the old web entries and preserve MX records if email is not moving. If the target fails, restore the relevant entries, retrieve writes received on the target and reconcile them before reopening the source. Before any closure, retrieve files, SQL, DNS, email if relevant and registrar access.

Restore Web files and the database at the correct scope

A missing image or theme file first calls for targeted retrieval. Identify the domain’s folder in Mes sites, then open the service and FTP - SSH tab. Record the FTP server and main user. The host’s guide states that adding a suffix to the username opens a read-only copy. The suffixes -snap0, -snap1 and -snap2 correspond to the three recent points, and -snap3 and -snap4 to the two Sunday points described in the help. Check the technical date in the documentation and panel. Download the expected file, compare it with the current state and upload only that file to the active folder after retaining the version it replaces.

For an incident affecting all storage, FTP - SSH then Restaurer une sauvegarde lets you select a date. This operation replaces the entire file space, including other sites residing there. Before confirming, verify the scope, download the current state and confirm that at least half the FTP quota remains free, as the guide requires to prepare the copy. If space is insufficient, prefer a targeted download or arrange restoration on a separate target. Afterward, check several sites if storage is shared. Web copies are provided as non-contractual assistance. Broader marketing references to backups do not establish the recovery schedule.

For the database, find its name in wp-config.php. In Hébergements, then Bases de données, identify the corresponding row. The database menu lets you create a backup or retrieve an existing copy. Download SQL of the current state before any write. To assess an older point, import it into a separate test database and configure only the private copy to use it. Compare the date of the latest content, a referenced media item and administrative access. If you must replace public data, prepare a consistent files-and-SQL pair and a record of new orders, registrations and changes. Reconcile these writes before reopening the service.

Hosting security and site maintenance

Web plans advertise SSL certificates and protection against denial-of-service attacks. A certificate encrypts exchanges with the covered domain. It does not prevent a weak password, vulnerable plugin or incorrectly assigned permissions from compromising WordPress. These layers must be managed together.

The documentation recommends keeping the CMS, components and compatible PHP versions up to date. An antivirus feature or malicious-behavior detection is not a guarantee of complete cleanup. After an incident, removing an infected file without fixing the entry point may allow the problem to recur. Determine the cause before returning a copy to service.

Prepare separate access and protect the hosting account, which may grant access to several services. During troubleshooting, send useful information without publishing secrets. A DNS change, restoration or version change must be limited to the identified scope. The presence of security tools does not justify globally disabling protection to bypass an error. No practical attack-resistance assessment was performed for this presentation.

French-language support and AI management of managed hosting

The sales website, help and customer-area workflow consulted are in French. The managed-service guide also lets you choose the WordPress administration language at creation. Standard support is the level provided by default. Support levels and channels have their own scopes. For an incident, state the service, domain, time and observed result, then distinguish a hosting fault from an application setting. Hours and timeframes relevant to your case depend on the subscribed level. Web-module installation help alone does not cover theme troubleshooting.

OVHcloud documents managing its managed WordPress service through MCP, a protocol allowing a compatible agent to access tools. The guide distinguishes the OVHcloud MCP server for hosting, MCP for WordPress for site content and MainWP for managing several sites. Use depends in particular on access to the offer, a compatible agent and granted permissions. Some operations can modify sites. The guide recommends reviewing proposed actions before approval. It describes an administrative integration. Third-party agent permissions, quotas and costs remain to be checked. Before connecting the agent, identify the intended project and necessary actions. For a write operation, prepare a copy, verify the targeted site and retain a way to return to the previous state.

This management applies to the managed service described in the guide. Web plans Starter, Perso, Startup, Pro and Performance are not presented here as including a site generator. Separately, Smart Automatic Updates describes an update-validation mechanism on a clone. For a purchasing decision, separate content-creation needs, administration needs and tasks the team wants to delegate. No agent command or account action was executed for this presentation.

Plan domain and email renewal

An eligible domain may be free for the first year with the relevant Web plans. Renewal then follows the extension’s price and the domain’s schedule. Record the holder, registrar, expiry date and address receiving alerts. Use a recovery address that remains accessible during migration. If the domain stays with another registrar, you can update its web records while retaining its contract and renewal.

In the selected Web plans, included mailboxes have their own 5 GB quota. Inventory existing mailboxes, aliases and groups. If messages remain with another provider, preserve MX records and corresponding authentication settings. If mailboxes change, verify outgoing and incoming mail at the destination and retrieve messages arriving during transition. Shared-calendar or collaborative-email services need separate assessment.

The France page describes the French scope of Web hosting. If a physical region or backup location is part of the requirements, have it specified for your plan. Keep that answer with the contract reference. Choosing the domain and choosing the hosting center are two separate decisions.

Check renewal and prepare an exit

The customer area distinguishes services to renew from those you can request to stop. Record the expiry date, renewal method and notifications for each line. For an outbound migration, choose the end date only after confirming recovery elsewhere. Check registrar, email and export access on a machine independent of the source hosting. If another service still uses a database or file from the old account, identify its owner and transfer date.

For a conventional Web site, keep a file archive and SQL from the same state, plus a record of Mes sites, the PHP version and scheduled tasks. For managed hosting, identify available export methods on the project before building an exit plan. Exporting articles from WordPress is insufficient to reproduce plugins and their settings. For a store, retain a record of the latest orders and active external processes.

Exit can be verified when the domain leads to the new target, email arrives at the expected address, and administration plus a business action work. Record the last write received on each environment. Reverting DNS returns visitors to the old target. Data entered since cutover must still be transferred or reconciled before making that target writable again.

Prepare your site

• Compare plans for an association with five mailboxes
• Check WordPress PHP and MySQL or MariaDB prerequisites
• Compare WordPress backup tools