Built by TurningMatter.

Why Idle9 exists

AI assistants got very good at writing software and never got anywhere to put it. Every session starts from nothing: reinstall the dependencies, re-clone the repo, re-explain the project, rebuild the state that existed an hour ago. The model is capable; the machine underneath it is amnesiac.

The industry's answer has been the sandbox — somewhere disposable to run untrusted code, wiped when the session ends. That solves a safety problem and creates a memory one. We think the more useful thing to hand an assistant is the same thing you would hand a new colleague: a computer of their own, which they set up how they like and come back to on Monday.

So Idle9 is a computer. Real Ubuntu, root, a disk that survives. Everything your AI installs stays installed, every note it leaves itself is still there, and the work compounds across sessions instead of resetting between them.

How we operate it

Idle9 runs on dedicated hardware we provision and manage ourselves, not on rented functions with a timeout. Machines sit on fast local disk while they run and on bulk storage while they sleep, which is what makes it reasonable to keep a project around for months rather than minutes.

Every computer is sandboxed and isolated from every other. Being a real machine and being safely walled off are not in tension — the isolation is what makes it safe to hand over root — and we take it seriously because your machine holds your source code and your credentials.

Contact

Questions, problems or feedback: [email protected].