Kosowwwa in Kosovo: managed WordPress and retention

Who Kosowwwa 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 and Albanian selector. Cited documents consulted in English.

Control panel

Client area and WordPress. Confirm languages available after login.

Support

Phone and contact in Ferizaj. Enterprise assistance advertised around the clock. Confirm languages and applicable SLA.

Kosowwwa for a WordPress site in Kosovo

Kosowwwa sells three hosting plans from Ferizaj, Kosovo. The comparison distinguishes Enterprise through explicit WordPress management and backup retention duration. The two lower plans provide pricing and capacity context.

This profile follows an association that discovers late that some site data has been modified. It wants to find the latest verified copy predating the change and determine whether the retention window still covers it. The exercise uses a fictional backup catalog. It helps decide when to request a restoration and when to use an independent export.

Plans, billing and renewal

The recorded prices correspond to the annual tab displayed in the grid. For Starter, multiplying the rounded equivalent of 6.67 € by twelve gives 80.04 €, while the written total is 80 €. Use the annual total when budgeting for this cycle. The interface also offers monthly billing and presents the annual choice as a saving of two months. Verify the amount for the period actually selected and the taxes before accepting the proposal. Within this profile, Enterprise is the offer to examine for WordPress application management.

The terms dated 10 March 2026 provide for advance monthly or annual billing and the addition of applicable taxes. They also provide for cancellation with 30 days’ notice and a prorated refund of unused months on prepaid annual plans. An engagement letter may set out specific provisions. The public documents examined do not give a guaranteed price for the next renewal or describe automatic payment. Ask for the second period’s amount, notification method, the date by which notice must arrive and the proration rules. The 30-day notification clause for material changes provides another reference point.

To compare monthly and annual quotes, verify that both cover the same regions, resources and support scope. A prepaid offer may include one-off migration or setup tasks. Have these tasks distinguished from the recurring amount and ask which fees qualify for the prorated refund. The start date, end date and notification method should be available in the same file as the initial invoice.

Capacities and managed WordPress scope

The page presents one-click installers for hosting. The comparison assigns WordPress management to Enterprise, together with a dedicated IP address and global CDN. The number of domains does not determine how many WordPress installations the team will maintain under the contract. Before choosing, clarify the number of managed sites, PHP and database versions, allocated resources and tasks performed by the provider. A project using several data-collection sites may consume storage for media, databases, exports and staging.

The word “managed” becomes concrete when tasks and their frequency appear in the proposal. Ask who schedules core, theme and plugin updates, who intervenes if an update breaks a page and who approves the return to service. The comparison mentions WordPress and Shopify on the same offer. The example association should have WordPress, its domain and the relevant installations listed in scope. For a store, also specify the payment-testing procedure and handling of orders arriving during intervention.

Languages, support and hosting regions

The public site offers an English and Albanian selector. The consulted documents are accessible in English. Client-area languages and those available from support outside business hours remain to be checked. The provider is based in Ferizaj and publishes a phone number, address and contact form. The FAQ places the main infrastructure in Frankfurt and the second region in Sofia, with Swiss and Albanian options on request. Clarify the chosen region, the backup region and the location of any recovery.

The grid associates Enterprise with an advertised round-the-clock incident response time of 15 minutes and Business with four hours. The public SLA uses the names Seedling, Grove and Forest and presents separate availability and response targets. It gives no mapping to Starter, Business or Enterprise. Request written confirmation of the applicable plan, channel to use, incident definition and response times. SLA availability rates cannot be assigned to the grid simply because the tiers look similar.

The provider also publishes a status channel. For an incident, record when it began, the region specified on the order and affected functions. The sales form and incident support may operate on different schedules. Questions about language or timing must address the channel that handles the site after purchase. Also identify the address to use if the organization’s panel or domain becomes unavailable.

Backups, staging and migration

The hosting page highlights daily backups and publishes retention windows of 14, 30 and 90 days depending on the plan. Ask whether these windows apply to files, the database, email and domain settings, and when a recovery point becomes accessible. A copy may exist but fail during restoration. To determine whether a recovery point is usable, restore it in an isolated environment and verify that expected pages and data open. Staging is offered from Business upward. Clarify whether it shares storage and whether a recovery point can be restored there without affecting the public site.

The FAQ states that Kosowwwa can move an existing site. To prepare a transfer, agree on the scope of files, database and mailboxes, required access and the switchover window. Once copied, compare media, links and form functionality. The actual migration time and commercial terms have not been established for the project. If the site receives registrations during transfer, agree on how to retain those arriving after the first copy.

