dhosting.pl: WordPress in Poland, prices and usage-based resources

Who dhosting.pl 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

Polish on the offer and help pages consulted.

Control panel

dPanel and guides in Polish; French availability in the account not established.

Support

Email advertised 24 hours a day, 7 days a week. Telephone from 9 to 17 Monday to Friday according to the contact page. French not established.

Two ways to fund the same type of site

Official hosting provider logo.

dhosting.pl offers Start Web Hosting and Elastyczny Web Hosting for WordPress sites and other applications. Both use dPanel to manage sites, domains and access. Start targets projects fitting fixed resources. Elastyczny adds a resource reserve the customer can enable and pay for according to consumption.

Read base resources, usage ceilings and conditions for returning to normal together. A brochure site may fit Start’s fixed resources. A store handling spikes must also examine what happens when its budget or resource ceiling is reached.

The catalogue also presents configurations tailored to larger needs. These have separate pricing, and their maximums must not be presented as specifications of ordinary annual plans. This profile covers the two publicly priced cards and their documented procedures.

First-year price and ongoing cost

When recorded on November 3, 2026, Start displays 39 PLN excluding tax for the first year and 229 PLN the following year. Elastyczny displays 99 PLN excluding tax for the first year and 399 PLN at renewal. First-year prices compare entry costs. The regular price is a more useful baseline for budgeting a site lasting several years.

Keeping both displayed references, the initial period plus first renewal would total 268 PLN excluding tax for Start and 498 PLN for Elastyczny. These exclude the domain and additional resource use. They represent two years at current references, and future renewal pricing may change.

The page displays net and gross prices. Figures retained here are net prices in zloty. Verify invoicing, acceptance of a French account holder and applicable VAT. Clarify accepted documents and payment methods before any transfer; a Polish-language page alone is not a residency restriction. The offer also displays a fourteen-day trial and thirty-day commercial guarantee. Check refund terms and treatment of options when subscribing.

A banner advertises a 200 PLN consumption bonus for Elastyczny. General scaling documentation also mentions a 5 PLN starting credit. The first amount corresponds to the offer page’s promotional display. Confirm conditions, duration and whether the credits can combine. The credit concerns resource consumption.

Base resources and account quotas

Start displays 25 GB NVMe storage, 3 GHz processor capacity, 4 GB memory, two sites and three email mailboxes. Elastyczny advertises 50 GB, 3 GHz, 8 GB memory and site and mailbox counts without a displayed ceiling. For an account containing several sites, read these resources at service level. Advertised site count does not reserve an entire resource set for each.

Transfer is advertised as unlimited on both offers. Storage, memory and computing limits still apply. A store may need more memory despite modest transferred traffic. Conversely, a media collection may primarily consume disk. Compare project load and volumes with resources actually included.

The public table shows a cross for Start resource scaling and a check mark for Elastyczny. Reading only the shared label may suggest both offers have the feature. Before transfer, check active site count, required mailboxes, file and database volumes and access needed by the team.

First approach: install WordPress in dPanel

This workflow assumes an active account and available destination. It creates an installation; it does not migrate posts or orders from an existing site. Prepare the desired domain or subdomain, administrator access and a location containing no installation that must be retained. The provider’s guide is old: check actual account labels without reusing version numbers shown in its screenshots.

The Pusta strona WWW option prepares an empty location for your own files. The guide allows setting its directory, PHP version, transfer account and associated database. An existing directory may be reused: check its contents before confirming. For migration, import a consistent file and database copy, then check the result at a preparation address. If creation does not meet the need, keep the source and examine only the new instance; do not erase a shared domain or database.

1. If the external domain is not yet linked to the account, open Domeny, then Zaparkuj domenę. Enter only the relevant domain. This association prepares management in dPanel; examine DNS separately before switching a live site over.
2. In Strony WWW, choose Dodaj, then Aplikacja WWW. Select WordPress and the intended domain or subdomain. Check the destination, proposed version and requested details, then run Dodaj stronę only when the target is correct.
3. Wait for installation to finish. Open Pokaż dane dostępowe and keep access details in protected storage. If the window is closed, the guide lists Akcje, then Dane dostępowe next to the site. Do not include this information in a public message.
4. Check the homepage and administration at the correct address. For HTTPS, verify the certificate covers the name used. Choose a maintained PHP version compatible with plugins; old versions appearing in a list does not make them suitable for a new site.

AI creation and bot controls address two needs

Kreator Stron AI is presented as included in the hosting offer. It prepares a WordPress site from project information. The guide describes selecting the topic and name, then generating an initial site found in WordPress administration. The creator page advertises layout, text and image features plus conversational help.

The page distinguishes a draft accessible for seven days from an advertised fourteen-day hosting trial. Keeping the site then depends on the account and plan. Check generation rights and limits, information sent to the service and elements remaining usable after migration. The host presents the result as editable in WordPress. Assess portability of each AI feature.

AI bot controls concern automated access to hosted pages. They are access and consumption settings. The creator acts on site content. For existing WordPress, the standard workflow remains available and preserves theme and plugin choice. Review every generated proposal before publication, especially if it contains prices, contact details or commercial promises.

Second approach: control resource consumption

On Elastyczny, start with project statistics and resources included in the subscription. The additional feature is enabled with customer agreement and uses a prepaid balance charged according to hourly consumption. Spending budget and the technical CPU, memory or storage ceiling are separate settings. Know both before preparing a traffic spike.

