Verified live architecture
Biznomad Infrastructure
+ SaaS Build Team
Mac control plane → Orca frontier-model team → GitHub → Biznomad VPS production plane
Snapshot: 2026-08-23
VPS: 187.77.10.20 · Ubuntu
VPS: 187.77.10.20 · Ubuntu
8 / 31 GB
VPS CPU cores / RAM
85
running systemd services
26
running Docker containers
37 / 6
Nginx sites / Hermes gateways
01 · Infrastructure topology
human/front endexecution/servicesmodels/datacloud/opssecurity boundary
02 · SaaS factory: Plan → Build → Ship
Operating rules
Plan once, validate early
No build begins without a written problem, target user, success metric, and acceptance tests.
Parallelize safely
One task per worktree. Explicit dependencies. Two-stage review. No shared-file races.
Ship isolated
Every new SaaS gets a new directory, service, port, Nginx site, database namespace, and rollback path. Never overwrite a live site.
Verified gaps / risks
- DNS gap: saves.biznomad.io does not currently resolve. Public fallback is the nip.io hostname.
- Fleet density: 85 services and 37 Nginx sites need a service registry and port allocator.
- Config debt: Nginx validates but reports duplicate/conflicting legacy site definitions.
- Data freshness: the public knowledge graph currently contains 1,010 cached saves; the Mac ingestion source and VPS dashboard cache still need a unified handoff.
- Kimi: Orca usage telemetry says the local Kimi session is expired.