AMATETA in Namibia: managed WordPress and renewal

Who AMATETA Hosting 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 for the reviewed pricing table, terms and SLA.

Control panel

Customer area and WordPress. Confirm available languages after login.

Support

Team in Windhoek, email, telephone and tickets. Confirm languages. Severity-based targets in the SLA.

AMATETA Hosting for WordPress in Namibia

AMATETA Hosting offers two managed WordPress plans in Namibian dollars. The table distinguishes one site with WP Lite from up to five with WP Business. The terms detail renewal reminders, deadlines after the due date and price changes.

The scenario follows an organization whose domain, WordPress hosting and email do not expire on the same day. The exercise turns a fictional renewal notice into checkpoint dates. It lets you check a price change and identify steps to take before the account or its copies become inaccessible.

Namibian-dollar prices and deadlines

The general pricing table confirms monthly and annual amounts. The WordPress plan selector also publishes two-year amounts in its card data. With the displayed 15% VAT, calculated annual totals are NAD 1,138.50 for Lite and NAD 2,173.50 for Business, before any other line items. The billing term matters when reading the invoice. A two-year plan’s monthly equivalent is not a monthly payment. The terms specify Namibian-dollar amounts and VAT itemized on the invoice.

The terms dated October 29, 2026 provide for a renewal invoice 14 days before the due date, then reminders 7, 3 and 1 day before. Prices may change with 30 days’ notice, effective at the next renewal. The terms provide three grace days, after which an unpaid service may be suspended, and allow termination from 30 days overdue with a risk of deletion. Read the future amount and applied payment method on the notice or confirm them with support. The domain has its own due date and rules. The 30-day guarantee covers a first WordPress order under the terms. Customers may request immediate termination or termination at the period’s end from their account area.

Resources and the scope of WordPress management

Both plans include WordPress installation, LiteSpeed with LSCache, daily backups and staging. The page describes scheduled updates to core, themes and plugins, with advertised automatic rollback when an update fails. For a shop, ask which failures trigger rollback, how it affects new writes and when a ticket is opened. Staging makes testing a copy easier. Define the publication scope before synchronizing data with the live site.

Lite advertises malware scanning, and Business adds removal, Redis object caching and priority support. The direct page says SSL certificates are available. Confirm the included basic certificate, its coverage and any option prices before ordering. The general table shows ten mailboxes on Lite and fifty on Business. The WordPress page does not detail mailbox capacity, email retention or their use of SSD space. Clarify these figures on the selected plan’s order.

Three or eight gigabytes require tracking media and copy sizes, especially if staging counts against the same account. CPU and memory capacity, file limits and PHP versions are not listed on these cards. Being able to install five sites does not establish processing capacity for each. To compare the plans, inventory the shop’s size and demanding operations, particularly product imports and image-generation tasks.

Languages, assistance and data location

The public site and its terms are in English. AMATETA places support in Windhoek and publishes a support address, local telephone number and ticket channel. Confirm languages available after login and those in which incidents can be handled, particularly Afrikaans. Priority appears in WP Business specifications. To organize recovery, also consult the SLA’s severity-based response targets and ask how Business priority changes handling. First-response and resolution times convey different information.

The SLA locates support, billing and account administration in Windhoek. It mentions international data centres without specifying the WordPress server country or copy country for each plan. Before processing registrations or orders, ask where the origin and backups are located. AMATETA advertises free WordPress migration for files, the database and permalinks. Clarify what email data is transferred and who coordinates DNS. If access is needed, request an approved channel and temporary credentials rather than reusing the account’s permanent access.

Backups, deployment and the SLA

The SLA advertises 99.9% availability for WordPress. It distinguishes an outage from a slowdown while the site remains reachable. Target response time is 30 minutes around the clock for a critical outage and two hours around the clock for a major-function failure. Less urgent requests follow the working hours specified in the document. To apply this classification to a membership site, record whether pages, forms and notifications each work independently. A form failure may justify a request even if the site responds.

The SLA publishes seven days of retention for daily WordPress backups and four weeks for weekly backups, with one free restoration per month. Additional restorations may incur administrative fees. The terms require an external copy and note that recovery after termination is uncertain. Check backup coverage, the restoration-request procedure and recovery turnaround. For the site in this scenario, try restoration on an isolated copy before depending on the service for the next membership cycle. Check files and database separately, then their consistency at the same recovery point.

The page advertises pushing changes from staging. Before using that feature, ask whether deployment selects files or tables and how it handles recent production changes. Keep a record of the cloning time and writes to preserve. When changing a form or payment flow, disable external messages and synchronization on the copy, then use the payment provider’s test mode with its fictional payment methods. A fictional recipient address is not enough to prevent a real transaction. Then validate the main functions in production.

AI and the site builder

