CleanNet in Georgia: WordPress prices and renewal

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

Georgian and English pricing table. The Georgian contract version takes precedence under Article 11.

Control panel

WordPress Manager and customer area. Confirm languages after signing in.

Support

Chat, tickets and telephone advertised around the clock. Confirm languages and response times for each channel.

CleanNet for WordPress in Georgia

CleanNet sells four WordPress plans from Tbilisi. They share a WordPress manager, command-line tools and a LiteSpeed stack, while capacities and prices vary. The table’s annual selector distinguishes the first-year price from the amount displayed at renewal.

This profile follows a small store preparing its migration. After copying, it wants to keep a fast catalogue and ensure personalized pages are not reused between sessions. The acceptance test checks this criterion against fictional responses, without a hosting account or requests to a store.

Prices in lari, first cycle and renewal

The two direct pages, in English and Georgian, publish the same values in plan cards. Annual amounts appear in the data used by the term selector. For Basic, two annual cycles total 480 GEL according to the table, compared with 600 GEL for 24 monthly payments assumed unchanged. For Starter, Premium and Pro, displayed two-year totals are 790, 1,120 and 1,610 GEL. These calculations use the renewal rate displayed today and assume no other line is added. Check tax, domain and payment terms on the order.

The general contract specifies advance billing in lari according to the selected cycle. It allows a price change with 30 days’ notice, without changing a prepaid period’s price before expiry. The table’s renewal price provides a numerical reference. For a firm budget, check the price on the notice received at renewal. Confirm payment method, notice generation date and cancellation handling for the account.

WordPress resources and tools

The table advertises WordPress Manager, one-click installation, WP-CLI, SSH, Git, SSL, CDN and backups. WordPress Manager provides an entry point for managing installations. The migration guide describes importing an existing installation into this tool after transfer. For WordPress with scheduled tasks, clarify available PHP and database versions, command restrictions and account permissions. SSH and WP-CLI provide ways to intervene. The project must still determine who performs and verifies application updates.

The cards present processor and memory multipliers from 2× to 4× depending on the plan. They do not give the absolute core count or memory in gigabytes. Premium and Pro display the same multiplier with different storage capacities and site counts. Starter and Premium host up to five sites according to the table. To size an account, add the files, databases, media and test copies the team wants to maintain. Ask how email and backup files are counted if space is nearly full.

Databases, traffic and email accounts are listed as unlimited in the comparison. Database size, task duration and allocated resources remain criteria to check. For a store, cart and checkout operations use the site even when public pages are served from cache. A storage and site-count table is therefore insufficient to estimate checkout or catalogue-import performance.

Languages, support and infrastructure

The WordPress page was examined in Georgian and English. The published contract states that its Georgian version prevails in case of interpretive differences. Check languages actually accessible after signing in to the management area and WordPress panel for project operators. WordPress allows the site administration language to be selected according to configuration. The offer does not document response times or support in each language for tickets, chat or telephone.

CleanNet’s migration guide locates its servers in Tbilisi and advertises round-the-clock chat, ticket and telephone support. It also describes copying files and database and checks before a DNS switchover. If data must remain in a specific region, ask for backup locations, the server assigned to the account and CDN scope. Primary-server location and caching locations address different needs. For migration, specify the window in which the team and support can act together. Also record the channel to use if the site responds but the customer account or payment is unavailable.

Cache, migration and backups

CleanNet states that its WordPress offers use LiteSpeed Enterprise and LiteSpeed cache. The table associates plans with a CDN and backups. For a store, record which pages may be cached and which responses depend on a session. The public catalogue can share a result if price, stock and language remain correct for the visitor. Cart, checkout and account require checking with multiple sessions. An exclusion rule must also account for localized versions and addresses actually used by the store. If the team changes rules, measure their effect after clearing the relevant cache layers.

The FAQ advertises regular copies. The general contract specifies at least the preceding three days for the hosting scope it describes. Ask for conditions specific to the WordPress plan and details of accessible restorations. Frequency, version count and database-restoration scope can have different consequences for an active store. Returning to an old copy may restore files while deleting data recorded after the copy. Also check how to export files and database independently.

The migration guide recommends testing the new server before changing DNS and keeping the old service during propagation. For the store, check media, permalinks, scheduled tasks and checkout using authorized testing tools. Before switching over, identify data changed since the first copy, plan its transfer and record who approves the new site. If email also changes servers, test sending and receiving before and after the switchover.

Setup AI and a separate builder

All four WordPress cards mention AI tools. The FAQ describes setup assistance, particularly for structure, initial configuration and basic settings. It details neither quotas, available languages, model nor retention arrangements for entered data. Check which tasks run in WordPress and whether settings can be revisited or corrected after creation. A store reusing its catalogue can test the assistance with demonstration text and then check visibility and navigation settings.

