Websoft in Fiji: Managed WordPress and Annual Budget

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

Offering in English. English, Simplified Chinese and Hindi selector.

Control panel

WordPress administration access. Languages after login must be confirmed.

Support

Team in Suva, form, phone and WhatsApp. Languages and incident response times must be confirmed.

Websoft for a WordPress site in Fiji

Websoft Pte Limited publishes three WordPress packages in Fijian dollars. They provide access to WordPress administration and leave email to be handled separately. The two higher tiers add storage, a domain and a page builder advertised in the table.

This profile follows an organization moving its site without changing email providers. Before cutover, it wants to check that pages and forms work on the copy and that email settings are preserved. The exercise uses a fictional state of the site and its DNS zone.

Annual prices, taxes and renewal

The page presents prices in Fijian dollars excluding VAT. It states that applicable tax is added under current rules, without publishing each customer’s payable total. All three amounts concern the WordPress hosting in the table. Site creation, email and assistance services must be recorded separately if they appear in the quote. For Turbo and Supersonic, ask which domain extension is included, whose name it will be registered in and whether renewal is included.

The page advertises an annual term but publishes no separate renewal price, automatic renewal rule or cancellation deadline for these three packages. To budget over several years, request the first-cycle total and expected next-cycle rate, including the price-change rule and domain due date. Clarify who receives the invoice and which payment method is required. The absence of a separate price in the table leaves open the possibility of a change. Keep the quote and subscription terms received so the same product can be compared at renewal.

To estimate the second year’s expense, distinguish the recurring hosting price from services supplied only once. Migration may be part of setup, while a domain or licence may be billed on another date. Ask whether changing plans during the year affects the amount already paid and how the next invoice will be calculated.

Capacity and WordPress access

The packages are designed for WordPress. The FAQ states that only WordPress administration access is provided and that cPanel is absent. For a site transferred from another provider, check how to retrieve files and database, who can import them and which permissions are available if the site no longer starts. Also ask about the PHP version, available scheduled tasks and import limits. The page recommends contacting the provider to host several sites. The table does not establish a number of installations per package.

Turbo displays twice the baseline CPU and one and a half times the memory. Supersonic displays four times the CPU and twice the memory. These relative values allow comparison across the range, alongside 10, 50 and 100 GB NVMe. Absolute capacity, concurrent processes and import sizes required for migration must still be confirmed. Bandwidth and visitors are presented without a fixed quota for normal usage. Resources may be reassessed in the event of sustained abnormal traffic, mass storage or prolonged load. For a campaign, tell the provider the expected volume before choosing.

Email is absent from every WordPress package in this table. The example organization retains its email provider and checks DNS records before cutover. Email settings and the service sending messages from a WordPress form may be managed by different people. Identify them before changing servers.

Languages, support and data location

The offering consulted is in English, and the site selector also displays Simplified Chinese and Hindi. Full availability of technical documents and assistance in those languages remains to be confirmed, as does support in Fijian. Websoft locates its business in Suva and offers a form, phone and WhatsApp. The contact page mentions a response within one working day for the requests it describes. Intervention time for a WordPress incident and arrangements outside business hours require an answer specific to the offering.

Having a team in Fiji does not establish the location of the origin server, backups or CDN-related services. Ask for these locations if the project processes registrations, customer information or documents subject to retention requirements. For migration, the provider should identify who leads preparation and who can intervene if the organization loses administration access. The sales channel can help define these points before purchase.

Migration, updates and backups

Websoft describes a three-step migration: choosing a package, copying and testing, then changing DNS after validation. To prepare the copy, it requests the site address, information about current hosting, relevant DNS access and the list of critical functions. Migration time and cost are not quantified for every case. For the example organization, agree on a window when content and the form can be tested, and specify when new records will be synchronized.

The table advertises automatic WordPress updates and its description mainly discusses core. Clarify how plugins and themes are handled, the schedule and rollback options. The offering does not publish the WordPress package’s backup frequency or retention. For a project limited to WordPress administration, ask how to download an independent copy, who intervenes if this interface becomes inaccessible and how long restoration takes. Do not infer backup terms solely from advertised SSL and CDN.

A server change may be limited to the site record when the DNS zone stays with the same provider. In other projects, nameservers also change and the entire zone must be recreated. To retain email, record the relevant entries, including MX and authentication settings, and compare the zones. The WordPress form also needs its own sending test. A visible page after cutover is insufficient to validate the message reception workflow.

Brizy and AI services

