Papaki: standard or managed WordPress, prices, access and exit

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

Greek and English; English pages sometimes mixed with Greek.

Control panel

Legacy Papaki 1.0 and new 2.0; SSO to old products; English documentation, private session not tested.

Support

Documentation and contract in Greek or English, with Greek prevailing under the terms. Tickets advertised 24/7; French and telephone/chat hours not established.

A Greek brand with WordPress hosted in Brussels

Official Papaki WordPress presentation illustration. It does not depict a private interface used or a feature tested.

Papaki offers standard and managed WordPress plans to the Greek market under operator Enartia Single Member S.A., a member of team.blue. Sales pages are accessible in Greek and English. This profile examines new offers as of November 3, 2026; it does not transfer terms from legacy products now available only for renewal.

The WordPress Service Order, updated September 9, 2026, places servers in Brussels, Belgium, and does not provide for moving the space to another center. It also mentions a geographical copy in another Brussels location depending on the purchased solution. The brand’s Greek market therefore does not mean the site will be hosted in Greece.

Papaki is also migrating management between panels 1.0 and 2.0. A button for older products gives separate access to legacy services. Before following a procedure, identifying the plan and platform is essential. Access limits on current managed WordPress in particular differ from some older guides. No private account, checkout, purchase or performance test was used for this research.

Standard WordPress: four sizes for one installation

The standard table displays Start with 5 GB NVMe, a 512 MB database, 256 MB PHP memory and one 2 GB mailbox. Business increases this to 10 GB, a 1 GB database, the same PHP memory and three 2 GB mailboxes. Digital advertises 25 GB, a 2 GB database, 512 MB PHP memory and five 2 GB mailboxes. Premium advertises 50 GB, a 5 GB database, 1 GB PHP memory and ten 2 GB mailboxes.

The contract permits only one WordPress site and one installation per space. These quotas do not describe general-purpose hosting for several CMSs, archive storage or a site farm. PHP memory is the advertised limit for PHP processing; it does not represent server RAM exclusively reserved for the customer. CPU and process counts are not quantified in the retained table.

A detailed table linked from the page contains other prices and contradictory email data, particularly for Digital. Several rows mix Greek and English or appear misaligned. This profile retains the main table as an identified record and preserves the conflict. It does not combine the best quotas from each table to fabricate a plan offered nowhere.

Managed hosting adds services and reduces technical access

The managed Start, Business, Digital and Premium plans display 5, 25, 50 and 100 GB NVMe respectively. They advertise one test environment on Start and Business, two on Digital and Premium, and update management. Disk volumes therefore differ from standard plans with the same names. Managed database and computing capacities are not inferred from standard capacities.

New-platform documentation states that managed WordPress provides neither database access nor FTP or SSH, including for test environments. WordPress administration remains accessible, and the panel supplies information about volumes, cache, updates, certificates and copies. This model suits a team accepting greater technical delegation.

Managed updates do not guarantee perfect compatibility of every plugin. The contract notes that customers must maintain commercial theme and plugin licenses unless otherwise agreed in writing, and acknowledges that problems can remain after an update. Before choosing managed hosting, check integration, diagnosis and exit requirements that would need unavailable access.

Displayed prices, promotions and payment term

The direct record of November 3, 2026 displays standard Start at 6.90 euros excluding VAT per month, Business at 9.50, Digital at a promotional 9.30 with a reference of 15.50, and Premium at 24.90. Managed hosting displays Start at 4.14 euros excluding VAT, reference 6.90, Business at 20.50, Digital at 30.50 and Premium at 41.90. Another extraction retains managed Business at 10.25 euros: this conflict prevents promising that discount. These amounts are dated observations, not a contractual offer.

The contract specifies an annual term by default, or another term if offered and selected. A monthly label therefore does not prove a monthly debit cancelable each month. No annual budget is calculated here: discount duration, applicable amount and initial total have not been established together. Before committing, record the exact plan, billed period, tax-exclusive amount, taxes, options and next advertised price in one summary.

Discounts depend on offer conditions, and renewal follows the standard rate then applicable, visible in the panel. Prices exclude VAT. Tax treatment and acceptance of a French application are not established; confirm accepted billing country and necessary supporting documents. The detailed standard table still displays 6.65, 12.67, 20.93 and 29.93 euros without explaining the difference from the main cards. It therefore does not establish a better guaranteed price.

