Domeneshop WordPress: new platform, NOK prices and AI

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

New platform mainly in Norwegian; old multilingual catalog and current documentation in Norwegian and English.

Control panel

Old Min konto or new account depending on the customer record; cPanel only in the corresponding range. Private interfaces not tested; French workflow not confirmed.

Support

Contact and documentation available in Norwegian; written help also in English. A commitment to spoken support in English or French has not been established.

A Norwegian host with two distinct environments

Domeneshop AS is a Norwegian provider of domains, hosting and email. It advertises Web servers in central Oslo and a direct connection to the NIX exchange point. For WordPress, its value mainly depends on the platform actually sold, the access available and backup responsibilities. A package name is not enough to identify all of these details.

Since the launch on June 8, 2026, new customers have been directed to a new platform, while existing customers have a separate login. The website explicitly states this. The documentation therefore includes guides for the old account area, the new Essential hosting and cPanel services. A procedure that works in one may be unusable in another.

This profile, prepared on November 3, 2026, focuses on the new catalog. It retains details of the old environment where they explain a specific difference, particularly AI and backups. No account or order was created. The caveats concern observed discrepancies and are not practical test results.

Current plans and annual budget in Norwegian kroner

The new Web range displays four annual amounts: Light at 468 NOK, Standard at 828 NOK, Pro at 1,188 NOK and Max at 1,548 NOK. The page states that its prices include 25% VAT and apply to customers in Norway. The cards show an annual cycle; dividing the amount by twelve provides a budgeting reference, not proof of monthly payment.

No separate introductory promotional price appears for these four packages. These amounts therefore serve as current renewal references, subject to the terms governing changes. The domain costs extra. The first invoice must confirm any fees, the billing address and tax treatment; a French buyer cannot reuse the Norwegian tax-inclusive total without checking.

A separate cPanel range displays 804, 1,164, 1,500 and 2,004 NOK per year for Light, Standard, Pro and Max. Compare these plans according to the panel you need, rather than assuming cPanel is a feature included in every Web package. The cPanel page also states that Norwegian VAT of 25% is included for customers in Norway. The quote must specify which of the two services is ordered and how your billing address is treated. No French checkout was validated.

Web resources and differences from the old catalog

On the new platform, Light advertises 1 GB for the Web, one database and one linked domain. Standard increases this to 25 GB, ten databases and ten domains; Pro to 50 GB, twenty-five databases and twenty-five domains; Max to 100 GB, fifty databases and fifty domains. Domain limits are not a guarantee of fifty simultaneously active WordPress sites: they must be assessed against execution resources.

The old catalog remains visible with different figures: 5, 20, 100 and 500 GB for the four package names. Its guide requires at least Web Standard for WordPress because the old Light lacks PHP and MySQL. The new Light advertises a database, but that alone does not certify all the PHP capabilities your installation needs.

Before choosing, record media volume, database sizes and plugin dependencies. Have the PHP limit and process restrictions confirmed for the product being sold. The new profile does not publish CPU capacity or guaranteed throughput per site here. Traffic described as unrestricted remains subject to the usage and stability limits in the contract; it is not unlimited processing power. Applying the old Max’s 500 GB to the new Max would be a significant sizing error.

Email: retain the discrepancy between cards and table

The new Web cards advertise one, five, twenty-five or fifty mailboxes depending on the package. They all state 1 GB per mailbox and a standard size of 1 GB. Further down, however, the comparison table displays per-mailbox capacities of 1, 5, 25 and 50 GB. This is a discrepancy on the same page, not additional capacity that can be taken for granted.

The general text also retains wording about an unlimited number of addresses, while the cards count mailboxes. A forwarding address, an alias and a mailbox storing messages are three different uses. To prepare a transfer, inventory each mailbox, its volume and essential forwarding rules, then obtain the contractual quota actually available.

The old environment still advertises 15 GB accounts and higher mailbox counts. Those values are not used to artificially supplement the new package. A migration from an old account to the new range must be checked as a resource change. If in doubt, keep an independent message archive before changing the product or incoming-mail settings.

Identify the account, language and technical responsibility

