Netlify for agencies: hosting multiple client sites and billing it sensibly

This page may contain affiliate links from which Blur Studio earns commissions.

Netlify is a hosting platform for deploying websites and web apps from code, and a lot of small agencies and freelance developers use it to host multiple client sites under one account. The platform itself handles this reasonably well, but the way you structure your team, your billing, and your eventual handoffs matters a lot more than which specific plan you buy. For the general picture first, read the Netlify review for small business and marketing sites.

Team plans and what they actually include

Netlify's current pricing (confirmed live on netlify.com/pricing as of October 2026) runs on a credit-based system rather than the old per-seat tiers many agencies may remember:

• Free, $0/month: 300 credits, individual-oriented, deploy from Git, AI tools or API, unlimited deploy previews, custom domains with SSL.
• Personal, $9/month: 1,000 credits, adds smart secret detection, 1-day observability and priority email support, still aimed at a single person rather than a team.
• Pro, $20/month: 3,000 credits, explicitly built for team use with unlimited members, private organization repositories, shared environment variables across the team, 3 or more concurrent builds, and 30-day analytics.
• Enterprise, custom pricing: unlimited credits, a 99.99% uptime SLA, an enterprise network tier, SSO and SCIM for managing logins centrally, log drains, and 24/7 dedicated support, aimed at agencies running many client sites at real scale.

Credit usage itself is metered: production deploys cost 15 credits each (roughly $0.10), compute runs 10 credits per GB-hour (roughly $0.07), bandwidth is 20 credits per GB (roughly $0.13), and web requests cost 2 credits per 10,000 requests (roughly $0.01). That pool of credits is shared across every site on the team plan, which is the key thing to understand for billing clients accurately: a busy e-commerce client site and a quiet single-page brochure site draw very differently from the same shared pool. The full breakdown is in Netlify pricing: free plan limits, credits and paid plans.

Client handoff: the part most guides skip

The technical side of hosting a client's site is the easy part. The part that causes actual problems later is ownership and access once the relationship ends, whether that's a happy handoff or a client leaving on bad terms.

• Decide upfront whose Netlify account owns the site. If the site lives under your agency's team account, the client doesn't own it directly, and moving it later means a formal site transfer, not just a password change. If it lives under the client's own account with you added as a team member, handoff is simpler but you lose some of the convenience of managing everything from one dashboard.
• Document the domain's ownership separately from the hosting. A domain registered under your agency's account, rather than the client's, is one of the most common sources of a messy, slow handoff later. Where possible, have the client own their own domain from day one, even if you manage the DNS settings for them.
• Keep environment variables and integration credentials recoverable. If a client leaves and needs their site's environment variables (API keys, third-party service credentials), make sure those are documented somewhere accessible to them, not only inside your team's Netlify dashboard.
• Use Netlify's own site-transfer process rather than recreating the site from scratch under a new account, which preserves deploy history, custom domain configuration and environment variables rather than starting over.

Client approval and staging workflows

Beyond hosting the live site, Netlify's deploy preview feature is genuinely useful for agency work specifically: every change pushed to a branch gets its own live preview link automatically, before it reaches the client's actual domain. That means a client can look at a redesign or a content update, leave feedback, and approve it, all without the risk of a half-finished change being visible on their real site. For an agency managing several rounds of revisions per client, this removes a step that used to mean spinning up a separate staging server or awkwardly emailing screenshots back and forth. It's also worth building this into how you price a project: a client who can see and approve changes themselves in a preview link tends to generate fewer "wait, I didn't realize that was live" conversations than one who only sees the finished result.

For agencies running many client sites with a consistent build setup (the same framework, similar structure), Netlify's shared environment variables at the team level also save real time: a shared API key or service credential used across several client sites can be set once at the team level rather than re-entered per site, provided that's appropriate for your specific client contracts and data separation requirements.

A real cost-per-site example

Say your agency hosts eight client sites on the Pro plan ($20/month, 3,000 credits): five quiet brochure sites with low traffic and infrequent deploys, two mid-traffic business sites with a contact form and occasional content updates, and one busier e-commerce site with regular deploys and meaningful bandwidth. The five quiet sites might together use a few hundred credits a month in builds and light bandwidth, the two mid-traffic sites a bit more each, and the e-commerce site alone could draw a disproportionate share of the pool through bandwidth and compute. If your combined usage threatens to exceed the plan's 3,000 credits, Netlify's billing adds overage charges at the per-credit rates above rather than cutting your sites off, so the real monthly cost is the $20 base plus whatever overage your heaviest site drives. Check what the Netlify free tier includes before deciding which sites need a paid plan.

The practical takeaway: price your client retainers around actual usage patterns, not a flat per-site number, since one busy site can cost you more in shared credits than five quiet ones combined.

Roles and access within the team

Netlify's team plans let you add every member of your agency with the same account, but that doesn't mean everyone needs the same level of access to every client's site. Worth deciding deliberately rather than defaulting to "everyone can touch everything": who can change environment variables and domain settings versus who's only making content or design changes, and whether a junior team member or a contractor working on one client project needs visibility into every other client's site in your portfolio at all. This matters more as your agency grows past a couple of people, since a mistake made by someone with broader access than their actual project needs is a genuinely avoidable kind of incident. To give a client limited access, see how to give a freelancer or client limited access to your website host.

Billing clients sensibly

Most small agencies either absorb hosting into a flat monthly retainer or pass Netlify's actual cost through with a markup. Given the credit system's usage-based nature, a flat per-site hosting fee only works cleanly if your client sites have genuinely similar traffic and deploy frequency. If one client's site is far busier than the rest, either price that one differently, or set up Netlify's team roles and site-level monitoring so you can see which site is actually driving your bill before you set next year's retainer.

How I'd approach this

For an agency hosting a handful of client sites, Netlify's Pro plan at $20 a month with unlimited team members is genuinely good value, and the credit system is more transparent than a lot of alternatives once you understand what drives usage. My honest advice beyond the pricing: decide account ownership and domain registration policy before you onboard your first client, not after your first messy handoff teaches you the hard way. If you're building client sites as part of a broader custom software practice rather than running a dedicated hosting business, the hosting decision is usually the least important part of the relationship, worth getting right once and then not thinking about again.