# Ship the work. Skip the ops desk.

> Managed hosting for design and dev studios. One flat rate per site, staging for each client, and CodeHerder to absorb small change requests.

Source: https://customhosted.com/for/agencies/

№ 01 Who it's for

Host every client site on one flat rate you can pass through or resell, hand out zero consoles for a client to break, and let the iteration add-on absorb the steady stream of small change requests instead of your evenings.

№ 02 Sound familiar?

## Sound familiar?

Design and dev studios and freelancers hosting client sites.

- A client's "quick fix" lands in your inbox at 9pm, and it's the fifth one this week.
- You've become the accidental ops desk for every site you've ever launched — DNS, TLS, backups, all on you, none of it billable.
- Explaining a surprise egress charge on a client's invoice isn't billable either.
- A client asks for something small enough that quoting it properly would cost more than doing it.

Not you? Running one site for yourself rather than a roster of clients? [Founders](https://customhosted.com/for/founders) · [No dev team](https://customhosted.com/for/no-dev-team) or try the [selector](https://customhosted.com/selector).

№ 03 The difference

## The week this replaces

Same situation, dimension by dimension — what it looks like now, and what changes.

| Dimension | Now | With CustomHosted |
| --- | --- | --- |
| A new client site | Another host account to provision, another set of credentials to track down later. | One flat rate, on the same account as every other client, provisioned as code. |
| Staging a change | Push to production and hope, or spin up a one-off preview by hand. | A dedicated staging environment per client, already wired in. |
| The client login | Hand over a hosting console you're now on the hook to support. | No console for the client — you stay the only point of contact, unless you choose otherwise. |
| The Tuesday-afternoon tweak | Squeeze it between billable work, or quote a special one-off for something tiny. | Roll it into the flat iteration add-on — brief it, an agent ships it, no special invoice. |
| Losing a client | Untangle their site out of your shared hosting before they can leave cleanly. | A free, documented handover — never a held-hostage migration. |

№ 04 The loop

## The loop, in your shape

The loop slots in wherever a studio already sits between a client and their site — bring your own build, or have CustomLabs design one, then let the other two roles carry the ongoing relationship.

1. 01 — Build — CustomLabs — Bring a client site you already built, or have CustomLabs design and build the first version alongside you.
2. 02 — Iterate — CodeHerder — The iteration add-on is the care plan you don't have to staff — every small client request gets briefed, opened as a pull request, reviewed, and shipped, no evening lost to a favour.
3. 03 — Run — CustomHosted — One flat rate per client site, provisioned the same way every time, with per-client staging and no console for a client to break.

An example brief

- **The brief**: A client asks to swap the homepage hero for a seasonal campaign and update three prices before the weekend.
- **What the pull request holds**: A pull request against the client's real repo, opened by an agent from the plain-language brief above.
- **What happens next**: [A human reviews and merges](https://customhosted.com/review). [It ships through the same pipeline](https://customhosted.com/deploys).
- **A real one**: [The site is blinding at night](https://customhosted.com/case-files#cf-01) (+751 −258 · 19 files · merged 2026-07-31).

№ 05 The care plan

## A care plan you don't have to staff

The part that actually protects a studio's margin isn't the hosting line — it's what happens to the small requests that never justify a proper invoice.

Every studio ends up running an unofficial care plan for the sites it launches, whether it means to or not — a client doesn't stop needing things the day the invoice is paid. The usual options are both bad: eat the small requests for free and watch your margin leak out one "quick fix" at a time, or quote each one properly and watch the client notice how much a two-line change costs when it's billed on its own.

The iteration add-on turns that unofficial care plan into a real, sellable line item. Fold it into your own hosting quote at whatever markup makes sense, and every small request — a copy edit, a new section, a config tweak — gets briefed in plain language, opened as a pull request against the client's actual repo, reviewed, and shipped. You keep the client relationship and the margin; the pull request queue is what changes. See [In flight](https://customhosted.com/in-flight) for how many of those requests actually fit in a month, and what sets the order they ship in.

It also means the client never gets handed a console. They see the site change; they don't see a dashboard with their name on it that they can misconfigure, or that makes it easy to walk to a different host. You stay the one point of contact, right up until — and even after — they don't.

№ 06 A starting configuration

## A starting configuration

A studio's first client site: staging comes with Static Pro, and the iteration add-on is on from day one.

- **Base plan**: Static Pro
- **Iteration — CodeHerder loop**: +$25/mo
- **Estimated total**: $40/mo

[Get this quoted →](https://customhosted.com/contact?plan=ST-PRO&addons=AD-CH&src=agencies) [Size it differently on the estimator →](https://customhosted.com/#estimate)

№ 07 FAQ

## Agencies questions

The questions this situation raises on its own. General hosting questions live on the homepage.

1. 01 Can I resell this to my clients? Yes — pass the flat rate through at whatever margin you choose, or fold it into your own retainer. We never contact a client directly unless you want us to.
2. 02 Do clients get their own login? Not unless you want them to. By default you're the only account holder — a client gets the site, not a console to break.
3. 03 What happens if a client leaves? A documented handover, free, any time. Nothing is held hostage in a proprietary dashboard.
4. 04 Does the iteration add-on cover design work? It covers implementation — copy edits, config changes, small features shipped as a pull request. Design decisions still come from you or your client.
5. 05 Can several client sites sit on one account? Yes — the Static Pro tier is built for multiple sites and environments under one account, with per-client staging.

№ 08 See also

## Keep exploring

- [Environments What "per-client staging" actually is — the address, who can reach it, and how a client sees a change before it ships.](https://customhosted.com/environments)
- [The real cost of a website Where the agency-retainer model breaks down against a flat iteration add-on.](https://customhosted.com/guides/the-real-cost-of-a-website)
- [Pricing The full rate card — flat, predictable, and posted in the open.](https://customhosted.com/pricing)
- [Access The "no console for the client" line above, as a matrix — exactly who can reach a client's stack, and who cannot.](https://customhosted.com/access)
- [Logins The other login — the one a client's own app presents to its users, not the hosting console above.](https://customhosted.com/logins)

## Ready to start?

Tell us what you're running — one fixed monthly rate, within a business day.

[Get a quote →](https://customhosted.com/contact)