Trust anchor
Repository, license, contribution guide, security model, install guide, and hardware matrix.
Launch plan
Open release, sponsor funding, and paid operations move together.
The launch is blocked on public repo assets, install docs, support rules, sponsor paths, runbooks, and test evidence.
Fresh-machine path
Installer, first-run policy, recovery path, and validation checklist before the install CTA becomes final.
Support without capture
Sponsor page, support intake, appliance waitlist, and MSP pilot path with clear support boundaries.
Evidence before scale
Demo, screenshots, public test summary, recovery drill, and first runbook execution report. Screenshots should use realistic synthetic values and note the claim each image supports.
Do not broad-launch until install, rollback, support redaction, and public evidence are linked.
Share with selected technical operators only after install scope, redaction rules, and recovery expectations are clear.
Successful install reports, route/DNS evidence, recovery drill results, support boundaries, and operator reports.
Verify production hosting, canonical metadata, sitemap, and public host routing before broad launch.
Security checks report no unresolved high-severity issues before broad launch.
Keep anonymity claims bounded, avoid VPN-only framing, and tie every paid offer to operational value.
Keep public-facing launch copy focused on operator value, product readiness, privacy limits, support boundaries, and evidence.
Keep public-facing launch copy focused on operator value, product readiness, privacy limits, support boundaries, and evidence.
Published assets should avoid private notes, local paths, credentials, temporary hosts, and machine-specific assumptions.
Published assets should avoid private notes, local paths, credentials, temporary hosts, and machine-specific assumptions.
Launch evidence
The launch plan needs screenshots for install, operations, and proof gates.
Shows the visible state behind launch claims about routing, DNS, tunnel, devices, and backup.
Shows the route and fallback policy surface that should be proven before install promotion.
Shows the rollback and backup surface that keeps paid operations bounded.