When the balance runs out, the documentation describes a return to base resources. A site dependent on extras may then slow down or no longer handle the same processing. Plan for this before a commercial event and identify who can adjust the budget. Setting a ceiling protects a spending allocation; it does not guarantee application availability.

1. Record current limits and consumption balance. Define the amount the project can spend on extras and check promotional-credit conditions; do not assume it combines with the starting credit in general documentation.
2. In dPanel, open Zarządzanie limitami. In the spending block, use the command to change limits. The guide allows daily, weekly and monthly ceilings. Save selected values and verify their display.
3. Examine resource ceilings and feature status separately before activation. During the planned period, monitor statistics and spending. A positive balance is insufficient: documentation states that reaching a spending ceiling also disables resource increases.
4. After the peak period, compare spending with expected need and restore normal settings if load permits. Keep initial values for returning to the previous configuration. Before lowering a ceiling, check site needs and occupied space; do not delete data to force a return to a smaller allocation.

Read hourly prices without overstating the ceiling

The calculator presents two reference tiers. For CPU, it associates 12 GHz with 0.1323 PLN excluding tax per GHz per hour, and 24 GHz with 0.1590 PLN. For memory, it displays 32 GB at 0.0882 PLN excluding tax per GB per hour and 64 GB at 0.1056 PLN. For storage, references are 500 GB at 0.0008 PLN excluding tax per GB per hour, then 1,000 GB at 0.001 PLN. These rates describe additional resources; they are not automatically charged across resources already included in the subscription.

Check the tier applicable to the account, extra quantity used and duration before estimating. For CPU, the guide describes average use measured over time, with hourly balance deductions. A one-second spike therefore does not equal an entire hour at the displayed maximum. Storage retained for weeks and a brief memory boost generate different costs.

The 24 GHz, 64 GB memory and 1,000 GB disk ceilings concern the ordinary mechanism described by the calculator. Larger quoted configurations are a different scope. A GHz value is not a reserved physical core count, and the table does not describe a dedicated server. To decide, combine subscription, estimated extras and useful budget headroom without converting marketing visitor examples into guaranteed WordPress capacity.

Third approach: recover files without overwriting the site

The table advertises a backup every twenty-four hours and the latest seven copies. Before recovery, identify incident time and points actually available. The procedure below retrieves files into a separate directory; it does not automatically restore a database or store orders.

The expected result is initially a dated, readable copy retained outside the account. Replacing files, restoring the database and restoring email are separate operations. If a point is missing or a copy lacks the desired object, ask support about available scope. In production, keep a current-state export and handle recent writes before replacing a database. Returning to files saved before intervention may undo a code change; it does not merge two order histories.

1. In dPanel, open Strony WWW, select the site, then Kopie zapasowe. Check the domain and choose the point preceding the problem.
2. Click Przywróć, then confirm recovery. Wait for completion: the provider states that duration varies with file volume. Do not start several recoveries to accelerate an ongoing task.
3. Examine the dated directory created under ~/backup, the account backup directory described by the guide. Find site files and download the copy through authorized transfer access. This path does not imply server-administrator access is needed. Active files remain unchanged by this step.
4. Before replacing a file, retain its current version and check the destination path. For a limited incident, recover the necessary file. For an application set, check consistency with the database at the same date, then validate on a protected copy without real payments, sending or synchronizations.

Prepare migration respecting the offer’s quotas

The migration page advertises up to fifteen sites and thirty mailboxes within its general free scope. It displays 44.50 PLN per additional site and 1.50 PLN per additional mailbox. Tax treatment of these amounts is not specified in the selected passage. Check target-plan capacity. The general migration ceiling does not give Start fifteen sites and thirty mailboxes.

The fast option advertises up to three sites totaling 30 GB and fifteen mailboxes totaling 60 GB, with a request before 11 on a business day. It also depends on scope and access. Use only the designated migration channel to send necessary access details and retain an independent copy.

Check the target before repointing the domain. Verify pages, email, certificates and scheduled tasks. An active store requires a plan for new orders during copying. Keep old DNS and the old service until validation. If rolling back, examine data already written at the new destination.

Support languages and scope

The offer and guides examined use Polish. The contact page states that email inquiries are handled at all hours every day. Telephone service is advertised from 9 to 17 Monday to Friday. French support and dPanel session-language options remain to be confirmed. The company’s Warsaw address does not locate the account and backups: clarify those locations if the project depends on them.

The sales page advertises a 99.9% uptime commitment. Calculation method, exclusions and compensation conditions are not established by the sales card alone. A team depending on a recovery deadline must check the commitment’s scope and time needed to retrieve its own files and database.

The installer prepares WordPress and the AI creator helps build an initial site. For production, assign someone to maintain plugins and check update effects. Managing the account and fixing store functions are different needs.

Renew or prepare departure in dPanel

Rates are displayed for an initial year and the following year. Check the domain, options and consumption credit separately. Before expiry, record dates, items to retain and the account’s actual extension method. A renewal reference does not prove every customer has configured automatic payment.

The exit guide describes Zaawansowane, Faktury i płatności, then Akcje and Rezygnuję z usługi. This option opens a cancellation request. For termination at expiry, the same help states that nonpayment of an extension leads to suspension and then deletion. Check the termination date and applicable terms before choosing, especially if a domain must remain active.

Export database, files and messages before any closure request, then check the new destination. Start offers a quantified allocation for a small number of sites. Elastyczny becomes relevant if the larger base and consumption budget address a measured need. The choice depends on regular cost, intended use and ability to recover data.