The WordPress plan describes a manager, installation, updates and staging. It does not publish an included generative assistant or AI quota for WP Lite or WP Business. The advertised security scans and rollbacks are operational features. Their automation does not document a writing assistant for WordPress. If the organization needs a generation tool, ask whether it is supplied separately or requires a plugin and external subscription.

AMATETA lists another product, Site Builder Plus, with visual editing and templates. Its FAQ presents moving to WordPress as an assisted migration. It does not promise inclusion of the builder in the WordPress plan or AI page generation. To choose between the services, establish where pages will be edited and in which formats files, forms and content can be retrieved. For an existing site, inventory essential content before deciding how to transfer it.

Local exercise: checking the renewal calendar

The model applies the stated intervals to a fictional date. Check the date and amount shown on your invoice. — Illustration by BlogPasCher.Open full-size illustration ↗

Goal. Build a calendar from a fictional due date of March 1, 2027, then check the interval between a price-increase notice and that due date. The script counts calendar days using normalized UTC dates. It calculates invoice issuance at D−14, reminders at D−7, D−3 and D−1, the end of the grace period at D+3 and the thirty-days-overdue marker. The example’s rules come from section 3. Confirm the exact time and treatment of a closure day for a real invoice.

Run the command in the extracted ZIP directory with Node.js 18 or later. Compare its output with resultat-amateta-namibie.json. For the fictional March 1, 2027 due date, the invoice falls on February 15 and reminders on February 22, 26 and 28. March 4 marks the end of the calendar-day grace period and March 31 the thirty-days-overdue marker. A January 30 notice meets the thirty-day threshold. A January 31 notice misses it by one day. A notice absent from the file does not prove it was not sent. The result indicates what can be checked from the available date. To repeat the exercise with another fictional due date, change dates and expected results, especially when the calendar crosses February or year-end.

For a real invoice, retain the notice date, billing term, amount excluding tax, VAT and requested total. Track domain, WordPress and email dates separately. Overdue markers guarantee neither suspension time nor copy availability. Arrange exports and payment approval before the due date.

node exercice-amateta-namibie.cjs

Choosing between WP Lite and WP Business

If a price increase is announced, check the effective date and billing term of every affected line. An annual domain and hosting paid for two years may have different dates even if the dashboard displays them together. Keep copies of the notice, invoice and receipt with the next payment date. For a team requiring expenditure approval, set the internal decision date before the first reminder.

WP Lite suits a single site whose files and database fit within 3 GB, with enough room for update and test operations. WP Business provides 8 GB, up to five installations and Redis. The host promotes this second plan for shops. Compare media volume, expected growth, staging needs and resources to confirm with support. Assess advertised capacity against the real site and its temporary data. Before transfer, ask where backups and mailboxes are stored and how they count against account limits.

When choosing a term, record its price and VAT, then clarify the amount due at the next renewal if the order includes a discount or option. The advertised monthly price and annual total allow comparison of first-term costs. Renewal pricing follows the applicable terms and may change with the specified notice. A small team can assign invoice receipt to one person and payment approval to another. Record the term, billed account, contact details and location of the latest external copy. When the notice arrives, check that the amount applies to the expected service and the domain line matches the extension in use.

After activation, check which access is actually supplied, how to open a ticket and where backups are visible. On an authorized copy, try a change and check the files and data a restoration would recover. If a site must remain available during an operation, agree on a pre-publication check and a form check after the change. Divide roles between the person deploying, the person validating and the person deciding on rollback if a function breaks. Keep support contact details and the ticket number somewhere the team can access during an incident.

When renewal is uncertain, separate the decision to continue the plan from data protection. First verify that the site and database have a recent copy that opens. Then confirm the actual due date, amount due and procedure if renewal is late. A billing incident may also block access to a backup hosted in the same account. Keep independent copies and instructions to restore the site and DNS if the service must move. For an organization, the person controlling the domain may differ from the person managing WordPress. Record both responsibilities.

For the next renewal, repeat the exercise using the actual notice dates after verifying them. If the increase notice and invoice arrive at different times, retain both documents with their dates. A discrepancy flagged by the check can be discussed with support using the invoice number and term. The team can keep the same checking method when adding sites to WP Business or renewing a domain on another date. Once payment is confirmed, enter the next due date in the shared calendar and check that billing contacts can receive reminders. For an account managed by a service provider, agree who may request a copy and how access will be returned when the contract ends.

If renewal coincides with a busy period, agree on an internal approval date and an available payment method. Put other due dates on separate lines so that one payment is not mistaken for payment of another service.

Prepare your site

• WordPress changes not visible: find and clear the right cache (in French)
• Noindex after WordPress staging: make the right pages indexable (in French)
• WordPress XML export and full backup: check what you can restore (in French)
• Download the renewal-calendar exercise