How is Yhost different from a typical hosting provider?

We do not build the platform around mass resale logic on overloaded nodes. Our focus is on a clean open source stack, resource isolation, and a defined operational model for real business workloads. At the managed level, we operate applications — Odoo, Keycloak, Nextcloud — not just the server underneath them.

You are a small team. What happens if something breaks at 2am?

Monitoring runs continuously and alerting is configured on the infrastructure and application layer — not on a human checking a dashboard. For managed tiers, incident response is part of the service scope. Whether the response is immediate or within a defined window depends on the SLA tier. We will tell you clearly what the response commitment is before you sign up, not after an incident.

Where are your servers physically located?

Infrastructure runs on Hetzner and UpCloud in Germany. Data residency for all managed services is EU — Germany specifically, unless you request a different EU location. Yhost operates under Apefo Ltd, registered in the UK. We can provide a Data Processing Agreement that reflects actual data flows.

Can you handle our procurement process — DPA, security questionnaire, vendor review?

Yes. We can provide a DPA template, respond to vendor security questionnaires, and produce a written scope statement that defines responsibilities clearly. Tell us upfront what your procurement process requires and we will prepare it as part of the initial conversation rather than after a decision is made.

What does self-managed mean in your model?

Self-managed means the customer controls the application, code, CMS, plugins, and business logic. We manage the platform, hosting environment, network layer, and baseline service stability. That keeps costs rational where full managed scope is not required. The managed tiers exist for when you want us to own the operations layer entirely.

We are on Odoo.sh or a self-managed VPS. How does migration work?

Migration is a risk management task, not a file copy. We review your current setup first — database size, modules, custom code, integrations, user count — then produce a migration plan with a staging validation step before anything touches production. Production goes live on Yhost only after staging has confirmed everything works. We handle the technical execution; you confirm the validation.

We have budget constraints. Can we start small and move up?

Yes, and that is explicitly how the platform is structured. A company website on Smart Web Hosting at €0.59/mo and a managed Odoo instance at €399/mo run on the same underlying infrastructure logic — same stack decisions, same engineering approach, different operational scope. You do not switch providers as requirements grow. The path from shared hosting to managed VPS to operated application is a deliberate part of the model.

Do you offer support in German?

Yes. Support is available in English and German. For clients operating in DACH, we can handle technical and operational communication in German throughout the engagement — including documentation, scope statements, and incident reports.

About Yhost and Our Smart Hosting Engineering Approach

One Provider Across the Entire Infrastructure Path

Most companies start somewhere simple and grow into something more complex. The infrastructure tier that made sense at launch is often not the right fit twelve months later. Yhost is built for that progression — the same stack, the same team, the same engineering logic at every level. You do not switch providers when the project gets serious.

Open source stack, not license overhead

Many providers wrap standard control panels around average infrastructure and call it premium. cPanel costs around €45 per server per month. Plesk is not free either. Every platform that abstracts the server layer passes that cost into your price — in the line item, or in slower hardware underneath.

We run NGINX or OpenResty, PHP-FPM, MariaDB or PostgreSQL, Redis. Open source, tuned directly. The money that would go to licenses goes into better hardware and operational depth instead. That decision is visible at every tier — from €0.59 shared hosting to a fully operated Odoo or Keycloak platform.

What this means in practice

100% NVMe Storage
Storage latency is where most CMS and ERP performance problems actually live. NVMe is the baseline across all tiers, not a premium add-on.

AMD EPYC Processors
Modern CPU resources keep dynamic workloads responsive when traffic and background processing increase simultaneously.

OpenResty on Managed Tiers
Standard NGINX reads config. OpenResty runs logic — rate limiting, WAF, dynamic routing — at the request layer before the application is involved.

Linux-Level Isolation
One account hitting limits should not affect the next. Resource isolation is a platform decision, not a plan feature.

From a €0.59 site to a managed enterprise platform

Different projects need different levels of control and operational scope. Some teams need an affordable self-managed environment with a clean stack. Others need a fully operated platform where infrastructure is someone else's responsibility. Yhost is built to support that progression without a provider change at each step.

