Consumer launch needs clarity
Private access
Private access that stays separate from the public VPN promise
RavenVPN can carry private access concepts such as connectors and private routes, but those capabilities should not pollute the public consumer claim surface.
Why separate private access from the public path
Public VPN messaging and private access architecture solve related but different problems.
Private access needs policy and route boundaries
Support and recovery language should match the user path
What a good public explanation looks like
Customers should understand that private access exists without being forced through internal architecture terms.
Describe the use case
Keep internal connector state off public pages
Link to the right platform entry points only when needed
Common questions
Only visible customer-facing answers belong here.
Is private access the same as the public VPN path?
No. Private access extends the platform for managed routes and connectors, while the public path stays consumer-focused.
Will consumer pages show connector rollout by default?
No. Connector and route detail should appear only in the contexts that need them.
Continue from here
These pages should connect back into real product paths.