# Keep it moving without a developer.

> Managed hosting for sites with no developer. Brief a change in plain words, a CodeHerder agent opens a pull request, and you approve it.

Source: https://customhosted.com/for/no-dev-team/

№ 01 Who it's for

The loop stands in for a hire: brief a change in plain language, an agent opens a pull request against the real site, and it's reviewed and shipped by the same pipeline that already runs it.

№ 02 Sound familiar?

## Sound familiar?

A business or marketing owner of a site whose original developer has moved on.

- The person who built your site left, and nobody since has been able to touch the code.
- A typo or an out-of-date price has been wrong for months because nobody knows how to fix it.
- Every quote for a two-line change comes back priced like a new build.
- The site is still live and still working — it's just frozen exactly where the last developer left it.

Not you? Still actively maintaining code yourself, or managing sites on behalf of other people? [Agencies](https://customhosted.com/for/agencies) · [Founders](https://customhosted.com/for/founders) 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 |
| --- | --- | --- |
| The stuck typo | Sits wrong for months — nobody has the access or the skill to touch it. | Brief it in a sentence. The fix comes back as a pull request. See [Content](https://customhosted.com/content). |
| Getting a quote | A developer prices a two-line change like a new project. | A flat monthly add-on covers whatever comes up, priced once. |
| Who has the keys | One person who left had all the passwords. | We hold them — everything defined as code, documented, and portable. |
| A new page or section | Waits indefinitely for someone to have spare time. | Briefed, opened as a pull request, reviewed, and shipped. See [Content](https://customhosted.com/content). |
| A security patch | Nobody's watching for it. | Patched on a schedule, before it becomes a headline. |

№ 04 The loop

## The loop, in your shape

For a site with no developer left, the move is first: bring what's already live in, then let the loop replace the hire that never happened.

1. 01 — Build — CustomLabs — Nothing to rebuild — we move what's already live with a rehearsed, little-to-no-downtime cutover, keeping the framework and content exactly as they are.
2. 02 — Iterate — CodeHerder — This is the loop instead of a hire: brief a change in plain language, an agent opens a pull request against the real repo, and it ships once it's reviewed.
3. 03 — Run — CustomHosted — TLS, DNS, backups, monitoring, and patching all run without anyone on staff having to remember to do them.

An example brief

- **The brief**: Update the seasonal opening hours, and add a new service to the homepage.
- **What the pull request holds**: A pull request against the site's real repository, opened by the agent from the brief above. No developer hired.
- **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 Instead of a hire

## The loop instead of a developer

Hiring a developer to keep one site moving is almost always the wrong amount of developer.

When the person who built a site moves on, the business behind it is left with a decision nobody wants to make: hire a developer for a handful of hours' work a month, save every small change up for an expensive one-off contractor, or just stop touching the site. All three are common. None of them are good, and the third one — doing nothing — is the quiet default most sites end up with.

The loop is built for exactly this gap. It doesn't require a technical hire, a contractor relationship, or any code knowledge at all — briefing a change is describing it in plain language, the same way you'd explain it to a person. An agent opens a [pull request](https://customhosted.com/glossary#pull-request) against the site's real repository, the usual checks run, and either you or we review it before it merges and goes live. Nothing about the site's framework, content, or history has to change first; see [keep shipping without a dev team](https://customhosted.com/guides/keep-shipping-without-a-dev-team) for how a single change moves end to end.

It's not a substitute for a real rebuild — a new design or a genuinely new feature set still needs a proper build, and that's a job for [CustomLabs](https://customlabs.io). What it removes is the much more common problem: the small, constant trickle of changes that used to need a developer on staff, and now doesn't. See [In flight](https://customhosted.com/in-flight) for how much of that trickle actually fits in a month.

№ 06 A starting configuration

## A starting configuration

A site moved in and kept moving: hosting plus the iteration add-on, nothing else required.

- **Base plan**: Static Pro
- **Iteration — CodeHerder loop**: +$25/mo
- **Starting point**: It's already running somewhere else
- **What it is**: A site / marketing pages — mostly content
- **Needs a database**: No
- **Recommended fit**: Move your existing app in
- **Estimated total**: $40/mo

[Get this quoted →](https://customhosted.com/contact?plan=ST-PRO&addons=AD-CH&stage=already-live&type=content&data=no-db&fit=migrate&src=no-dev-team) [Size it differently on the estimator →](https://customhosted.com/#estimate)

№ 07 FAQ

## No dev team questions

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

1. 01 We don't have the original files or logins anymore — can you still help? Often, yes — describe what you're running and where, and we'll work out what can be recovered or rebuilt before quoting anything.
2. 02 Who actually approves each change? You can review pull requests yourself in plain language, or we can act as the reviewer if you'd rather not.
3. 03 What if the change is bigger than a brief? A real redesign or a new feature set still needs a proper build — that's a job for CustomLabs, not a pull request.
4. 04 Do we need any technical knowledge to use this? No. A brief is plain language — no code, no ticket templates, no account to learn.
5. 05 Is this actually cheaper than hiring someone? For the steady trickle of small changes most sites need, yes — see the real cost of a website for the three-year math.

№ 08 See also

## Keep exploring

- [Migrations How the move in works — a rehearsed cutover with little-to-no downtime.](https://customhosted.com/migrate)
- [Keep shipping without a dev team The Build → Iterate → Run loop, written as a how-to.](https://customhosted.com/guides/keep-shipping-without-a-dev-team)
- [Pricing The full rate card — flat, predictable, and posted in the open.](https://customhosted.com/pricing)

## Ready to start?

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

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