Seven modules ship in one binary: the rule engine that decides where traffic goes, the profile system that swaps whole rule sets at once, the monitors that show what is actually happening, and the automation surface that runs it all without you.
Module 01
A rule names one application and one adapter. Applying it installs Windows Filtering Platform filters that block that executable on every other adapter, so its new outbound connections can only leave by the one you chose. Applications you have not written a rule for are untouched — Windows routes them exactly as it would have.
From the installed-applications list, read out of the registry with its real
executable path. From the running-process list, when you would rather point at
something already open. Or browse straight to an .exe for anything
neither of those found.
Each rule reports what was actually achieved rather than assuming success: whether filters were installed, how many adapters the application was blocked on, and any caveat that applies. A rule that could not be enforced says so instead of showing a green tick.
Every rule has its own switch, so you can lift one assignment without deleting it or disturbing the others. Rules persist across restarts and come back disabled, because a rule that was enforced last session is not enforced now and showing it as active would be a lie.
What blocking cannot do
Enforcement blocks rather than redirects, and that has three consequences worth knowing before you rely on it. Connections already open keep the adapter they started on until they are re-established. There is no automatic failover, so an application whose adapter goes offline loses connectivity and is not moved. And operating-system and service traffic is not covered.
Module 02
A profile is a named collection of rules. Activating one tears down the previous profile's routes and applies the new set as a single transaction, so you never sit in a half-applied state where some traffic has moved and some has not.
{
"version": 1,
"name": "Gaming",
"description": "Game on fibre, updates on the metered line",
"schedule": {
"isEnabled": true,
"startTime": "19:00:00",
"endTime": "23:30:00",
"days": "Weekdays"
},
"rules": [
{
"name": "steam",
"type": "Application",
"priority": "Normal",
"adapterName": "Ethernet",
"processName": "steam",
"processPath": "C:\Program Files (x86)\Steam\steam.exe"
}
]
}Modules 03 and 04
Routing decisions are only as good as the numbers behind them. Counters come from the same IP Helper interfaces Windows uses for its own statistics, sampled at an interval you set.
Illustrative animation. The application reads real counters from your own adapters.
Up and down per adapter with a rolling window, so a spike reads in context instead of as a single jumping number.
Bytes attributed to each process by walking the socket table and matching owners, with history kept locally so yesterday and last month are still there.
A continuous probe per adapter against a target you choose, charted so jitter and loss read as shape rather than one flattering average.
Download, upload and latency measured over the adapter's own address, so the figure belongs to that line rather than to whichever one Windows preferred. The last result stays on the adapter card for comparison.
Every adapter is judged on whether it can actually carry traffic — link state, an address, a gateway — and one that cannot says so in plain words, such as "no DHCP lease (link-local only)". You cannot assign an application to a dead line by accident.
If an adapter carrying enabled rules stops being routable, the app raises a notification naming it. Because there is no failover, this is the moment an application silently loses its network — so it is the one thing worth interrupting you for.
Diagnostics summary
One click copies your adapters, rules, enforcement state and licence status to the clipboard — the whole picture, ready to paste into a support email.
Rolling log
Every routing and isolation operation is written to a rolling local log under your own profile, openable from inside the app.
Module 04
Give a profile a daily window and it activates and stands down on its own. The scheduler runs inside the app, so it works while the window is hidden in the tray — but not while the app is closed.
Set a start time, an end time and which days it applies to — every day, weekdays or weekends. Windows that cross midnight are handled properly: 22:00 to 06:00 is one overnight span, not an impossible one.
When a window opens, the previous profile’s enforcement is torn down and the new set applied together, so you never sit in a half-applied state with some traffic moved and some not. When it closes, enforcement is cleared.
A scheduled change is a change you did not make, so it is announced — in the status bar, and as a tray notification when the window is hidden. Failures are reported with the reason rather than passing silently.
Start with Windows registers a scheduled task that launches the app elevated at sign-in, with no UAC prompt, optionally straight into the tray. Turn on Re-apply rules on launch and your last active profile is enforced as it starts.
There is no health probing or failover
Scheduling is time-based only. The app does not measure a line’s health and move traffic off it, and rules have no fallback adapter. If an adapter goes down, the applications assigned to it lose connectivity and you are notified — deliberately, rather than being moved somewhere you did not choose.
Module 05
This app runs elevated and changes live network state. Everything it does is designed to be undoable, and to be undone even if it is killed mid-flight.
Before an adapter’s interface metric is altered, the original value is written to a journal on disk. If the process is killed instead of exiting cleanly, the next launch reads that journal and restores the adapter — so a crash cannot leave a line permanently deprioritised.
WFP filters are owned by the running application. End the process and Windows discards them, which means there is no state left blocking traffic that you cannot clear by closing the app. Rules can also be removed at any time, licensed or not.
Two copies managing filters and metrics at once could overwrite each other’s restore data and strand an adapter with no correct value left to put back. A single-instance guard makes that impossible.
Removing a rule, clearing them all or deleting a profile asks first, with the count it is about to affect and No as the default button. You can switch the prompts off if you would rather work without them.
Every routing and isolation operation is written to a rolling local log with the rule that caused it. Open the folder from inside the app, or copy a diagnostics summary to the clipboard for a support thread.
No telemetry and no analytics. Rules, profiles and preferences stay on your machine. The only outbound traffic is a speed test when you press it, and a licence check when you activate a key or it re-validates one.
Module 06
Everything lives in a single window with a sidebar — no separate console, and no “advanced mode” to find before the app becomes useful. There is no command-line interface and no PowerShell module in this release.
Manage
Every connection with its address, gateway, link speed and whether it can actually carry traffic. Run a speed test, or isolate an adapter so the rest of the system deprioritises it.
Manage
Installed programs read from the registry with their real executable paths, searchable, so you can assign something without hunting for where it was installed.
Manage
What is running right now, for when it is easier to point at an open program than to find its installer entry.
Traffic
Every assignment, each with its own switch and its real enforcement state. Apply them all, or remove one without disturbing the rest.
Traffic
Named rule sets with optional daily schedules. Save the current set, activate another, or export one to JSON and import it on a different machine.
Traffic
Live download and upload per adapter, sampled at an interval you choose, with totals since the app started.
Support
Start with Windows, what minimising and closing do, tray visibility, notifications, sampling interval, confirmation prompts and verbose logging. Every switch takes effect immediately.
Support
How enforcement works, what it cannot do, and what to check when an application is not behaving — in the app, not only on this site.
Support
Trial days remaining or your licence details, activation by email and key, deactivation to move a seat, and a diagnostics summary you can copy.
Scripting is not in this release
A command-line interface and a PowerShell module are on the roadmap but are not shipping today, so nothing on this site documents them. Profile export and import is the supported way to move a configuration between machines.
The 30-day trial is the complete application, with no rule limits — enough to prove the idea on your own hardware before you decide anything.