li-life in Liechtenstein: WordPress pricing and quotas

Who li-life 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

German storefront and help center.

Control panel

Plesk documented in technical notices. Confirm edition and enabled languages.

Support

Phone during business hours, email and WhatsApp. Public resources in German; confirm support in other languages.

li-life in Liechtenstein: sizing an association’s WordPress site

li-life offers four WordPress-compatible web plans in Liechtenstein, with separate limits for advertised space, MySQL databases and mailboxes. A fictional association maintains a public site and prepares a private copy. Its team also receives documents in an administrative mailbox. When choosing the offer, files, databases and email must each fit their own allowance.

A site of a few gigabytes may leave enough room for production but run out of space during restoration. Conversely, moving site archives to a backup drive may free storage without making a second database available. An undersized mailbox remains undersized even when other mailboxes are empty. The choice therefore begins with an inventory of needs during operation and recovery.

The exercise compares several scopes for the same association. It calculates the smallest plan compatible with the displayed limits and provides a twelve-month budget at the observed rate. It does not open a hosting account. Example quantities are fictional. Invoicing, provisioning and backup organization remain separate questions.

Compare setup fees and recurring costs

The four web plans display a recurring monthly rate and a 129 CHF setup fee. The page invites visitors to request an offer. The general terms state that prices include VAT. The page specifies neither actual billing frequency nor an introductory discount. The first twelve months’ cost in the table adds twelve displayed monthly payments and the setup fee. The next column shows twelve months at the same recurring rate. This is a constant-price projection without a second setup fee. The quote must confirm that the plan, tax treatment and renewal match the budget.

| Plan | Displayed price CHF per month | Setup CHF | First twelve months budget CHF | Twelve recurring months CHF | | --- | ---: | ---: | ---: | ---: | | Zero | 13 | 129 | 285 | 156 | | Standard | 27 | 129 | 453 | 324 | | Professionell | 48 | 129 | 705 | 576 | | Ultimativ | 75 | 129 | 1,029 | 900 |

Liechtenstein’s tax administration states a standard VAT rate of 8.1%. Since li-life’s general terms present prices as VAT-inclusive, retain the displayed budget without adding this rate again. Check the exact treatment and itemized charges if the customer has a billing profile outside the usual market. Domain price, transfer, assisted restoration and any intervention fees are excluded from the calculation.

li-life publishes an AGB index, and its help center lists a web subscription form. The available general PDF specifies a one-year term for web and email hosting. Without written cancellation at least thirty days before expiry, the subscription automatically extends for a corresponding period. The text permits changes in purchase costs to be passed on, and the grid sets no separate amount for future renewal. In particular, check whether the domain and hosting have the same due date and whether an upgrade triggers new setup fees. For an association, the person receiving the invoice must also have contact details and the exit procedure.

Read web space, databases and mailbox quotas

File space, database count and each mailbox’s individual limit appear on separate lines. Zero advertises 5 GB, one database and ten 500 MB mailboxes. Standard lists 20 GB, ten databases and fifty 3 GB mailboxes. Professionell lists 50 GB, thirty databases and two hundred 5 GB mailboxes. Ultimativ lists 100 GB, fifty databases and an advertised unlimited number of mailboxes, each capped at 10 GB. These figures inform the budget. They do not specify whether database storage or local archives count against the advertised space.

A second database lets you separate testing from the production site. By itself, it does not establish that the offer permits a second site or subdomain on the same subscription. Before modeling a copy on the same account, check the number of usable sites, subdomains and certificates, PHP settings, maximum database size, CPU, RAM and any file quotas. The consulted grid does not quantify these limits. Meanwhile, the exercise can compare rehearsal in another environment with rehearsal on the account, using genuinely different volumes.

The legal notice places li-life in Liechtenstein. Its site describes infrastructure in the country for cloud and backup services. The web table mentions li-life servers and thirty days of backups without specifying every backup’s physical location. If WordPress location is a requirement, confirm the region of the web server, email service and every backup copy for the web contract. A company address or the location of another product range does not answer this question.

Check WordPress, languages and the absence of advertised AI

The grid lists WordPress as a supported system alongside Joomla and other CMSs. Provider technical notices mention its Plesk platforms and the operation of PHP applications including WordPress. This establishes advertised compatibility and the provider’s use of Plesk. The pricing page does not state the Plesk edition supplied with each plan, available PHP versions, WordPress Toolkit activation or a core-and-plugin maintenance offer. Ask which actions remain possible with the customer role. Before importing a database, check the PHP version, database server version and PHP extensions used by the site.

The consulted storefront, notices and help center are in German. The web page lists phone availability Monday to Friday from 8 to 12 and 13 to 17:30, along with WhatsApp and email. Other support languages and those actually enabled in the panel remain to be confirmed. The team can prepare a bilingual sheet linking each technical term to its German section, then have the procedure validated by the person opening the request. Published hours do not constitute a guaranteed restoration time.

The consulted web and help pages describe no included AI builder, WordPress assistant or generation credits. The page mentions a mail filter with an adaptive algorithm in a separate antispam section. When sizing the offer, keep content generation and email management on separate lines. Test text or a thumbnail generated elsewhere adds to the file inventory like any other media. The exercise quotas stay the same regardless of content origin.

Organize restoration without filling the site’s storage