A data anomaly discovered late requires dating the first unwanted change and distinguishing recoverable data from data added afterward. Restoring an entire older site can remove valid information. The recovery file must therefore specify which elements to extract from the copy and which to leave in production. Ask the host whether selective restoration is possible, who performs it and at what cost. The team also keeps an external export and verifies it to the same standard.

AI and creation services

The grid advertises neither a writing assistant in WordPress, website generation nor an AI allowance included with Enterprise. The site presents design, development and operations services. Their presence does not indicate which features would be available in WordPress administration after subscribing. If an AI plugin is part of the project, ask whether its configuration is included and which contract covers the external provider. Also check rights to imported content and how to remove the plugin.

For the association, the recovery test can be prepared with demonstration text and registrations. Restoration operations involve copies and dates. A writing-assistance tool might help with page text, but change control still requires history and independent backups. During scoping, identify any external processing that uses the content and what must be maintained if those tools are discontinued.

Local exercise: find a recovery point

The model applies the displayed windows to fictitious dates. An actual copy must be restored and checked. — Illustration by BlogPasCher.Open full-size illustration ↗

Objective. Find the most recent copy verified before an unwanted change. The fictional change is dated 6 October 2026 and the check 11 November. A backup from 5 October is therefore 37 days old. The script applies the host’s 14, 30 and 90-day windows, assuming a copy is eligible when its age is strictly less than the window. This convention is used for the test. Confirm the rotation time and exact contractual boundary. The external copy remains available if listed in the inventory and validated.

Run the command from the supplied package using Node.js 18 or newer. Compare the result with resultat-kosowwwa-kosovo.json. With the 14 and 30-day windows, the model finds the external export from 1 October. With 90 days, it selects 5 October, or 3 October if the newer copy is invalid. Without an external export and with 30 days of retention, no recovery point qualifies. The 1 November copy is excluded because it postdates the change. The 4 October copy is excluded because its verification failed. To test another window, change the duration and expected assertion. On a real site, “validated” status must correspond to a test restoration and documented checks. The command selects a point in a fictional inventory. It neither downloads nor restores any data.

To repeat selection in a more realistic case, add the covered data type, WordPress version and environment where the copy was tested to the inventory. A valid file backup may be insufficient to recover registrations if the database is missing. When an external service has received some records, reconcile the two inventories at a common date. The latest dated point remains an assumption until a test restoration confirms the expected data.

node exercice-kosowwwa-kosovo.cjs

Choose a plan and check the contract

On the test copy, verify data restoration and file restoration separately. Record the recovery point’s date, covered service and number of accessible registrations before approving recovery. If backups are managed from a client area, check who can view them and how the team would request access during an incident. Keep an inventory of external copies that remains readable even when the account is unavailable.

Enterprise is the relevant plan if the association wants WordPress management included in the offer. Business provides staging and a 30-day window, which may suit a team maintaining its own site with exports covering the rest. Starter targets a simple project, and its 14-day window requires frequent external copies when anomalies are discovered late. Storage choice depends on media size, mailbox count and space consumed by copies. Have these uses clarified in the quote.

Before accepting, record the domain and installations covered, the initial total, renewal date, notice rule and next period’s cost if specified in the offer. If an intervention is included in an engagement letter, check whether it covers WordPress core, plugins and the theme, along with operations on a site receiving registrations during an update. Ask how out-of-scope work is billed and who approves a restoration. Taxes, termination terms and specific engagement-letter rules must appear in the order document.

For backup tracking, keep the creation date, covered service and result of the latest test restoration. If data is spread across the site, an inbox and an external tool, retain it with its own reference date. When an anomaly appears, determine the earliest time the incorrect content could have been saved. Then seek a point before the most plausible time and verify valid writes occurring between that copy and the present. The exercise illustrates selection using whole dates. A real incident may require more precise times or record comparisons.

Prepare an off-production restoration before changing DNS or overwriting the public site. On the copy, test pages, media and the form. Compare a few entries with a record made before the incident. If only part of the site is affected, agree on how to retrieve those elements without reverting all data to its previous state. After intervention, keep the copy and records needed to understand differences. For an association, this process helps recover content without losing recent registrations.

Finally, confirm the hosting region, backup region and SLA plan name before deciding. If the proposal mentions an initial response within fifteen minutes, ask whether the target applies to all requests or only qualifying incidents. Keep the emergency channel with the recovery file. For a credit request, retain the ticket and downtime record and refer to the applicable SLA deadline. Support can then identify the project and offer that actually cover the site.

Prepare your site

• Contact Form 7 stays on the loading indicator after submission
• WordPress XML export and full backup: check what you can restore
• WordPress import: resolve a missing or invalid WXR version
• Download the backup selection exercise