What runs when we don't

• Tonight

  What's different

  Nobody who works here is awake right now.

  What keeps running

  The automated watch, and everything on its auto-handled tier below — restarts, retries, and a redeployed last-known-good build.

  What waits

  Anything past that tier waits for business hours, with priority handling once someone is back at a screen.

  Your route out

  None needed. This is the normal state of every night, not an outage in progress.

• A month

  What's different

  One person on the team is away for a stretch, not just off for the evening.

  What keeps running

  The same automated watch, the standing patch window, and the same loop for a briefed change — none of it is one person's job alone.

  What waits

  A judgment call that genuinely needed that one person waits for their return, or gets picked up by whoever is covering.

  Your route out

  Write in on the same quote channel as anything else and ask where things stand — the queue does not stop because a name is out.

• For good

  What's different

  CustomHosted stops operating, and the account ends at the close of the current billing cycle.

  What keeps running

  Nothing here — the service itself ends. Nothing about this page pretends otherwise.

  What waits

  Nothing waits. What matters at that point is what you already hold and what a handover can still hand you.

  Your route out

  The pack below, and the exit procedure already published on Portability. Portability

• Restarting a crashed process or a hung worker
• Retrying a failed background job once before flagging it to a human
• Redeploying the last known-good build when a deploy fails partway
• Renewing a TLS certificate ahead of its expiry
• Rerouting a request away from an origin that is failing its health check, where the edge network in front of it supports it
• Logging every one of the above, whether or not anyone gets woken

Restart, retry, or redeploy the last known-good version, done automatically No one, unless it recurs — it goes in the log, not a message to you Every one of those actions runs alongside 17 automated checks that gate every change on this platform, whether or not anyone is watching them run.

• A human reviews and merges

  Someone reads the diff before it goes anywhere near production — nothing here is auto-applied blind.

• Nothing merges itself

  There is no setting that lets an agent merge its own pull request. A person approves every change, including when you would prefer that it did not.

Of the 10 items in the handover pack, 4 sit in the repository already. That account stays in your name, and we only hold read access to it — our absence cannot put those out of reach. The other 6 live in infrastructure we hold, and need a person here to export them.

• The domain name itself

  Registered in your name, at whichever registrar you chose, renewed on whatever cycle you set up there. That relationship never moves to us.

• The account is yours

  Your code host account stays in your name and under your control, whether we work in it or set one up for you.

• We hold read access

  Enough to build and deploy what you already approved, and no more.

• We never hold the only copy

  Your code host holds the repository. We build from it; we do not become the one place it lives.

Termination

“Either side can end the service at any time, effective at the close of the current monthly billing cycle. There's no long-term lock-in and no early-termination fee.”

Data portability

“Your stack is defined as code, in a repository you hold — not clicked together in a console only we can see. If you leave, you take the repo and its configuration with you. Nothing is stored in a proprietary format, and we'll help with a reasonable export on request.”

Read the whole thing on Terms.

1. 1

   Say which way you're going

   Pick one of the two shapes below, through the quote form: take the pack yourself, or have it rebuilt into an account you own.

   You

2. 2

   The pack is assembled

   Every item in the manifest below is exported fresh, alongside the stack that keeps running while it happens.

   CustomHosted

3. 3

   Confirm where it lands

   Your own storage, or handed straight to whoever's building the new home — your call.

   You

4. 4

   Rebuild, if that's the shape you picked

   Only for the "rebuild into your account" shape: the same definitions, stood up inside infrastructure you own.

   CustomLabs

5. 5

   Confirm the new home is live

   Point DNS, or just confirm everything is where it should be.

   You

6. 6

   Old access is revoked

   On the schedule you set, once you've confirmed the new home is live — not before.

   CustomHosted

Around 30 minutes of your own time end to end — the same procedure Portability publishes in full.