Smart Web Hosting — from €0.59/mo
A lean NGINX and NVMe baseline for business websites, landing pages, and smaller projects. No cPanel overhead in the price.

WordPress and WooCommerce
Redis object cache configured for how WordPress behaves, not just installed. WooCommerce-aware cache bypass so cart and checkout work correctly under load.

Cloud VPS — Hetzner and UpCloud
Root access on AMD EPYC hardware in Germany. For engineering teams that need to own the full environment — OS, stack, deployment model, firewall policy.

Managed Premium
VPS-level control without the operational overhead. OpenResty with Lua, monitoring with real alerting, managed updates and backups, SLA-backed support.

Managed Solutions — Odoo, Keycloak, Nextcloud, n8n
Operated platforms for teams that want to own their software without running day-to-day infrastructure themselves. Each application managed for how it actually fails, not as a generic hosted service.

Operated means operated — not just deployed

We are a UK registered company operating infrastructure for B2B teams that need stability, clear scope, and direct communication. That includes agencies and developers at the shared and VPS tier, and finance, operations, and IT teams at the managed platform level.

What we mean by managed

Monitoring with real alerting
Not a human checking a dashboard. Alerting configured on the infrastructure and application layer so incidents surface before clients report them.

Updates with a plan
Keycloak major versions change database schema. Odoo updates break modules. We plan releases, validate on staging, and keep rollback paths available. Updates do not happen without a defined process.

Backups with tested restores
A backup that has never been restored is not a backup. We test restore procedures on a schedule and can demonstrate the process during onboarding.

Transparent scope
We define what we manage and what the customer manages. That keeps expectations clear before an incident, not during one. If your procurement or security team needs a written scope statement, we can provide it.
Talk to the team about your project.

Three Decisions That Shape Everything Else

These are not features we added. They are the foundation the platform is built on.

Open Source Stack, Not License Overhead

cPanel costs €45 per server per month. Plesk is not free either. We run NGINX or OpenResty, PHP-FPM, PostgreSQL, and Redis — open source, tuned directly. The money that would go to licenses goes into better hardware and operational depth instead. That decision is reflected in every price on this site.

Germany by Default, Not by Option

Infrastructure runs on Hetzner and UpCloud in Germany. That is not a GDPR checkbox — it is where we operate. User data, authentication logs, ERP records, and backups stay in EU jurisdiction. For businesses operating under GDPR or working with German Mittelstand, that matters before you sign a DPA, not after.

Isolation That Holds Under Load

One account hitting limits should not affect the next. We use Linux-level process and resource isolation so your site or application behaves predictably regardless of what else is running on the same hardware.

A Defined Managed Scope

We define what we manage and what the customer manages. That keeps scope understandable, pricing credible, and operational expectations clear before the project goes live — not during an incident.

Application-Specific Operations

Odoo, Keycloak, Nextcloud, and n8n do not fail the same way a WordPress site fails. We operate each platform with its specific failure modes in mind — PostgreSQL vacuum for ERP, schema migration for identity, queue saturation for automation. Not generic hosting with a product label.

Infrastructure Without the Abstraction Layer

Managed hosting and operated platforms for European businesses.

Yhost is a small infrastructure team. We run hosting and managed platforms — Odoo, Keycloak, Nextcloud, n8n, and others — for companies that want to own their software stack but cannot afford to run operations themselves.

We work from Germany. Infrastructure runs on Hetzner and UpCloud in Germany. Data does not leave EU jurisdiction. That is not a feature we added — it is where we started and how we are built.

We do not use cPanel or Plesk. Not because it is unconventional, but because license costs go into your price without going into your performance. We run OpenResty, PHP-FPM, PostgreSQL, and Redis — tuned directly, not abstracted away. That decision shows up in what we can offer at €0.59 on the low end and in what we operate at the managed level.

We are a young company. We do not have a wall of client logos. What we have is direct access to the engineers running your infrastructure — not a tier-1 support script, not an account manager. When something needs attention, it gets it from the person who set it up.

Talk to the team

Built for B2B Teams, Not Mass Hosting