The login guide asks you to choose the access corresponding to when the customer was created, before or after the June launch. Start with this check if a documentation screenshot does not match your screen. The new account area shows active products; some provide cPanel access, while others provide the Essential service assistant. The presence of cPanel guides in the help center does not give that panel to every customer. The cPanel installation guide even contains an isolated mention of Plesk in its introduction, although its title and steps concern cPanel: this inconsistency does not prove that a second panel is supplied.

The commercial pages examined are mainly Norwegian, and the help center also offers articles in English. This provides a documentation route for a non-Norwegian team without establishing a support commitment in every language. No complete French workflow was confirmed. For a customer in France, requested identification, eligibility and invoicing still need to be clarified before purchase.

The contract leaves customers responsible for maintaining the software they install. Assign someone to WordPress, themes, plugins and licenses. Any automatic updates do not prove that a human checks forms or orders. A managed Cloud plan mentioned in the terms is a different service: its guarantees do not automatically extend to the Web packages examined.

Install WordPress on the new Essential hosting

1. The new-environment guide explicitly concerns Essential Multi-hosting Website. You need an active service, an available database and a virtualhost, meaning the Web address configured to reach the site. In the customer area, open the hosting service and then its WordPress assistant. If the product uses cPanel, follow the workflow in the next section instead.
2. After checking the database and address, choose the site title, domain or subdomain, then the path in advanced options; the guide suggests public_html by default. Next enter the administrator username, email address and a strong password. Review the destination before selecting Install WordPress. An empty destination and an identified database prevent this new trial from becoming mixed with an existing site.
3. The service view should display WordPress deployed successfully when the operation is complete. Open the public address and its administration area, check HTTPS and preview a page. This result comes from documentation: it was not executed for this profile. To cancel a trial, export any useful elements, then remove only the identified installation. Reinstallation must not replace a production WordPress site without a backup.

Choose the cPanel workflow when the service includes it

1. For a cPanel plan, open the product in the list of active services, then select Logg inn på cPanel. The guide places Wordpress management in the domains section. Start the installation and check the path, title, version, administrator details, database and automatic-update options before confirming.
2. The expected result remains the same: an accessible administration area, the correct domain and a site loading over HTTPS. For multiple projects, use easily recognizable database names and destinations. Do not point a trial at a live store’s database. The hosting panel and WordPress have different permissions: knowing how to access the commercial account does not replace control of each site.
3. This workflow then provides the WP Toolkit features documented for cPanel. It does not prove that the old Min konto has the same buttons or that the provider’s automatic copies cover the same scope. If you mainly want a WordPress management tool, compare this convenience with the annual cPanel range price before ordering a Web plan solely because its name is similar.

Documented AI: useful, but tied to the right plan

Screenshot published by Domeneshop for Sidebygger AI in the former environment. It illustrates its template library, not the new account or cPanel; no test performed for this profile.

The old catalog offers Sidebygger AI for WordPress with Web Pro and Web Max. Its getting-started guide describes choosing the product during quick installation, followed by questions about the site’s title, description, tone, goals and structure. Generated pages can then be edited in WordPress. The official visual associated with this section shows the template library of that old environment, not an account opened for this profile. This workflow must not be presented as a feature already confirmed in each new package.

The usage documentation shows a site assistant, template library, chatbot and text or image creation. It explicitly limits generated images to ten per day. No unlimited text quota, guaranteed model or right to retain assistance after leaving is established here. Access to library photographs also requires checking their license.

For an eligible old account, the documented route is Webhosting > Kom i gang, then selecting Sidebygger AI for WordPress, the address and credentials. A new installation at a separate destination remains preferable for exploring the result. Review content before publication and keep its previous version before replacement. On the new platform, have inclusion and activation confirmed instead of assuming that the Pro name alone guarantees them.

Back up according to the scope actually available

The old hosting guide is explicit: infrastructure copies protect the servers against their own incidents and do not guarantee recovery of an individual Web account or mailbox. Customers must keep their files, databases and important email. This caveat must not be converted into a guarantee of daily backups that can be restored on demand.

In the old Min konto, exporting a database without a plugin follows Mine domener > domain > Webhotell > Se på/endre on the MySQL line, then the database menu and Eksporter. The download contains an SQL file in an archive. Pair it with a copy of files and media kept outside the account. The guide notes that a very large database may require another method.