• Take it and go

  You receive the full pack and stand it up wherever you like — another provider, or back in-house. Free, documented, no rebuild required from us.

• Rebuild in an account you own

  You want the running stack itself, not just the definitions for it. We rebuild it from those same definitions into an infrastructure account you control, and hand over the keys. Also free, also documented.

1. 1

   A routine scan flags a dependency

   The same kind of check that watches the infrastructure layers above, run against your application’s own dependency list.

   CustomHosted

2. 2

   It's triaged as application-level, not infrastructure

   A library your own code imports isn't ours to patch silently — it can change how the app behaves.

   CustomHosted

3. 3

   Briefed as a change

   Written up the same way any other change request is — this is what the Agentic iteration — CodeHerder add-on covers.

   CustomLabs

4. 4

   An agent opens the pull request

   The upgrade lands as a real pull request against the repository, with the test suite run against it.

   CodeHerder

5. 5

   A human reviews and merges

   Someone reads the diff before it goes anywhere near production — nothing here is auto-applied blind.

   CustomLabs

6. 6

   It ships through the same pipeline

   The same pipeline that deploys everything else on your stack ships this too — no separate process to babysit.

   CustomHosted

7. 7

   You're told it's done

   A note confirming what changed and that it merged, in the same shape as every other note on this site.

   CustomHosted

Nothing merges itself. There is no setting that lets an agent merge its own pull request. A person approves every change, including when you would prefer that it did not. The Agentic iteration — CodeHerder add-on is what covers a change briefed this way.

Automated checks gating every change

17

Changes shipped through this same loop

132

Calendar span those changes cover

2026-07-07 → 2026-10-03

No pace or authorship figure is published alongside those numbers — see Case files for why.

• TLS certificates
• DNS management
• Daily backups
• Monitoring & alerts
• Security patching
• A human who answers

• No named successor, no dated wind-down plan

  There is no named backup operator standing by, and no published date by which a wind-down completes. The termination clause above is the only binding commitment on this.

• No source-code escrow

  Nothing here is held by a third party for release if we fail. You already hold the repository yourself, which is the reason there is nothing to escrow.

• No standby provider agreement

  There is no arrangement with another host to take over your account if this one stops. A handover, not a handoff, is what the pack above is for.

• No staffed round-the-clock desk

  The automated watching runs continuously. The people behind an escalation work business hours, with priority on an outage and best effort outside them.

1. 01What happens if nobody here is awake and something breaks tonight?

   The automated watch keeps running regardless of the hour, and its auto-handled tier fixes a known, safe failure on its own — see "What keeps running with nobody awake" above. Anything past that tier waits for business hours, with priority once someone is back.

2. 02What if the one person who knows our stack is away?

   The loop does not depend on one person's memory. The watch, the standing patch window, and a briefed change through CodeHerder all run the same way regardless of who is out — see "Why it does not rest on one person" above.

3. 03What if CustomHosted goes out of business?

   Either side can end the service at any time, effective at the close of the current monthly billing cycle. There's no long-term lock-in and no early-termination fee. You already hold the repository and its full history today. That covers 4 of the handover pack's 10 items — see "What you already hold" above for which ones, and for the 6 that need a person here to export them.

4. 04Do you offer source-code escrow?

   Nothing here is held by a third party for release if we fail. You already hold the repository yourself, which is the reason there is nothing to escrow.

5. 05Is there a backup operator who takes over if you disappear?

   There is no arrangement with another host to take over your account if this one stops. A handover, not a handoff, is what the pack above is for.

6. 06Can an agent open a pull request with nobody watching?

   Yes — that is the point of the loop. Someone reads the diff before it goes anywhere near production — nothing here is auto-applied blind. There is no setting that lets an agent merge its own pull request. A person approves every change, including when you would prefer that it did not.

7. 07How big is your team, really?

   This page is the honest answer to that question, without a headcount number: what runs with nobody awake, what waits for a person, and what you already hold either way.