Managing Multiple Cloud Accounts Across Client Projects

Agencies and consultancies face a question in-house teams do not: whether to run every client inside one environment or to give each its own. The tidy answer is separate accounts per client, and the reasons are mostly about the end of the relationship rather than the start.

Why separation wins

• Billing is unambiguous. One account, one invoice, one client. No allocation arguments.
• Access is containable. A contractor added for one project cannot see another client’s data.
• Handover is possible. When the engagement ends you can transfer the account. Extracting one client from a shared environment is a migration project.
• Incidents are contained. A compromise or a runaway process affects one client.

The real overhead

Separation costs something. More accounts mean more credentials, more billing relationships, more places to check, and quotas that do not pool. A ten-client agency has ten sets of everything.

The overhead is manageable with conventions rather than tooling.

Conventions that keep it tractable

Name everything predictably

A consistent scheme for accounts, projects, servers and tags means anyone can find the right environment without asking. Inconsistent naming is the single largest source of wasted time across many accounts.

Use a standard baseline

Every new client account should start from the same checklist: credentials in the shared password manager, second factor on a team device, budget alerts configured, audit logging on, naming applied. Sameness makes the estate readable.

Keep a register

One table listing client, provider, account identifier, who holds credentials, billing state and renewal date. It takes minutes to maintain and answers most questions instantly.

Decide the exit at the start

Agree at kickoff whether the client will receive the account at the end. If they will, keep it clean from day one: no shared agency tooling baked in, no credentials that also unlock other clients. The record you will need is described in documenting a cloud account handover.

Choosing providers for this pattern

Providers with simple, uniform environments suit per-client separation particularly well, because the per-account overhead stays low. Droplet-based environments from DigitalOcean and server-count environments from Hetzner are straightforward to stamp out repeatedly and to hand over intact.