SP VPN Persistence
SP VPN Persistence is being shaped around a common Windows VPN problem: connections drop, startup timing changes, route state gets unclear, and the person using the machine may not notice until work has already stalled.
The product direction is a focused tray application that watches Windows VPN profile state, physical adapter state, route checks, and reconnect attempts so VPN behavior is visible instead of guessed at.
VPN drops are easy to miss until work breaks.
Windows VPN profiles can disconnect after sleep, adapter changes, weak networks, credential prompts, service timing, or normal remote-work friction. When that happens, operators need a clear state and repeatable reconnect path instead of checking Windows menus and guessing what happened.
Watch the real state and make reconnect behavior visible.
SP VPN Persistence is designed to sit in the tray, observe configured Windows VPN profiles, check whether the intended route is available, and make reconnect attempts, fallback choices, and companion status easier to understand.
One place for profile choice, route checks, and companion state.
Representative interface direction. Final layout and feature details may change as the product moves through development.
VPN persistence control panel
Watch. Test. Reconnect. Report.
Select the profiles
Choose the primary and backup Windows VPN profiles the workstation should use for remote access.
Watch adapter state
Track physical network availability so reconnect work can respond to real uplink conditions instead of blind retries.
Test the route
Use a configured route target or probe host to confirm whether the expected VPN path is actually usable.
Reconnect visibly
Reconnect attempts, backup selection, and status changes are surfaced to the operator instead of buried in Windows networking state.
Without VPN persistence
- VPN disconnects are discovered only after applications stop working.
- Operators check Windows VPN menus manually and guess whether the route is valid.
- Backup VPN profiles are easy to forget during normal troubleshooting.
- Reconnect attempts are hard to explain after the fact.
With SP VPN Persistence
- Primary and backup VPN profiles are visible in one focused tray application.
- Route checks make the useful VPN path clearer than a connected/disconnected label alone.
- Reconnect behavior becomes a repeatable workflow instead of a manual scramble.
- Companion Killswitch state can be shown beside the VPN monitoring workflow.
Focused VPN visibility for Windows profile-based work.
Windows VPN Profiles
The product direction is based around standard Windows VPN profiles instead of locking the workflow to one VPN provider.
Primary and Backup VPNs
Operators can model the expected primary path and a backup profile so reconnect choices are visible.
Route Target Checks
A configured target helps answer the practical question: is the route that matters actually available through the VPN?
Adapter Awareness
Physical adapter state gives reconnect behavior better context when a laptop sleeps, docks, roams, or changes networks.
Tray Operation
The app is designed to live in the tray so VPN monitoring and controls stay close without taking over the desktop.
Killswitch Companion
SP Network Killswitch is optional, but the two products pair well when a workstation needs both reconnect visibility and traffic hold behavior.
For Windows machines where VPN state should be obvious.
Remote support workstations
Systems that need a clear VPN path before support tools, internal resources, or customer workflows are reliable.
Field laptops
Machines that sleep, move between networks, and need visible reconnect behavior without a full management platform.
Small IT operations
Teams that want practical VPN state visibility without turning a focused reconnect issue into a large deployment project.
In development and expected to change.
SP VPN Persistence is in development. The product direction is based on Windows VPN monitoring, reconnect visibility, route checks, and optional companion workflow with SP Network Killswitch. Interface details, defaults, and exact behavior may change before release.
Screens shown on this page are representative product-direction visuals. They are intended to explain the workflow without exposing live VPN provider names, machine details, or network configuration.
Need Windows VPN state to be easier to see?
Talk with Source Potato about SP VPN Persistence, Windows VPN profile behavior, reconnect workflow, and whether pairing it with SP Network Killswitch makes sense for your machines.