This company claims to run itself. Claims are cheap, so this page shows the machinery instead: what the pipelines actually shipped, exactly where a human touches the loop, and what changed after each incident. Every on-server count is computed live, on each request, from the same files the pipelines write when they publish. One number on this page comes from outside this server — it says so, with a date. The euro ledger is private; everything else here is checkable.
Every product this company ships follows the same five-step loop — conceive, generate, QA-gate, publish, recover — run by one self-hosted control plane on our own hardware. It triggers each pipeline on schedule, gates its releases, retries its failures, and escalates only what a person must decide. Every model call is traced and quality-scored.
Every number above is checkable at the source:
→ The models on CGTrader → The reels on Instagram → The blog → The digest archive
The claim is not “no humans anywhere” — that would be false, and you could falsify it in an afternoon. The claim is: humans only at the approval gate. Here is the exact split, workflow by workflow.
| Workflow | Runs itself | Human touchpoint |
|---|---|---|
| Instagram reels | Concept, prompt, video + synced audio, QA | One approval tap per reel |
| 3D models → marketplace | Concept, mesh, QA render, listing copy, publish | None in the daily loop |
| Blog posts | Topic pick, writing, hero image, publish | None |
| Daily digest + PDF | Curation, writing, build, send, web publish | None |
| Newsletter infrastructure | Sending, unsubscribes, abuse control | None |
| Incident response | Retries, watchdog alerts, some auto-restarts | A human reads alerts, fixes root causes |
| This page’s numbers | On-server counts computed per request | Off-server counts verified by hand, dated |
The approval tap is accept-or-reject only — no edits. It exists because the incidents below were caught by a person rather than a metric: one tap per reel is the cheapest available insurance against a failure mode nobody has named yet.
Real incidents from our own logs, each with the change it produced. They are here because the fix is the part worth publishing: a system is only as good as what it does the second time.
On-server counts are file counts: the 3D tally comes from the gallery manifest the publishing pipeline writes, blog and digest counts from the article files on this server — computed on every request, never cached, never rounded up. The reel count lives on Instagram’s servers, not ours, so it is a snapshot verified against the platform’s own API and stamped with its date; a stale snapshot keeps its date rather than being estimated forward. Nothing on this page comes from an analytics service.
→ What our inference speed actually feels like → The Notebook: what running this is actually like → Want a machine like this for your business?
The AI news that matters — in your inbox by 07:30 CET. Free, no spam.