Windows memory, measured honestly / the extended read
Your machine says it has memory to spare. FrankinRAM measures what you would actually get back, then reclaims it from the apps sitting idle.
Windows counts memory it has already compressed or written to disk as "available," and charges shared library pages to every app that touches them. FrankinRAM cuts through both. It shows the memory you can truly use, frees it from running apps without closing them, and never touches what your system needs to keep running.
Get it
FrankinRAM is almost here.
It is in the last stretch of testing before its first public build. When it ships, the signed installer and its sha256 checksum will appear right here, served only from frankinsuite.com. Verify the hash before you run it, the same way you would with anything you download.
A note for early builds: like the rest of the suite right now, the first FrankinRAM release will be unsigned until code signing is in place, so Windows will warn you when you run it. That warning is expected. The published checksum is how you confirm the file is the one we built.
8 GB
This is the number you usually trust. Task Manager and the tray both show it. It looks like room to work. Flip the switch to see how much of it you can actually use right now.
What "free memory" actually means
Available is not the same as usable. Windows reports memory it has compressed or moved to the page file as available. On a machine showing 0.9 GB available, as little as 22 MB may be instantly usable; the rest has to be decompressed or read back from disk before anything can touch it.
Per-app numbers double-count. A shared library loaded by ten apps is counted against all ten. A process reading 185 MB of working set may hold only 108 MB that is genuinely its own. Close it and you get the 108 back, not the 185.
On a small machine, the gap is the crash. When you are running a local model with a few hundred megabytes to spare, memory that Windows counted but cannot instantly hand over is the difference between finishing a session and an out-of-memory failure mid-inference.
How FrankinRAM fixes it
The truth, per app and for the whole system. Private working set for each process, truly-free memory for the system. The numbers you act on are the numbers you can actually reclaim, matched to what Windows shows only in its optional columns.
Trims memory from running apps without closing them. A soft reclaim pulls back working-set memory from apps sitting idle. They keep running; the memory comes back to you.
Suspends the groups you choose, fully reversibly. Every frozen group can be resumed from the dashboard, the tray, or the command line, and a restore ledger tracks exactly what changed.
A dial from Gentle to Max, per app. Max converges on each app's real floor by learning it over time, so it reclaims as much as it safely can without sending the app into a thrash. A watchdog measures actual memory every cycle and holds the app there rather than trusting the request went through.
Understands what a process is, not just its name. A four-layer classifier reads each app by its metadata, its loaded libraries, and its behavior, so renamed or unknown apps get categorized correctly instead of dumped in a catch-all. It can never reclassify something system-critical as optional.
That is how far a reported working set can overstate what you would actually reclaim. Measured live: one Claude process reading 185 MB held only 108 MB that was truly its own, the rest shared with other apps. FrankinRAM shows you the 108, because that is the number you can act on.
It asks first, and everything is reversible
The things your system needs are off limits. A built-in SafetyGuard excludes system-critical and important processes, including your terminal, the active shell, and console hosts, before any plan is even drawn. FrankinRAM will not touch them, at any intensity.
Automatic optimization needs your yes. When it triggers, a popup lists the exact apps it would act on, each with the memory it would free. Untick any of them. Switch a freeze to a gentler trim. Do nothing and nothing happens; the popup expires on its own and your RAM stays where it was.
Silent only when it is identical. Once you approve a plan, the same situation is handled quietly the next time, logged in the activity feed. The moment the plan would differ by even one app, the popup comes back and asks again.
Nothing is a one-way door. Every freeze resumes, the restore ledger tracks each change, and uninstalling even puts back any third-party startup items FrankinRAM had disabled, so nothing else on your machine is left worse off.
Built for the machine that needs it
Made for modest Windows hardware. The machines where a few hundred megabytes decides whether a session survives are exactly the ones FrankinRAM is written for. Windows 10 and 11, 64-bit, installed for your user alone with no machine-wide changes.
Nothing leaves your machine. The engine listens only on your own loopback address, behind a per-session token. No account, no sync service, no telemetry. Your settings and reports are a folder on your own disk.
Part of FrankinSuite, distributed from a domain we own. No code host, no marketplace, no storefront that can remove it. When it ships, it will be served from frankinsuite.com and nowhere else.