iHost.al: WordPress hosting prices and limits in Albania

Who iHost.al 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 on the offer and catalog consulted.

Control panel

WordPress Toolkit advertised in the catalog. Actual panel and private interface languages to confirm.

Support

Albanian and English advertised. Technical channel and intervention hours to clarify.

iHost.al for WordPress in Albania

iHost.al publishes three WordPress plans in euros. The dedicated page advertises preinstalled WordPress, migration assistance and resources increasing with domain, database and email-account counts. The store also presents WordPress Toolkit. For a project retaining several websites, database count is useful when preparing restoration. Permissions and the database name must still be checked for every installation.

This profile considers a small Albanian team maintaining two websites and wanting to avoid restoring one website’s archive into the other’s database. It compares pricing, general terms and limits still requiring clarification. Offline acceptance testing uses fictional names and archives. It checks that the intended domain, archive origin and destination database belong to the same project record. The procedure prepares a trial on a copy before a real operation.

Monthly prices, term and renewal

The iHost.al WordPress page displays three monthly euro prices. The store’s public catalog gives the same amounts in the web review consulted. Its header specifies that displayed prices exclude VAT. At unchanged prices, Basic at €2.99 excluding tax per month totals €35.88 excluding tax over twelve months. Deluxe at €4.99 excluding tax totals €59.88 excluding tax over the same period, and Gold at €9.99 excluding tax totals €119.88 excluding tax. The table consulted documents no annual discount for these plans. The price paid depends on the cycle and amount presented when ordering. The tax-inclusive total and WordPress hosting renewal amount must be specified in the quote.

The terms require recurring services to be paid before expiry and allow charging an authorized payment method when automatic renewal is enabled. They state that termination must be requested before the next renewal. The product page advertises a seven-day money-back guarantee. The general terms dated October 21, 2026 state that voluntary refunds are generally excluded after activation. They preserve expressly advertised guarantees and applicable rights. Domains and renewal payments are among generally excluded items. A cancellation request can be submitted through the customer area or a ticket and does not automatically trigger a refund. Ask which arrangements cover the chosen product, especially when the order includes a domain or renewal.

The public schedule gives €12.99 per year to register or renew a .al. The domain count in WordPress cards indicates hosting capacity. The table gives no domain name included at this price. If the team buys .al separately, the Basic-plus-domain projection totals €48.87 for twelve months before any tax or pricing adjustment. To prepare the second cycle, keep both amounts and their expiry dates separate.

Resources and WordPress tools

The cards give separate counts of domains, databases and email accounts. Basic provides one domain and one database. Deluxe doubles both and adds four email accounts. Gold advertises five domains and five databases. The table helps prepare an inventory for an organization operating several websites. Before choosing, check how the plan counts a test copy and whether it can use a separate destination database.

The product page presents prepared WordPress, monitored updates and an SSL certificate. The public store mentions WordPress Toolkit for installation, update management and management of several websites. The name and access details of the panel actually supplied on each WordPress plan need clarification. Pages for other hosting families give tools and limits that may differ. A team using a specific Toolkit feature should ask to see it on the relevant plan.

To price recovery, record each website’s space, each database’s size, account count and any archives retained on hosting. The table does not quantify WordPress-specific CPU, memory, file or process caps. Nor does it detail per-mailbox size. An organization wanting two separate production databases may still need a third destination to try restoration. Ask whether that destination can be temporary or another tier is needed.

Languages, panel and location

The WordPress page presents information in English. The customer catalog offers English and Albanian. The direct home page advertises support in Albanian and English. The contact page places the team in Tirana and lists tickets, chat, telephone and email. It advertises continuous assistance while also giving a Monday-to-Friday window from 9 to 20 for the technical section. Ask which channel covers the intended intervention and what response time applies if restoration is needed outside that window.

The team can keep internal documentation in French and set WordPress administration per account. Languages actually available in the provider’s private interfaces remain to be confirmed. A demonstration can include viewing an invoice, a database name and locating an archive. The domain manager, publisher and database operator do not always need the same permissions. In an organization operating two websites, assign each access point to someone and document which account can act on which website.

The home page presents infrastructure in Albania. The WordPress page refers to several centers. Clarify server and copy locations applicable to the selected contract. For a Tirana team, support address and data location answer two needs. One describes the team relationship; the other concerns service configuration. If the two websites have different constraints, ask whether the same choices apply to every installation.

Backups, migration and responsibilities

