Here is the evidence. I’m better than you.
Not because I say so – because the system I build will show it. This is a public case study: maximum goals with zero budget. We construct reach with open‑source, data and discipline.
Mission: Dominance without budget
We don’t buy attention – we engineer it: a resilient, measurable marketing infrastructure that turns low‑cost hardware into a high‑availability OSINT system. Everything is documented in public – blog, LinkedIn, code and metrics.
Foundation architecture
Hardware: 3× Fujitsu‑Siemens S920 thin clients, Level One 10G switch, FritzBox (static IP 500/50).
Software: Proxmox VE (no subscription) hosting container services for OSINT/SEO/automation.
Network zones: red = Public/WAN (Router↔Switch), orange = DMZ (Switch→Nodes), blue = internal cluster P2P (30 cm), green = isolated WLAN (management).
Principle: redundancy over hope – if one node fails, the system stays online.
Why odd numbers? Quorum beats opinion
Clusters need decidability. We always run an odd number of nodes (3/5/7/…). A quorum prevents split‑brain; one node can act as a witness/arbiter. If a node fails, the remaining nodes decide who keeps computing – controlled load, no chaos.
Information security ≠ IT security
Firewalls are hygiene. Information security is governance: clear zones, purpose binding, auditability. This structure supports IT‑Baseline/ISMS compliance. We build an information management system – not just servers.
Cost base (honest up‑front – then zero budget)
Thin clients from backup stock: ≈ €20 per S920 → ≈ €60.
Switch & uplink: existing hardware/contract. Proxmox VE: €0.
Windows Server licenses avoided: ≈ €100+ per instance.
From here on: no additional budget. Open‑source. Automation. Proof.
Stack design (Proxmox → containers)
-
Proxmox cluster with quorum; bridges: vmbr0=public, vmbr1=dmz, bond0=cluster.
-
Reverse proxy + TLS, observability (logs/metrics/traces), GitOps deployment.
-
OSINT/SEO tools: crawlers, index monitoring, keyword pipelines, backlink intelligence.
-
Backups & snapshots; prefer stateless services, persist data per zone.
Roadmap (8‑week outline)
W1–2: infrastructure & zones. W3–4: content engine (cluster SEO, pillar pages).
W5–6: automation, dashboards, experiment pipelines. W7–8: scaling & outreach.
Weekly public updates with metrics.
Key metrics (core KPIs)
Indexing velocity, crawl coverage, top‑10 rankings per cluster, CTR, referring domains, conversion events. Goal: repeatable dominance by design.
Advisory – quiet but clear
I design architectures for teams that refuse to burn budgets. Tailored, expandable, license‑free. Get in touch if you want infrastructure that works.