Website hosting for agencies: plans, limits and client handoff

If you build websites for clients, hosting is part of the handoff: someone must operate each site, pay renewals and respond when something breaks. A multi-site plan can simplify hosting several websites. A reseller plan may add separate client accounts or white-label branding. They are different offers.

Count the sites and resources you need

List active sites, databases, mailboxes and storage before choosing a plan. Leave room for new projects, but do not buy capacity without a reasonable forecast. Hostbrid’s public Sites catalogue lists 3 websites on Starter, 10 on Pro and 30 on Agency. Agency includes 50 GB NVMe storage, 30 databases, 100 mailboxes, daily backups, a staging environment, SSH and priority support. Domain registration is billed separately.

Agency is listed at €14.99 per month; annual billing is shown at €11.99 per month, paid upfront. Check the current total, applicable taxes and terms on Hostbrid pricing and in checkout before ordering. The plan limits do not guarantee that thirty websites or every application will perform well under any workload.

For a batch migration, create an inventory for every domain: CMS and version, file size, database, email, DNS, forms, integrations and owner. Confirm that you have a recoverable backup, migrate one representative site first, then check pages, images, forms, access and email before repeating the process. Changing hosts does not automatically move the registrar or every service used by each client.

Tell a multi-site plan from reseller hosting

A multi-site plan gives you a site limit under one hosting plan. A reseller service may also offer separate client accounts, delegated access, white-label branding, client billing or isolation between clients. Before reselling hosting, check exactly what the provider supports and who handles support, security, backups and cancellations.

Hostbrid publishes the site count, resources and Sites features, but does not describe Agency as a reseller control panel or promise independent client accounts or white-label branding. If those functions are essential, do not assume they are included; get written confirmation before building your service around them. Do not share the main account password with clients.

When pricing your service, separate the hosting plan, domains, extra mailboxes, migrations and your maintenance hours. State what the recurring fee covers, who handles renewals and what response time you offer. Agency includes a staging environment in the catalogue, but do not sell it as an isolated preview for each client without checking its URL, data and permissions.

Assign responsibility for each client site

Record who owns the domain, controls DNS, renews hosting, receives alerts and takes over if a maintenance agreement ends. Keep credentials separate and use delegated permissions where the product supports them. A limit of thirty websites does not mean the sites are isolated from one another or that every client has a separate account.

If a client must be able to continue without your agency, prepare a verifiable handoff: files or repository, DNS inventory, named owners, publishing instructions and access checks. Use the website client handoff checklist to organize the transition; it is not an automatic Sites feature.

Match the product to the application

Sites is intended for websites and applications supported by its catalogue. For PHP or WordPress, check the available applications and migration requirements. For a static build published from Git, compare Projects and its limits. For containers, custom processes or operating-system control, assess a VPS and take responsibility for administering it. Do not choose Agency just because of its name if the deployment workflow or backend does not fit.

Compare Hostbrid Sites with your actual site inventory, the access features your workflow requires and each client’s agreed budget. Confirm details in the panel before promising a feature or delivery date.