Independent comparison · no paid rankings
Home / Blog / Comparison / Agency or client: who should own the hosting account?

Agency or client: who should own the hosting account?

An account in the agency name simplifies daily work — until end of mission, a dispute or the client GDPR request for "their" access.

Hébergeurs.eu Editorial Team 3 min read Updated Jul 19, 2026

The site is delivered. The client asks for hosting access to onboard marketing. The agency replies that "everything is managed" — account in the agency name, agency card on file, root never shared. Six months later, commercial breakup: the client cannot pay the host directly or recover DNS without the agency.

This is not an edge case. It is the most common failure mode of poorly closed web projects.

Agency account: short-term efficiency

Pros. One panel for twenty clients, fast deploy, reseller margin, centralized tier-1 support.

Cons. Client technical lock-in, GDPR blur (who is processor?), conflict migration, billing continues on agency side after end of mission.

Client account: initial friction, long-term calm

Pros. Clear ownership, direct billing, agency change without access negotiation, aligned controller role.

Cons. Slower client onboarding, misconfiguration risk if client touches settings untrained, no hosting margin for agency.

CriterionAgency accountClient account
End of missionHigh riskSimple transition
GDPROften blurredAligned
Agency marginYesNo (unless reseller)
Deploy speedFastMedium

Hybrid model: the most robust

  1. Account created in client name at kick-off.
  2. Agency users with limited technical admin roles (not billing owner alone).
  3. Documentation: who has which access, revocation procedure.
  4. Handover clause: full transfer, no DNS retention.

The peak: holding the account is holding leverage

Decide and move forward without blind spots

  1. Create the client account before first deploy.
  2. Document access and revoke unnecessary agency accounts after handover.
  3. Sign a transition clause: export, DNS, billing, 15-day window.
  4. Train the client on basics (backups, users) or sell explicit managed services.

More on by use case and our directory.

Frequently asked questions

Why do agencies want their account?

Group billing, central access, margin. Convenient — risky at end of mission.

Should the client own the account?

Yes for data, GDPR or future agency change.

How to share without giving everything?

Client account + limited revocable agency roles.

What to contract at handover?

Ownership transfer, export, access revocation, client billing.


The site belongs to the client. The hosting account should too — or the next agency pays in downtime what you saved in "simplicity."

Compare European hosts

Filter by compliance, location and use case — then open the sheets to verify the real scope.

Browse the directory
Blog

Related reading

All articles →