Independent proxy assets
Store configuration, groups, upstream relationships, and results in the proxy library while an account binds one entry.
Proxy management topic
Keep every hop visible from the proxy library to account launch.
Organize proxies as independent assets and test them on the current computer. Accounts select one final entry, then verify the actual exit and timezone before launch.
MaskPilot 
Proxy runtime principles
The backend stores configuration and results; the current computer performs real tests.
This keeps the test path close to the network route used after account launch and prevents the backend from connecting to user proxies.
Desktop-side testing
The desktop client checks health, latency, and multi-hop routes. The backend does not connect to a user proxy.
Actual exit verification
Before launch, the actual route must return a non-empty timezone or the account does not start.
Proxy runtime flow
Import, testing, assignment, and launch have different responsibilities.
Historical tests help evaluate state, but they do not replace confirmation of the current exit immediately before account launch.
Normalize configuration before saving a proxy asset.
The desktop client parses and previews JSON, YAML, or common proxy text. The backend accepts normalized single-exit configuration with lightweight validation.
- Group by region, purpose, or source
- Do not send sensitive credentials to the website for testing
- Maintain chain relationships in the proxy library
- Do not recreate routes in the account form
Check the protocol and real outbound behavior.
The client runs the test and reports health, latency, quality, and a concise diagnosis. An open port with an invalid proxy protocol still fails.
- The backend does not connect to user proxies
- Protocol behavior, not an open port, determines health
- Results include time and quality state
- Failure guidance keeps the next step actionable
Test multi-hop routes one prefix at a time.
Test the first hop, then the first two, and continue through the complete route to identify where failure begins. The account still selects one final entry.
- Store upstream relationships with proxy assets
- Test every prefix through the actual route
- Map failure directly to a hop
- Do not read legacy account chain records
Recheck the exit timezone before starting the browser.
When an account uses a proxy, the desktop client obtains exit information through the actual route and uses its non-empty timezone instead of historical configuration.
- The complete route determines the exit timezone
- A failed request stops this launch
- Do not fall back to cache, account, or system timezone
- Clear the local launch reservation after failure
Technical boundaries
Every result has a source, time, and limited scope.
Proxy state changes with the device, network, and upstream service. Saved results support decisions but are not a permanent availability promise.
One entry per account
Multi-hop routes use upstream relationships rather than a second route model on the account.
The backend does not test proxies
The server distributes configuration and stores results without connecting to user proxies.
History is not a launch decision
Launch must obtain the exit timezone through the actual route again.
Internal dependency names stay private
The website explains supported configuration and visible behavior without marketing an internal runtime.
FAQ
Questions before you start
Why does a proxy fail even when its port is open?
MaskPilot checks the proxy protocol and outbound behavior. An open port with an invalid protocol is still unavailable.
Where is a multi-hop route configured?
Maintain upstream relationships in the proxy library. Account create and edit flows select only the final entry proxy.
Does the backend connect to or test my proxy?
No. Health, latency, and multi-hop tests run from the desktop client on the current computer. The backend stores reported results.
Why can launch fail after an earlier successful test?
Launch obtains the exit timezone through the current actual route. Network changes, upstream failures, or a missing timezone stop that launch.
Start with one proxy
Complete one local test and test-account launch.
Download MaskPilot, import one authorized proxy configuration, and verify its protocol, exit, and timezone before expanding the proxy library.