CleanNet also presents a product for creating a site from a description, with its own editor and publishing workflow. That product’s page confirms neither inclusion in the WordPress plan nor export of the resulting site to WordPress. Clarify where the site is edited, which offer it requires and whether generated pages can be retrieved. For this profile’s project, the team can perform cache and migration checks independently of content generation.

Local exercise: check private pages and caching

Fictitious cache check. Each private response must match the session that requested it. — Illustration by BlogPasCher.Open full-size illustration ↗

Goal. Check fictional catalogue, cart and checkout responses. The catalogue must display the expected public version even when a response comes from cache. For private workflows, the script checks that the marker matches the session and that the observation does not report shared-cache reuse. Cache names and response text are demonstration values. They represent observations the team would record after testing site pages.

Run the command from the extracted ZIP directory with Node.js 18 or newer. Compare the output with resultat-cleannet-georgie.json. The compliant scenario passes. Cart B receiving cart A triggers two alerts: shared cache and incorrect session. A checkout response in shared cache and a stale catalogue each trigger a distinct alert. In the compliant example, the catalogue may respond twice from cache while private responses keep their own markers. In the third case, the body is correct, but the reuse signal is enough to trigger checking. As a variant, replace session B’s checkout response body with A’s marker and adjust the assertion. The error must be detected even if the observation does not carry the shared-cache value.

In real conditions, test on an authorized copy with two isolated browsers or profiles, demonstration products and accounts. Repeat cart and checkout workflows with the gateway in test mode. Headers differ between CDN and origin cache. The simulated result therefore validates neither an actual CleanNet configuration nor the absence of every possible site leak.

node exercice-cleannet-georgie.cjs

Choose a plan and check the order

During acceptance testing, also record cache options offered by the CDN and WordPress plugin. On the copy, open every language version of the cart and account with both test profiles. Add workflows you actually use, such as a checkout page with a language prefix. For an intermittent regression, compare a cold opening with a repeated opening and indicate in the ticket which layer produced each header.

For the example store, Basic may suit if two slots and 5 GB are enough for installations, their files and data occupying the account. Starter increases storage to 10 GB and site count to five. Premium keeps the same site count and increases storage to 25 GB with a higher resource multiplier in the table. Pro offers ten sites and 35 GB. An agency planning several sites can count public domains, working installations and the volumes needed for recovery separately. For a single project producing many media files, storage and the ability to handle simultaneous tasks are more direct criteria than slot count.

Compare cycles with identical scope. A monthly invoice may be easier to approve if the project is still uncertain. The displayed first year costs less than twelve monthly payments for each of the four offers, and the displayed annual renewal equals twelve monthly payments from the table. A team can establish two budgets, one for launch and one for the following year, then add the domain and genuinely necessary options. At sign-up, retain values as they appear in the annual selector and quote. Check the billed period, domain holder and effect of a plan change.

Before migration, inventory themes, plugins, scheduled tasks, PHP settings and external dependencies. An active store must also plan how to handle orders written during copying. Check which data can be synchronized at the last moment and when a maintenance window must be announced. If several people have administration access, record who checks the cart and checkout, who triggers the DNS switchover and who opens a ticket if an anomaly appears. The host’s guide describes migration while keeping the initial service accessible. Timing depends on site size and transfer method.

After switching over, open a public page in a browser not used for trials, then compare two demonstration sessions for personalized workflows. Check response content and headers. If the cart retains an earlier version or an unexpected session, record the cache layers present and their configuration. Before reproducing a problem, ensure test orders, messages and recipients are isolated from real workflows. Repeat the check after any cache-rule change that could affect private-page behavior.

Ongoing tracking can then record the plan, confirmed limits, renewal price, date of the last restoration trial and rollback procedure. For an anomaly, add the time, checked path and expected result to the ticket. Also ask whether origin and CDN can be checked separately. This information gives support context to identify the setting or layer serving a stale response. When the team plans a campaign or major update, repeat observations on a copy before making the change public. Finally, assign someone to receive renewal notices and link that tracking to the site’s verified backup date. The project thus retains a decision date before renewal even if technical work and accounting are split among several people.

To make future comparisons easier, retain the date prices were recorded and the exact cycle label. The monthly amount and annual total may appear in different places on the invoice.

Prepare your site

• WordPress change not visible: find and clear the right cache
• Empty or outdated WooCommerce cart: recover the session and refresh data
• WordPress XML export and full backup: check what you can restore
• Download the cache-checking exercise