Servers that come with engineers attached
Most hosting problems are not hardware failures. They are an unpatched package, a backup nobody has ever restored, a mail domain without DKIM. We sell cPanel hosting, VPS, dedicated and GPU servers together with the hours needed to look after them, so someone who knows your stack can act before a small issue becomes an outage.
Compliance and data protection
We treat data security, traceable actions and GDPR compliance as defaults, not add-ons. An Article 28 data processing agreement is included, and standard contractual clauses cover transfers outside the EEA. Our practices are aligned with ISO 27001; that is alignment, not a certificate.
How the model works
Four product lines cover the usual path: cPanel hosting for websites and mail, VPS for root access and containers, dedicated servers for sustained load, and GPU servers for AI and ML workloads. Dedicated servers carry a 99.99 % SLA.
Engineering hours are part of the plan, not a separate contract:
- cPanel: 1 h per month from cPanel Advanced upward; entry plans include no hours.
- VPS: 1–8 h per month, depending on the plan.
- Dedicated servers: 5–10 h per month, depending on the plan.
- GPU servers: 10 h per month.
You request hours from the client panel, under DevOps services, and propose a deadline. The team delivers. Hours are not carried over to the next month; work beyond the quota is accepted and billed separately.
Where we operate
4hosting is operated from Romania and serves customers in many countries, with the website available in several languages. Servers run in European Union datacentres in Frankfurt. Support is available in English and Romanian.
Local VAT is shown separately on every invoice; the pricing page has the plans and billing details. 4hosting belongs to the 4b2b ecosystem, which also includes invoicing, accounting, CRM and notification products.
How we work
Three habits that shape every request.
Measured by results
A task is finished when the server, the pipeline or the mailbox works for you, not when a ticket is closed.
Plain terms
Plans, included hours and limits are stated up front, and we say so when a request falls outside them.
Tested first
We test each critical flow before it goes live, and we recommend restoring backups on a schedule instead of trusting them.