Renewal, trial and refund

The Service Order provides for renewal for the same term unless otherwise specified. It allows switching from automatic to manual up to twenty days before expiry and the reverse up to thirty days before. The first debit is attempted twelve days before the due date. The general terms repeat these thresholds in article 7.4 but also state thirteen and fourteen days in article 4.7.1. They give the Service Order priority for this product: make the decision before the specific threshold, then confirm acknowledgment and the service stop date.

The sales page advertises a thirty-day trial and a money-back guarantee on paid offers. The Service Order allows cancellation with a service refund within thirty calendar days of activation or renewal. It does, however, exclude an automatic refund of unused time following early termination outside this window. Domains and options may have other terms.

For a trial, check whether paid conversion is planned: the general terms announce a first debit attempt the day before it ends and cancellation before that attempt. Keep confirmation of stopping. Trial and refund are distinct; neither proves migration or all options are included. Keep the old instance and data during evaluation. Written cancellation is also subject to a general thirty-day notice period: do not confuse that process with simply changing renewal settings.

AI: creation advertised, quotas and portability not established

Both ranges present AI Site Assistant. The provider attributes structure selection, site creation and WordPress content generation to it using customer-supplied information. This inclusion is advertised on product pages; it should not be confused with the site builder, Macaly or a standalone AI model subscription.

The pages examined give no clear contractual quota for text, images or requests, no model used and insufficient detail on data processing. No content was generated to verify operation or quality. For an agency regularly creating pages, these missing details can matter as much as the assistant’s name appearing in the table.

Before publication, review content, contact details, prices, images and product commitments. For a trial, use a protected location and prevent real messages, payments or synchronizations. Keep an independent content copy and check reuse rights. Creation in WordPress does not prove that the AI assistance service or all its functions remain available after moving to another host.

Activate the service without replacing an existing site

This workflow requires an already purchased service, the right to administer it and an empty destination. If a site exists at the chosen address, use a prepared migration; do not start a second installation to repair a display fault.

To abandon a trial, identify the created instance precisely and preserve necessary data before deletion. Available restoration and access then need to be verified by the customer according to the plan. This profile describes the official workflow without executing it on an account.

1. In the Papaki panel, open To be activated, select the correct plan, then Activate.
2. Fill in Website Name, Admin Email, Website Address, Admin Username and both password fields. Use an accessible recovery address and a secret unique to this account.
3. Review the domain and service before Install WordPress. Wait for completion; Login then opens administration.
4. Check access and follow connection information received after activation. Automatic DNS depends on who actually manages the zone and its state: retain previous values before any cutover.
5. Check HTTPS, administration and pages, without real payments or email. If connection fails, check the DNS target and contact support instead of reinstalling.

Read backup retention by level

The table advertises three daily copies for Start; seven daily and twelve hourly for Business; fourteen daily and twelve hourly for Digital; twenty-eight daily and twenty-four hourly for Premium. These numbers describe available points and history windows, not three or twenty-eight daily operations to add together. The general announcement of hourly backups therefore does not mean Start has the same hourly history as Premium.

The contract describes a backup on a separate server and a geographical copy depending on the solution. Nevertheless, it asks customers to retain an original on their own media and limits commitments if retrieval is impossible. Check dates and times actually available before intervention and keep an independent copy meeting recovery needs.

Email is separate: the restoration guide specifies that the WordPress operation changes neither mailbox settings nor contents. Successful site restoration therefore does not constitute an email backup. Its export and receipt must be planned through another workflow.

Restore managed WordPress: a complete replacement

A managed-plan operator can use integrated restoration with Papaki access. In the dashboard, open the product, then Hosting Packages, WordPress and the plan. Choose Advanced settings and Backups. First record the date, time and scope; Restore then Confirm trigger replacement. Confirm only after preparing recent data as described below.

The guide explicitly states that this operation replaces the whole installation, files and database together. Selecting just a file or table is impossible. Before confirming for a store, preserve orders and registrations received since the copy and organize a write freeze. The expected result is the entire site in its previous state; afterward, check administration, pages and business functions.

Managed hosting excludes local backup downloads. Arrange a usable copy or confirmed recovery point before replacing data; if no method preserves the current state and recent writes, defer restoration and request a procedure from support. Another older point will not retrieve orders never backed up. Afterward, check media, access and business data without real transactions or messages.