Most hosting companies are optimised for volume — thousands of shared accounts, automated provisioning, support by ticket queue. That model works for personal blogs. It does not work when Odoo is running your month-end close or Keycloak is the authentication layer for every internal tool.

Direct access to the engineers

We do not replace technical reasoning with generic replies. When a project needs a serious discussion about environment design, performance, or an upgrade path, you speak with the person who set it up — not a tier-1 script.

NVMe storage and a tuned database layer

Fast storage and a properly configured database stack reduce delay in the admin area, on dynamic pages, and in ERP workflows. Storage latency is where most performance problems actually live — it is the baseline across all tiers, not an upgrade.

Procurement-ready documentation

We can provide a DPA, a written scope statement, and a vendor security questionnaire response. For B2B teams where infrastructure requires sign-off from legal, security, or IT management, that documentation is part of the onboarding process — not an afterthought.

Migration handled as risk management

For a business, migration is not about copying files. It is about risk control. We review the current setup, validate on staging before touching production, and keep the process documented. The goal is that production goes live on Yhost only after staging has confirmed everything works.

Developer tools where they belong

SSH, Git, Composer, WP-CLI, and staging environments are available on the tiers where they are needed. Modern infrastructure should support the team that has to ship and maintain the project, not sit behind unnecessary friction.

A path that scales without a provider change

Start on shared hosting at €0.59/mo. Move to a managed VPS. Step into a fully operated Odoo or Keycloak platform. The same stack decisions, the same engineering logic, the same team at every tier. You do not rebuild when the project gets serious.

Frequently Asked Questions

Questions that come up before B2B teams commit to an infrastructure provider. If your situation is more specific, send us the details and we will respond with a direct assessment.

How is Yhost different from a typical hosting provider?: We do not build the platform around mass resale logic on overloaded nodes. Our focus is on a clean open source stack, resource isolation, and a defined operational model for real business workloads. At the managed level, we operate applications — Odoo, Keycloak, Nextcloud — not just the server underneath them.
You are a small team. What happens if something breaks at 2am?: Monitoring runs continuously and alerting is configured on the infrastructure and application layer — not on a human checking a dashboard. For managed tiers, incident response is part of the service scope. Whether the response is immediate or within a defined window depends on the SLA tier. We will tell you clearly what the response commitment is before you sign up, not after an incident.
Where are your servers physically located?: Infrastructure runs on Hetzner and UpCloud in Germany. Data residency for all managed services is EU — Germany specifically, unless you request a different EU location. Yhost operates under Apefo Ltd, registered in the UK. We can provide a Data Processing Agreement that reflects actual data flows.
Can you handle our procurement process — DPA, security questionnaire, vendor review?: Yes. We can provide a DPA template, respond to vendor security questionnaires, and produce a written scope statement that defines responsibilities clearly. Tell us upfront what your procurement process requires and we will prepare it as part of the initial conversation rather than after a decision is made.
What does self-managed mean in your model?: Self-managed means the customer controls the application, code, CMS, plugins, and business logic. We manage the platform, hosting environment, network layer, and baseline service stability. That keeps costs rational where full managed scope is not required. The managed tiers exist for when you want us to own the operations layer entirely.
We are on Odoo.sh or a self-managed VPS. How does migration work?: Migration is a risk management task, not a file copy. We review your current setup first — database size, modules, custom code, integrations, user count — then produce a migration plan with a staging validation step before anything touches production. Production goes live on Yhost only after staging has confirmed everything works. We handle the technical execution; you confirm the validation.
We have budget constraints. Can we start small and move up?: Yes, and that is explicitly how the platform is structured. A company website on Smart Web Hosting at €0.59/mo and a managed Odoo instance at €399/mo run on the same underlying infrastructure logic — same stack decisions, same engineering approach, different operational scope. You do not switch providers as requirements grow. The path from shared hosting to managed VPS to operated application is a deliberate part of the model.
Do you offer support in German?: Yes. Support is available in English and German. For clients operating in DACH, we can handle technical and operational communication in German throughout the engagement — including documentation, scope statements, and incident reports.

About Yhost