The grid displays thirty-day data backups for all four plans. It does not give recovery-point frequency, exact archive scope, self-service access or intervention time. A month of retention means data may be kept over that duration under the applicable terms. It does not establish thirty daily copies. Ask for the time of the latest available point, the oldest copy, details of covered files, databases and mailboxes, and the procedure for recovering a single table or folder. Site recovery does not always require email restoration.

If enabled for your Plesk subscription, its documentation describes access through Websites & Domains, Backup Manager, along with content, configuration and database backups. This documentation describes Plesk’s product capabilities. For li-life, permission to download a backup, choose remote storage and restore independently must be checked. Plesk also specifies that space occupied by backups stored on the server may count against the quota. Have this established for your account. Before restoration, prepare enough room for the decompressed copy and temporary files, and keep an independent archive.

An accessible method without an integrated backup feature is to prepare an SQL export and a copy of the site files. Check the export’s time, location and size together. Then record the time needed to reconstruct the site in a private installation and open media attached to a page. If mailboxes are part of the contract, inventory them separately and plan recovery according to the email client and retention rules. A WordPress archive alone does not contain the administrative office’s email history.

Practice choosing a plan from an inventory

Four fictitious inventories make it possible to check web, database and mailbox limits before calculating the cost. — Illustration by BlogPasCher.Open full-size illustration ↗

In the extracted ZIP folder, run node EXERCICE-LI-LIFE.cjs. The saved result file is RESULTAT-LI-LIFE.json. The script reads neither account files nor a remote database. It uses in-memory constants and compares needs across four dimensions: web volume, database count, mailbox count and largest mailbox size. Volumes are converted using an internal decimal convention of one thousand megabytes per gigabyte. Confirm the contractual convention and actual space calculation method. The script selects the first offer meeting every dimension, ordered by displayed prices, then adds twelve monthly payments and setup.

The “site seul” scenario requires 4,200 MB, one database, eight mailboxes and 450 MB for the largest. Zero fits the model at 285 CHF over twelve months. “Site et répétition” adds a second database, raises total files to 5,800 MB and the main mailbox to 650 MB. Zero fails on all three dimensions. Standard fits at 453 CHF. “Boîte archives” starts from the site-only scenario and increases one mailbox to 3,200 MB: Standard fails the individual limit despite its mailbox count, and Professionell fits at 705 CHF. The final scenario puts 101,000 MB in the web allowance, exceeding even Ultimativ. The script then returns a result with no plan or budget instead of recommending the most expensive plan.

Try a variant with the rehearsal outside the account and only the large mailbox’s archive moved elsewhere. Modify a copy of the needs constant and examine the detailed obstacles for each offer. Assertions fix the results for the supplied examples. Update them for your variant after calculating the expected result by hand. Price enters the decision only after all four thresholds have been checked. Useful headroom is not included in the model. On the real project, set it before comparing offers, according to the rate of media additions and time needed to remove working archives.

Repeat the calculation with measured volumes

To repeat the calculation, start by recording production files and peak space during restoration. In the private copy, measure the site directory, the archive if kept locally and extra space during decompression. If the panel shows disk usage or statistics, compare them with your records and note what is counted. An SQL export may be small in a compressed archive but occupy more space during import. Check whether the provider counts databases with files or separately. Also count existing databases that nobody wants to delete blindly.

For mailboxes, record the required number and then the largest size. An aggregate volume of 4 GB spread across ten small mailboxes and a single 4 GB mailbox may lead to two different plans. Check which archives may be moved with the association’s agreement, where they will remain readable and whether users need to retain some history online. If archives leave the account, test that their format can be read before reducing a quota. This step separates active-mailbox needs from retention needs.

If local staging is sufficient, install a copy in an independent environment with fictional or minimized data and email sending disabled. Production then retains its own database and resources. If the team needs staging accessible to several volunteers, confirm availability of a subdomain or second private site, a second database and a certificate. Restore a backup to the authorized target and verify an editor’s access, theme operation and media URLs.

Decide on the smallest capacity that supports recovery

The exercise selects Zero for production alone and Standard for the version with a second database, workspace and 650 MB mailbox. It selects Professionell when a single mailbox must retain 3,200 MB, even when the site remains small. These results illustrate three ways of shifting a constraint. You can choose a higher subscription, isolate rehearsal in another environment or retain email archives elsewhere if the association’s policy allows it. Recalculate after every change: freeing disk space does not reduce a mailbox’s size, and reducing history does not free a database.

Approve a plan only when the observed restoration volume fits with headroom defined by the team. Confirm how archives count against the quota, which Plesk menus are available and which scope permits the most selective restoration. Plan a rehearsal with someone unfamiliar with the site: they must find the archive, choose the target and observe that the database and media belong to the same recovery point. If the copy cannot coexist with production, restore elsewhere. Production web space then remains available during rehearsal and new content is not overwritten.

If the calculation finds no suitable plan, separate the working archive from the site before requesting a larger offer. Measure the peak again and establish whether separate hosting or backup storage is sufficient. If storage costs and recovery time increase, compare them with the annual difference between two plans after confirming billed items and setup fees. Keep the exit schedule beside the budget. Note the last day of access to backups, the person receiving invoices and where recoverable files are stored. The association must be able to explain its chosen plan through a volume, an operation and an amount that can each be verified separately.

Prepare your site

• WordPress requirements not met: check PHP and MySQL or MariaDB
• 25 WordPress backup tools by recovery need
• WordPress migration, staging and imports: choose the right tool
• Download the sizing exercise