Restore standard hosting: files and database separately

Standard hosting offers separate recovery through Advanced settings, then Backups. For the database, select its name and download the chosen point with Download. The result is a compressed SQL file. First keep an export of the current database and stop writes during recovery. In phpMyAdmin, select that exact database before Importer, choose the archive and verify SQL format. An import may replace or add data depending on its contents: if a size or existing-table error occurs, stop and send the message to support without randomly deleting tables or blindly retrying.

For files, choose the date in the corresponding section. The service creates a dated folder under /restored-backups containing that copy’s files. Customers can then download them or recover only useful items. The folder consumes plan storage; after checking and retaining it elsewhere, remove only the restored copy that is no longer needed.

To repair a file change, this approach avoids restoring an older, healthy database. For full recovery, coordinate file and database dates to avoid incompatible versions. If a fault occurs, return to the copy preserved before intervention. The standard plan’s download capability must not be attributed to managed hosting, which works differently.

Contractual limits that can block migration

The Service Order prohibits using the space for personal backups or a plugin that automatically accumulates local copies. It also prohibits transfers of files of at least 100 MB and states these may be technically blocked. A method based on uploading a large migration archive to the server therefore must not be assumed compatible with this offer.

Other published limits are one hundred thousand files or folders in one directory, one thousand tables in a database, two thousand emails per day and database queries not exceeding fifteen seconds. These ceilings differ from an overall storage quota and guarantee no traffic level. They matter for a site generating many small files or long-running processes.

Before migration, inventory large media, caches, archives and tasks, then confirm handling of elements exceeding a restriction. The official restoration folder does not generally authorize retaining local backups produced by a plugin. No bypass of service limits is proposed; if the project does not fit, choose another plan or suitable arrangement.

Migration and email: clarify exclusions

The general terms offer migration of up to five sites from a third party to paid hosting, provided the plan permits them, the operation is technically possible and the request arrives within ninety days. Since the WordPress plan remains limited to one site, that general maximum of five does not increase its capacity. Trials and free services are excluded.

Transfer between the operator’s services is normally free within this framework only when it upgrades to a service with a higher list price. Late operations, certain technical changes and specific work may be billed. Promotional terms also require checking offer provisions. The commercial promise of free transfer must therefore be matched to the exact plan and project.

Email contents are not included in this site migration. Customers must retain and move messages, folders and attachments separately. WordPress restoration does not retrieve them either. Before modifying DNS, check MX records, sending settings and receipt in old mailboxes, then retain the previous service during verification.

Languages, tickets and production checks

English documentation describes the main workflows, but some pages mix Greek and English. The contract can be concluded in either language; under its terms, Greek prevails if interpretation differs. Tickets are advertised as permanently available through Support, then Request Assistance in a logged-in account. Without an active account, a written request is possible through the contact form. No French support, response time or equivalent telephone and chat availability is established.

Managed test environments are used to try changes before replacing production. The guide states that Replace live environment with test environment transfers the copy’s content and settings. Before activating it, protect its access and disable messages, payments and synchronizations. Lack of indexing does not replace an access restriction. Before promoting it, preserve recent public-site data; do not assume automatic order merging.

The contract mentions a credit mechanism linked to availability below 99.9% over a year, with exclusions and required notification. That threshold must not be replaced by the brand’s general statistics or presented as a measured result. Server status alone does not verify that a purchase or form works; these application checks still need to be organized.

Organize exit before choosing managed hosting

Export documentation distinguishes old and new panels and offers different methods by product: files, SQL database, email and DNS information. It states that availability depends on the service and permissions. This general guide does not remove managed WordPress’s specific restrictions: no FTP/SSH, no directly accessible database and no local export of integrated copies.

Before subscribing to managed hosting, obtain a workflow for retrieving all files and the database in a format restorable elsewhere, with scope, timeframe and any necessary interventions. A WordPress page export or panel printout is insufficient to rebuild a complete store. Provider-advertised export assistance does not prove every account has a self-service button.

On standard hosting, retain native files and the database, then validate restoration at the destination. In both cases, keep email, domains and licenses separately, and make the decision before the deadline to stop renewal. The contract provides for data deletion at the end of service. Papaki may suit a project handled in Greek or English; choosing standard or managed must start with expected access and portability. The inspected official visual is promotional and demonstrates no performance.