Seventy-four controls, six surfaces and one execution pipeline. This page walks the whole thing — what each part reads, what it writes, what it records so a change can be walked back, and the things it deliberately refuses to do.
Selecting a control stages it. Nothing executes until you open the plan, see every operation written out with its target key, command or package, and confirm. The plan you see is the plan that runs — there is no second, quieter list.
Reversal designed in, not bolted on
Each operation captures its exact prior value at the moment it runs, into a revert journal keyed to that run. Undo replays the journal backwards from the History page, and takes its own restore point before it starts.
A pipeline that fails closed
Review, confirm, restore point, registry export, changes, journal. If the restore point cannot be created, execution stops before the first write rather than continuing with a warning nobody reads.
Validated against your machine
Startup detection reads CPU class and core count, memory, GPU family across RTX 20/30/40/50 and GTX 16, system drive, laptop thermals and your Windows build. Controls your machine cannot support are filtered out before you ever see them.
A catalogue you can audit
Every control is a JSON manifest entry with its own detection, apply and revert steps, minimum Windows build, risk tier and a documentation link. Eleven manifests, all in the public repository, all readable without running anything.
A short list of refusals
No blanket TCP presets, no registry cleaning, no wholesale service disabling, no driver or firmware installs, no overclocking from the app. The category's staples are absent on purpose.
01The app
Six surfaces, one model.
Optimal is organised the way the work actually goes: see the machine, choose the changes, review them, apply them, and keep the receipts.
01
Dashboard
What your machine currently is, read-only.
Live CPU, GPU, memory, system drive and Windows build detection
Current state of every control it can detect, before anything is staged
A suggested starting plan derived from the hardware — a suggestion, never a selection
02
Tweaks
The catalogue: 74 controls across nine categories.
Each control names its registry key, command or AppX package
Risk tier on every entry — verified, situational or aggressive
Filter by category, search by name, and expand any control for its full tradeoff
03
Networking
Read the connection first, then the controls that apply to it.
Adapter, link speed, IPv4, gateway, addressing, MTU and DNS — all read-only
Live gateway and public-route latency, measured on demand
Three reversible hardening controls, plus organised shortcuts into Windows' own network tools
04
Apps
Twelve curated installs through exact WinGet IDs.
Browsers, utilities and measurement tools, each pinned to a published WinGet ID
Everything starts unchecked; nothing is installed as part of a preset
The only part of Optimal that needs the internet after download
05
History
Every run, what it did, and the button that undoes it.
One entry per run with its operations, timestamps and outcome
Undo replays the revert journal behind a fresh restore point
Per-run registry exports written as readable .reg files you can inspect yourself
06
Simple and Advanced
One global switch over how much of the catalogue you see.
Simple shows the everyday controls and hides expert policy and security ones
Advanced exposes network hardening, Memory Integrity and Windows Update policy, with the full tradeoff written out
The switch changes what is shown, never what is selected
02Safety model
The six gates every run passes.
These are not settings. They are the order the engine executes in, and there is no path around them.
GATE 01
Startup is read-only
Detection reads hardware and current state. No change is staged, let alone applied, by opening the app.
GATE 02
Selection is manual
Optimal opens with zero controls selected. Onboarding can suggest a plan; accepting it is a click you make.
GATE 03
Review shows the operations
The confirmation step lists every operation with its exact target. Nothing is summarised into a count.
GATE 04
A restore point comes first
Applying or undoing requires a fresh System Restore point. If Windows cannot create one, nothing executes.
GATE 05
Registry state is exported
Affected keys are written out per run as readable .reg files, independent of the app's own journal.
GATE 06
The journal records prior values
Each operation stores the value it replaced, which is what makes an operation-level undo possible at all.
03The catalogue
All 74, by category.
Counts come straight from the manifests. Each entry lists what falls under it; the app shows the exact key or command for every one.
Clipchamp, Solitaire, News, Weather, Feedback Hub, Get Help, Microsoft 365 hub, Power Automate, Dev Home, 3D Viewer, legacy Cortana, Messaging, Mixed Reality Portal, Sway, Wallet. Security, Store, Terminal, runtimes and frameworks stay protected.
Network
3 controls
Local-network hardening, reversible
Disable LLMNR name resolution, block insecure SMB guest logons, and require SMB client signing. Advanced-mode controls with documented Microsoft sources, all reboot-gated and revertible.
Explorer
10 controls
File Explorer, Start, and taskbar behaviour
Show file extensions and hidden files, compact spacing, align the taskbar left, End task on the taskbar, last-active click, open to This PC, and drop search highlights, Phone Link and Start recommendations.
Gaming
8 controls
Input, capture, and NVIDIA driver profiles
Game Mode on, pointer acceleration off, background capture and Game DVR off, Sticky Keys shortcut and Memory Integrity off, plus the Balanced Latency and Competitive NVIDIA Profile Inspector profiles.
System
7 controls
Shell rendering and filesystem behaviour
Dark mode, transparency effects, Storage Sense, long path support, background Store apps, menu delay, and the Explorer startup delay.
Power
2 controls
The OPTIMAL POWER PLAN and fast startup
Builds a dedicated powercfg scheme derived from Ultimate Performance, and switches off fast startup so a shutdown is a real shutdown.
Update
3 controls
How and when Windows Update interrupts
Stops Delivery Optimization seeding updates to other machines, excludes drivers from quality updates, and blocks restarts while you are signed in.
Total74 controls · 9 categories
04How it compares
The difference is what it tells you.
Every optimizer claims speed. The question worth asking is what each one shows you before it writes, and what it leaves you when you want it back. Drag the handle to compare the same moment in both.
Comparisons describe common behaviour across the category rather than any single product. Every claim in the Optimal column is verifiable in the manifests and source.
05Limits
What Optimal will not do.
A tuning tool is defined as much by what it declines to touch. These are permanent positions, not a roadmap.
No blanket TCP registry presets
They are copied between tools without measurement, they are not one-size-fits-all, and they are the single most common reason a “network optimizer” makes a connection worse. Optimal measures the route and exposes the supported Windows controls instead.
No registry cleaning
There is no evidence that removing orphaned registry entries improves performance, and plenty that it breaks installs. Optimal ships nothing of the kind.
No wholesale service disabling
Batch-killing services by preset is how tweaking tools break Windows Update, printing and audio. Where a service matters, the specific policy control is offered on its own.
No drivers, firmware or overclocking
The app does not install drivers, touch GPU power and fan curves, or push clocks. That work is real, and it is done by a person in a booked session rather than by a button.
No system-wide app removal
Debloat removes current-user AppX packages, which reinstall from the Store. Security, Store, Terminal, runtimes and frameworks are protected and cannot be selected.
No numbers it cannot show you
Optimal claims no FPS figure and no “percent faster”. It reports what it changed and what the machine reads now, and leaves the benchmarking to a benchmark.
Read it, then run it.
The documentation covers the execution pipeline, the manifest format and every control in the catalogue. The download is the same build described on this page.