The new cPanel environment has a guide for WordPress copies through WP Toolkit. It concerns the selected site and does not automatically archive all email or the entire account. For the new Web Essential, automatic retention and recovery service must be confirmed separately. Do not select a plan based on a number of backup days that its documents do not establish.

Create and restore a WordPress copy in WP Toolkit

1. On a cPanel service with a recognized installation, open WordPress Management, locate the correct site and select Back Up / Restore. Back Up creates a point that appears in the available copies list. Make this copy before a major update and download anything that must remain available outside the hosting account. An archive stored only in the account is not an independent copy.
2. Before recovery, also preserve the current state and record orders or messages received since the selected point. If the problem affects only a file, plugin or old paragraph, first look for a targeted fix or examine the backup on a copy; the Restore button does not merge states. In the same area, choose the point, its Restore action, then confirm. The guide warns that later changes will be overwritten. Choosing the correct site and date therefore comes before confirmation; do not restore every project to fix a single plugin.
3. After the completion message, check the administration area, pages, media and business data. On a store copy, disable payments, email and synchronization before testing. If the restored point is unsuitable, the copy made just before the operation provides a possible rollback. This procedure does not demonstrate any automatic backup frequency: it describes managing a recovery point created or available in the tool.

Plugin compatibility and migration of an existing WordPress site

The old-environment documentation separates two lists. Updraft (Plus) and BackWPup appear among explicitly prohibited software; All-in-One WP Migration and Wordfence appear in the section asking customers not to install them, titled “software to avoid.” These assessments are the provider’s, within this specific scope, and do not constitute our audit of those plugins. The document names Duplicator and Akeeba Backup as alternatives. Before transfer, have the destination product’s rules confirmed; do not automatically apply this list to the new Web service or cPanel.

The plugin-free route consists of preserving files and the database, preparing a separate destination, importing data into an identified database and adapting the configuration using the supplied credentials. The old guide states that the MySQL server is not necessarily localhost. Do not reuse credentials from another platform or blindly replace addresses stored in the database.

Check the copy before changing DNS and transfer email separately. The scope and price of a migration performed by Domeneshop have not been established for the packages examined; a domain-transfer button does not prove that website migration is free. Keep the source until validation and organize final writes. Reverting DNS does not merge new data.

Plan ahead for support, renewal and notice periods

The new contact page provides a customer-service address and a number usable from abroad. Listed sales hours are Monday to Friday from 9 to 11 and then from 12 to 16. The old footer displays 8–17 for the general number. These statements do not guarantee continuous technical coverage or identical hours for every team.

The terms revised on June 6, 2026 state that written requests receive a response within two business days. This is a documentary commitment, with no measurement performed for this profile and no promise of resolution within that time. Sensitive changes to contact details or DNS must be made while logged in; the contact page refuses to accept them simply by phone or email.

Unless otherwise stated, the contract specifies a one-year term renewed annually, with an invoice generally sent thirty to sixty days before expiry. It requires at least thirty days’ written notice to end the agreement and does not advertise a general prorated refund. Keep the dates and effective confirmation before arranging departure; the current rate is not a permanent guarantee.

Leave without losing the site, domains or email

Before cancellation, keep files, databases, useful messages and DNS settings, then verify that everything works at the destination. The old guide asks customers to contact the provider to stop or downgrade services linked to a domain. For the new account, identify the relevant product and have its end date confirmed; do not automatically use a menu described for the old environment.

One contractual point needs particular attention: transferring a domain to another provider is considered cancellation of associated services unless advance notice requests that they remain active. Moving only the address can therefore affect hosting or email. Define in writing what must remain active until the switchover ends, and keep the response.

Domeneshop may suit a Norwegian project that wants to retain control of its data and administration. Choosing nevertheless requires distinguishing platform, panel and contract, then clarifying contradictory email quotas and recovery capabilities. For a small WordPress site, first compare Web Standard and cPanel Standard: the latter currently costs 336 NOK more per year and provides access to the documented cPanel workflow. This extra cost should meet a real management need, without inventing a speed benefit. Web Light needs confirmation of its WordPress scope; a store also needs commitments on resources and recovery. AI should not determine the purchase of a new Pro or Max until its inclusion is confirmed.