playbook/

playbook — the 7 workload profiles xmrcloud builds for. each one maps to a specific threat model and a specific catalog slice.

synopsis

xmrcloud-cli playbook list
xmrcloud-cli playbook describe --workload=<slug>

description

The catalog is shaped around seven workloads, picked for the threat models the operator actually sees and answers for: tor relays and bridges (RFC 7686 / Tor Project guidance), crypto nodes and validators, personal-use VPNs (RFC 4301 + WireGuard / OpenVPN), ethical scraping and OSINT pipelines, open-weight LLM inference, mid-sized community / matrix / fediverse infrastructure, and source-protection hosting for newsrooms. None of these are sales pitches — they are configurations the operator has shipped, with the BGP-level, jurisdictional, and AUP boundaries documented per page.

xmrcloud-cli playbook list

7 workload profiles returned. All XMR-billed.

slug positioning

ai-inference open-weight llm serving on offshore gpu — vllm + ollama preinstalled, outside us export-control gating crypto-node run a btc/eth/xmr/lightning node or pos validator on hardware you control, in a crypto-neutral jurisdiction forum discourse / lemmy / phpbb at offshore latency — narrow-takedown jurisprudence and no first-strike termination journalism source-protection-grade hosting for newsrooms, leak inboxes, and securedrop / hush line intake scraping stable-asn vps for ethical crawling: clean ip reputation, generous egress, no per-target rate limits tor-relay operate a tor middle/exit relay or obfs4 bridge with bgp-stable uplinks and a sane abuse posture vpn self-hosted wireguard / openvpn endpoint — your trust boundary is the vps, not a third-party provider

Click a slug for the full playbook — threat model, recommended nodes, region notes, AUP boundary.

For the underlying hardware see node catalog; for region posture see location; for billing rationale see why-monero.

ls /usr/share/doc/xmrcloud

A curated index of the strategic surfaces — not a sitemap; /sitemap.xml is.