Skip to content
lubemy

For agencies and studios of 2 to 15 people

Hosting for web agencies: hand over the servers, keep your clients

When the portfolio grows and tickets steal time from projects, you need a way to delegate management without giving up the relationship. We manage your sites' infrastructure with separate accounts and explicit scopes: you keep invoicing your clients, we invoice only you.

The typical web agency situation

An agency with 10–60 sites spread across several providers accumulates different panels, scattered renewals and unclear responsibilities. Every incident becomes a ticket to forward, translate and chase; technical time ends up in management instead of in the projects that generate margin.

Our role is to take over the system side of the portfolio: node, accounts, backups and monitoring. The first line towards your clients stays yours; when an infrastructure intervention is needed, you open it with us and receive a report of what was done.

White-label reselling: your client relationships stay yours, by contract

The fear of every agency that delegates is finding the provider inside its clients' house. We rule it out in writing and make it hard by design.

Contractual end-client protection

The contract states that we do not commercially contact your end clients: the relationship, the price to the client and the margin stay yours.

Separate accounts per client

Each site lives in a distinct account with declared quotas: a problem does not spread to the others, and a single client leaving remains a simple operation.

We invoice you, not your clients

We invoice the agency; the agency invoices its own clients at the price it decides. No direct financial relationship between us and your end clients.

White-label reports where technically available

Where the technical format allows it, reports can be presented under your brand, so you can document the service to your clients without exposing the provider.

Delegation and partner features

Delegated access for your team with distinct permissions: who does what is tracked, and you can revoke one access without touching the others.

A declared exit path

If one day you want to leave, the contract provides for data export and delivery of the documentation: portfolio portability is a commitment, not an obstacle.

Moving your client sites gradually, starting with a pilot

There is no need to move sixty sites on day one. The path is designed to reduce risk and give you verifiable evidence before widening.

  1. Pilot migration of one or two sites

    Together we choose representative but non-critical sites. We clone them to staging, verify against a shared checklist and run the cutover in an agreed window, with a rollback plan ready.

  2. Portfolio inventory

    While the first sites are running, we survey the rest: domains, DNS, mail, versions, dependencies and workloads. The inventory is delivered to you and remains yours.

  3. Transfer in batches

    Sites move in agreed groups, with a calendar and checks for each batch. High-load sites are assessed individually before being included.

  4. Operation with reviews

    In steady state: daily backup with 14-day retention and periodic restore tests (operational targets, not an SLA), an operations log and reviews at 30, 60 and 90 days.

Who does what: your agency and your host

We manage

  • Node, accounts and platform configuration
  • System updates and infrastructure hardening as an operating practice
  • Daily backup with 14-day retention (operational target)
  • Base monitoring and anomaly reporting
  • Documented infrastructure interventions, at your request

Stays with you

  • Commercial relationship and invoicing to your clients
  • First line of support towards end clients
  • Content, themes, plugins and application-level site maintenance
  • Deciding which sites to migrate and in what order
  • Advance notice of campaigns or expected load

Where to start

The recommended starting point is Hosting Multi 10: ten separate accounts to begin with part of the portfolio. The 25- and 50-account sizes are available on request, with a dedicated offer.

Hosting Multi 10

Recommended

Ten separate accounts for your portfolio

49 €/month · VAT excluded

Separate accounts on a shared node

  • Included: 10 separate accounts
  • Included: 30 GB total storage
  • Included: Partner features and delegation
  • Included: Contractual end-client protection
  • Included: Daily backup with 14-day retention
  • Not included: Creating further resellers autonomously (separate feature)
  • Not included: Maintenance of individual installations
  • Not included: High-load sites (require assessment)

Launch prices in euro, VAT excluded. The renewal price is stated before activation, and the signed offer lists inclusions, limits and terms. Renewal price communicated before activation; no lifetime price locks.

Frequently asked questions from web agencies

How is the service activated?

Through assisted activation: you send us a request, receive a written offer with price, renewal, inclusions and limits, and the service starts once you sign. No online payment before you have signed.

What happens if one of my clients contacts you directly?

We redirect them to you. The contract excludes commercial contact with your end clients: we are your provider, not a competitor with access to your portfolio.

Can I manage sites with very different workloads?

Yes, with a declared limit: high-load sites require an assessment before being included, because on a shared node quotas protect every account. When a site consistently outgrows shared hosting, we propose moving to a dedicated VM only on the basis of measurements.

Is maintenance of the individual sites included?

No: the Multi plan covers the infrastructure, not the application-level maintenance of individual installations, which stays with you or is quoted separately. It is a declared exclusion, not a surprise on the invoice.

What if the experience does not work out?

That is what the pilot migration is for: it starts small, with a rollback plan. If you decide to leave even later, the contract provides for data export and delivery of your environment's documentation.

Bring one site, not the portfolio

A pilot migration of one or two sites is the most concrete way to verify how we work, before deciding on the rest.