Back to The Gateway

Known limitations

Pre-launch means some claims still need proof.

The Gateway keeps limitations visible so operators can separate proven behavior from release gates.

Release gates
  • License selection, fresh-machine install evidence, rollback, hardware matrix, and production contact endpoints.
  • Self-service install remains gated until evidence is attached.
Product gates
  • Appliance, MSP, and managed operations paths need repeatable evidence before broad promotion.
  • Known hardware support starts as untested until reports populate the matrix.
Privacy boundary
  • The Gateway can help verify privacy posture but does not guarantee anonymity by itself.
  • Browser fingerprints, logged-in accounts, payments, and endpoint compromise remain outside the gateway boundary.

Next action

Use install readiness to clear the first release gates.

Start with the install readiness review, then attach install transcripts, route and DNS checks, fallback checks, recovery drills, hardware reports, and privacy posture checks to remove the remaining limitations.

Request install readiness review Open evidence checklist Open launch status