# Known Limitations

The Gateway is pre-launch. Known limitations should stay visible so operators understand what is proven, partial, or still gated.

## Current Limitations

- Public self-service install is not finalized until fresh-machine evidence is attached.
- License selection is still a release gate.
- Hardware support is untested until reports populate the hardware matrix.
- Appliance path requires hardware fit, image build, update path, backup/restore, and support boundary evidence.
- MSP path remains a pilot until repeat deployment templates and evidence are ready.
- Support contact endpoints must be production-ready before broad launch.
- The Gateway does not guarantee anonymity by itself.
- Browser fingerprints, logged-in accounts, payment trails, endpoint compromise, and customer behavior remain outside the gateway boundary.

## Evidence Needed To Remove Limitations

- Install transcript.
- Route and DNS checks.
- Fallback checks.
- Recovery drill.
- Hardware report.
- Privacy posture check.
- Redacted support bundle example.

## Next Step

Start with the [install readiness review](./install-readiness.html), then review [support boundaries](./support-boundaries.html) and attach the evidence above to remove the remaining release gates.

Use the [publication review](./site-qa.html) when you need the publication checks that confirm the site, copy, and release output still agree before release.

When the limits are resolved and the public story is ready, use the [production checklist](./production-checklist.html) for the final go-live review.