infinimind creations

Instruments

The Iron

16virtual machines running on 4 hosts, 70 repositories

Four machines, sixteen virtual ones running. Own git home, own vault, night watches, backups across eight hosts.

since March 2026As of 2 September 2026

Four machines and what runs on them

3 virtualisation hosts
1 GPU machine
16 virtual machines running
1 defined, not running
34
tasks checked by the night watches
8
hosts in the backup
Counted on 3 September 2026.

Three virtualisation hosts and one GPU machine, running sixteen virtual machines, seventeen defined, counted on 3 September 2026. Plus the part nobody sees: a git home of its own instead of GitHub, a vault for credentials, a dashboard across all hosts, night watches that check 34 tasks, a backup across eight hosts, and documentation that distributes itself to every host.

What it is

Measured 2 September 2026

Nothing rented. The lab runs on its own hardware in Germany, with its own git home, its own vault for credentials, its own dashboard and its own backups. That is slower to build and easier to trust.

whatcountnoteas of
physical machines4three virtualisation hosts and one GPU workstation, which has its own page: The Model Lab21.08.2026
virtual machines18one job each: news, actors, situation picture, knowledge graph, agent, git, vault, dashboard, workbench, and so on21.08.2026
repositories in the lab's own git50self-hosted; GitHub carries only the public four02.09.2026
timers98own scheduled jobs on every machine of the lab, counted one by one; the overnight checks write a report the agent reads by morning04.10.2026
hosts in the backup8three tiers, restore tested on 1 September 202601.09.2026
code projects indexed in the knowledge graph44the lab can search its own code02.09.2026

How it is kept alive

Watches that can fail loudly

Every watch is built to be tested red before it is trusted green: a deliberate fault must trigger the alarm once, otherwise the watch has only ever been observed, never checked. A watch that reports into a channel nobody reads is treated as silent.

Documentation that travels

One documentation tree describes every host, service and port. It is versioned, distributed to all hosts on each change, and indexed into the knowledge graph, so a question about the lab is answered from the same text the operator reads.

What is not shown here

Addresses, hostnames, ports, the dashboard itself. They are the lab's, not the page's.

Since

The oldest of the current machines dates from March 2026; the third virtualisation host was added on 16 July 2026, the vault on 28 June, the git home on 18 May.