The directly consulted product-page FAQ advertises automatic backups on every plan. The current page gives neither frequency nor retention for these copies by plan. The general terms require customers to keep their own copies and describe applicable backup responsibilities. Confirm frequency, retention, included file types, restoration cost and permissions needed to retrieve the database.

The page advertises free WordPress migration. Clarify timing, transferred elements and email migration conditions. When an organization takes over two websites, establish a separate record for each domain. Specify source database name, archive date and destination installation. For an export including only editorial content, also record components to retrieve separately, including theme, plugin and media files.

Payment terms and backups operate on different timelines. A team ending a contract must retain a verified copy before the period ends. If using WordPress Toolkit, ask whether a copy can be restored into a test database and how to identify the database remaining in production. Website paths and URLs may also require checking after restoration. Acceptance testing must be stoppable before any write if the destination name does not match the inventory.

AI and editorial tool choices

The WordPress page and catalog consulted describe themes, assisted installation and updates. They do not document a generative AI service included with Basic, Deluxe or Gold. WordPress Toolkit is presented as an installation-management tool. If a sales proposal includes a creation tool, ask who owns the account, which languages are offered, the next-cycle cost and rights over the output. An answer must identify the plan and covered uses.

An Albanian association publishing its activities can write from already public information. A draft must be reviewed before publication, especially when containing times or place names. If the team creates several websites, prepare a folder per domain. Record plugins storing settings in the database and those depending on external services. The archive owner can then establish what a restoration reinstates and which access must be restored separately.

The test account should use fictional information. The team can check confirmation messages and recipients without using members’ contact details. Also check that the copy does not display public forms as though it were production. This check concerns website configuration and remains valid regardless of writing tool. When the copy is ready, another person can test a page, navigation and a form before approving recovery.

Local exercise: check a restoration destination

The acceptance test checks the archive’s origin and test database name against a fictitious inventory. — Illustration by BlogPasCher.Open full-size illustration ↗

A team in Tirana maintains two fictional websites, culture.example and archives.example. Each has a production database and identified test destination. Every archive is associated with its domain and source database in the export record. The team sets a simple rule: the origin must match the requested website and the destination must be that website’s test database. Exercise database names, domains and archives are fictional. The script reads no database and starts no restoration.

Extract the ZIP and run this command in the extracted folder.

The first scenario submits the Culture archive to its acceptance-testing database. The second selects the Archives archive for the same website. The third chooses Culture’s production database. The fourth selects Archives’ acceptance-testing database with the correct Culture archive. Compare output with RESULTAT-IHOST-AL.json. Only the first scenario passes. The second fails on origin, while the last two fail on destination. Several databases on a plan do not guarantee access separation or an extra database for testing.

Replace the first case’s destination with the production database. The result must block the operation. On a real copy, record names from the panel or validated inventory, check the file fingerprint and date, then have a second person verify the destination. Next check expected pages, dated content and website-specific settings. The local check concerns element identity. A trial restoration remains necessary to verify archive content and copy behavior.

node EXERCICE-IHOST-AL.cjs

Which plan to choose and what to clarify

Basic gives an entry price for an organization operating only one domain and one database. If the project already owns a name, ask about conditions for using it without transfer. If a .al must be registered, add the domain line to the budget with its own expiry. To compare monthly purchase with an annual proposal, use amounts actually displayed in the quote. The profile’s projections help verify an unchanged-price total and identify tax, option or renewal lines requiring clarification.

Deluxe is the first plan advertising two databases and two domains. In the Tirana example, production may already occupy both databases. The team must therefore clarify where a test destination can be created and whether the provider offers temporary capacity. Gold advertises five databases, but that number does not answer access or isolation questions. For a project retaining several installations, request a demonstration with a domain name and database reserved for acceptance testing. Check where the panel shows the production and destination databases.

The quote must also cover renewal terms, taxes and any commercial guarantee. Ask for a first-cycle price and renewal price for the same product. The consulted terms specify that a charge may occur when the automatic option is enabled. Before moving, confirm end dates and how the team retrieves files, database and email. Keep the request date, identity of the account used and provider’s response in the handover folder.

To accept the copy, have two people verify the domain-archive match, then check content clearly distinguishing the two websites. A test edit, dated page and fictional form confirm that the copy loaded expected data. If one team works in Albanian and the other in English, use the same reference names in their documents. Support can then locate the case from the domain and export date. Also retain the name of the person who validated the copy and the planned date for removing test access.

Prepare your site

• 25 WordPress backup tools according to recovery needs
• WordPress XML export and full backup: check what you can restore
• WordPress migration, staging and imports: choose the right tool
• Download the restoration-check exercise