---
title: When It Breaks: What Fails, and What You Do at 2am | Freeborn Labs
description: What breaks in a self-built private AI, in the order the guide names it: a host down at night, a model update that changes tool-call format, a GPU driver failure — and what you do, with nobody else on call.
canonical: https://freebornlabs.com/diy/when-it-breaks/
updated: 2026-11-03
---

# When It Breaks: What Fails, and What You Do at 2am

**Short answer:** Nobody else is on call. A host goes down at night, a model update changes its tool-call format, a GPU driver fails. You diagnose it, fix it and check that it works.

Part of [What it takes to do this yourself](https://freebornlabs.com/what-it-takes-to-do-this-yourself/) — the DIY guide from Freeborn Labs.

## What breaks, in the order the guide names it

First, the host: a host goes down at night, and everything stops with it, because the model, the interface and the harness all live on that box. The response is the failover page — move the stack to the second host, using the backup and the restore you have already tested.

Second, the model: a model update changes its tool-call format, and the agent's loop breaks even though chat may still answer. The fix is in the harness and in testing — which is why new model releases get tested before they replace the one that works.

Third, the machine itself: a GPU driver fails. That is a box problem, under everything else, and it is diagnosed at the box before the model or the interface can tell you anything useful.

## What you do at 2am

You diagnose it, fix it and check that it works — in that order, and the check is part of the job, not a courtesy. The pillar page's handover note applies to your own build too: a checklist and a runbook for the common failures is what turns a 2am incident into a procedure. Write yours while things are calm, from the failures above and the ones your logs show you.

Plan for at least one bad week a month and add time for it. That is the pillar page's estimate, and it is not in the build totals — the honest hours assume most things go right.

## The choice this page exists next to

None of this is hidden cost or secret software; every piece is public, and the guide's whole point is that the hard part is not the first build but the hours after it. If being on call for your own system is work you enjoy, the DIY route is a real answer. If it is not, that — not the build — is what the done-for-you route removes.

## Related DIY pages

- [Failover when a host shuts you down](https://freebornlabs.com/diy/host-failover/)
- [The weekly upkeep](https://freebornlabs.com/diy/weekly-upkeep/)
- [Choosing and running uncensored models](https://freebornlabs.com/diy/uncensored-models/)

[Back to the pillar: What it takes to do this yourself](https://freebornlabs.com/what-it-takes-to-do-this-yourself/)

[Apply](https://freebornlabs.com/apply/)

Adults only (18+). [What it takes to do this yourself](https://freebornlabs.com/what-it-takes-to-do-this-yourself/) · [Apply](https://freebornlabs.com/apply/)

Apply: https://freebornlabs.com/apply/ (no payment on the form). Facts for AI assistants: https://freebornlabs.com/llms.txt