DESIGN §12 · defaults table
Presets at coxswain init,
not separate products.
The same binaries run for one operator and for a team of
thousands. The difference is one flag —
--personal or --enterprise — which
sets defaults. Every field is reconfigurable after first run.
| Setting | --personal | --enterprise |
|---|---|---|
| Regions | 1, nearest | operator picks |
| Idle nodes | none | encouraged, pre-positioned, stopped |
| Protocols | AmneziaWG default, XRay optional | both |
| Relay | embedded | embedded + remote relays |
| Account sync | on | optional (MDM-only deployments run none) |
| Admins | one (the operator) | core admin + UI-added others |
| Audit retention | 30 days | 1 year |
| Metrics retention | 7 days | 90 days |
| REALITY decoy site | www.microsoft.com | configurable, rotated |
| Endpoint rotation | off | on — per-client, live |
| Engine | identical | identical |
| Licence | Apache-2.0 | Apache-2.0 |
| Source | same repos | same repos |
| Price | your cloud bill | your cloud bill |
why this matters
Most VPN brands ship two products.
A cheap personal tier and an expensive enterprise tier — sold side-by-side, but built from different codebases. The personal product is the marketing funnel; the enterprise product is the revenue.
PharosVPN is the inverse. One project, both audiences, no upsell path between them. It's Apache-2.0, so anyone can run, modify, and build on the platform without a fee or a contribution obligation — there's nothing to upsell toward. Improvements upstream are welcome, not required.