Quick answer: There are two clean ways to run client infrastructure on Cloud2Y: keep all services in your agency account (full control, one invoice, you re-bill clients), or have each client register their own account that you administer technically (client owns billing, survives your offboarding). Choose per client — both models can coexist.
Overview
Ownership decides what happens in edge cases: who pays an overdue invoice, who can open tickets, who keeps the server if you and the client part ways. Getting this explicit up front — in your client contracts and in how accounts are structured — prevents almost every hosting dispute agencies run into.
Before you start
- A policy decision per client: agency-owned service (you re-bill) vs client-owned account (you administer).
- Separate credentials discipline: per-client SSH keys and panel users even on agency-owned servers.
- A written agreement covering data ownership and handover.
Step-by-step guide
- Agency-owned model: order services in your account, name them per client, keep isolation at the server or panel-user level, and re-bill via your own invoicing.
- Client-owned model: the client registers at cloud2y.com and orders (or you assist); you keep only technical access (SSH keys, panel user) — not their Client Area password.
- Either way, document per client: services, IPs, hostnames, backup locations and who owns the domain.
- For handover, transfer what the model dictates: data and configs (agency-owned) or just your access removal (client-owned).
Common issues
- Sharing one Client Area login with clients: never — it exposes every other client's services and billing.
- Client stops paying on an agency-owned server: the invoice is still yours; suspend at your own billing layer first.
- Handover without documentation turns into archaeology — keep the per-client record current.
When to contact support
Ask via ticket about moving a service between accounts, structuring a large fleet, or access questions during a client handover — such changes are verified for security.
Frequently asked questions
Should servers be in my account or the client's?
Agency-owned services give you control and one invoice you re-bill; client-owned accounts keep billing and ownership with the client while you hold technical access. Decide per client and document it.
Can I share my Client Area login with clients?
No — one login exposes every client's services and billing data. Use per-client SSH keys and panel users for technical access, and keep the Client Area credentials strictly yours.
Can a service be moved to another account later?
Ask via support ticket: ownership and access changes are verified for security, and the team will guide the transfer between your agency account and a client's own account.
Related articles
- How agencies can host multiple client sites
- White-label infrastructure options
- How to request priority support
Want to discuss a partnership? Contact Cloud2Y pre-sales →