Brizy Site Builder appears on Turbo and Supersonic. The table does not specify the edition or licence tier provided. Brizy states that AI generation for WordPress is available in Brizy WordPress PRO offerings. Its inclusion therefore cannot be inferred from the builder name listed by Websoft. Clarify the edition, quotas, languages and rights to pages if the site leaves the hosting service. Publishing and export features must be checked for the builder actually offered.

Websoft also publishes a private AI service involving audit, deployment and assistance by proposal. This service concerns organizational uses and has its own scope. None of the three WordPress packages consulted advertises its inclusion. For a team seeking only a WordPress site, keep the hosting quote and AI proposal separate. If a form or documents will feed an external service, specify authorized data and who may approve processing.

Local exercise: prepare migration checks

The scenario compares fictitious records and check results. Rerun the checks after an actual switchover. — Illustration by BlogPasCher.Open full-size illustration ↗

Goal. Check that a fictional migration changes the site address, preserves email records and passes three application checks. The exercise compares two objects representing a zone snapshot. Demonstration values use addresses and names reserved for documentation. It compares the supplied strings and makes no DNS query. Page, administration and form tests are results entered in the scenario.

Run the command from the extracted ZIP folder with Node.js 18 or later and compare the output with resultat-websoft-fidji.json. The complete scenario passes. The scenario with a changed MX fails the email check. Even with a correct zone, a failing form still blocks validation. In the final case, the script detects the old address and missing SPF and DKIM values. As a variation, change only the DMARC value in the correct copy and add an expected result identifying that record. The script should flag the discrepancy. For a real DNS change, inventory full names, multiple values and priorities, as well as other services using the zone. A real comparison may normalize equivalent formats. The acceptance test retains identical strings to make tests reproducible.

Then perform independent validation after cutover. From an external network, open the site, send a demonstration message and check receipt at the retained email provider. If the team also changes nameservers, compare the new zone’s authority with the agreed values. The exercise prepares the check and validates neither propagation nor deliverability.

Once the fictional checks are adapted to the project, date the DNS snapshot and record the form verification result. If several addresses or selectors are used, inventory each value with its name and type. For a multilingual site, also open a page and a form in the languages actually published. These checks can be assigned to different people.

node exercice-websoft-fidji.cjs

Choose a plan and check its scope

Before the change, have the email administrator review the list of values. If only the site address changes, confirm which records to retain and arrange a demonstration recipient who can report the form’s arrival. After the change, separately record results for the page, administration, email reception and form. If a check fails, assign it to the person responsible for that layer.

WP Starter is the first tier to consider for a WordPress brochure site and an annual budget of 899 FJD excluding VAT. If the organization wants more storage, an included domain or the Brizy editor, Turbo publishes those elements and higher relative resources. Supersonic raises storage to 100 GB and displays the table’s highest relative values. For a store or a site with demanding forms, clarify absolute resources and the amount of concurrent work the account can handle. The host recommends Turbo or Supersonic for WooCommerce according to load.

Define the scope in the quote before comparing amounts. List hosting, domain, any migration charges, email and licences that may have their own due dates. Ask for the price payable each year and the notice period if the organization decides to migrate. The quote should also specify who owns the domain and how to transfer it. If Brizy matters to the choice, check the advertised licence and edition availability on the intended domain. An existing site may use another editor and gain no benefit from this builder in its everyday operation.

With access limited to WordPress administration, prepare a procedure for recovering database and files when a plugin prevents login. Before migration, copy the original site, record site and form addresses, and ask what will change in the DNS zone. If maintenance is included, obtain its tasks, schedule and restoration request procedure. The CDN also introduces a layer to check after cutover. If the new page is slow to appear, record the expected content and specify where caching is managed.

During preparation, the site team must have authorized zone access and the list of services declared in it. If another provider manages the domain, check who may change site addresses. Keep a copy of records, note what must remain identical and decide who checks WordPress sending. For demonstration messages, use recipients who can report receipt and record the test time. A domain may continue receiving email while a form sends to an incorrect address.

After cutover, check several pages, media links and administration access. Ask another person to submit a test form and confirm receipt. If it fails, compare DNS, cache and sending settings. The original copy must remain accessible until agreed workflows function and data received during the transition has been transferred. On the due date, separately check domain, hosting and email status.

The tracking file should also retain contact details for each service’s owner. If the email provider remains in place, inform it only of changes likely to affect its settings. For the next renewal, record the date and amount on the proposal received and update the overall cost with separate options. The organization can then recover each service’s scope even if someone else takes over administration.

Prepare your site

• WordPress form: confirmation displayed but email not received
• WordPress XML export and full backup: check what you can restore
• Invisible WordPress change: find and clear the right cache
• Download the migration-check exercise