Ramback
Get your RAM back from the dev tools you forgot
Activity Monitor tells you something is using your memory. It doesn't tell you it's yesterday's simulator.
Ramback lives in the menu bar and lists your dev stack as things, not processes: iOS simulators (Xcode Previews too), Android emulators, Gradle and Kotlin daemons, Docker, OrbStack and Colima containers, Metro and other bundlers, dev servers, tunnels, local databases, and AI agents with the servers they started. Each row shows its RAM, who started it and how long it has been idle.
Stop one, or everything at once with Clean slate. Each thing stops the way its own tool would: simctl shutdown, adb emu kill, docker stop, or SIGTERM to the process tree. Databases stop only after you confirm; pinned rows and builds are skipped.
Free, with no account. Pro, $19 once, adds memory pressure warnings, rules with Undo and disk cleanup.
Features
- Your dev stack, by tool: simulators, emulators, Gradle daemons, containers, dev servers and agents, each with its RAM, who started it and how long it's been idle.
- Stops things properly: simctl shutdown, adb emu kill, docker stop, or SIGTERM to the process tree. Asks before forcing.
- Clean slate: one click stops everything that's safe to stop and tells you how much it frees first.
- Knows what not to touch: databases only after you confirm; pinned rows, builds, root's and other users' processes never.
- Rules: stop the servers an agent started when its session ends; shut simulators down when Xcode quits, with Undo.
- Disk tab: old simulator runtimes, DerivedData, DeviceSupport, unused Android images and old Gradle versions. Your files go to the Trash.
- CLI and MCP server: ramback status, stop and free in the terminal; list_running, stop, free_memory and find_free_port for agents.
- Free, no account. Pro is $19 once for 2 Macs. Nothing about your projects leaves your Mac.
Use Cases
- iOS developers: simulators and Xcode Previews still booted after you closed the project.
- Android developers: an emulator and a few Gradle daemons filling a 16 GB Mac.
- React Native and Flutter: a simulator, an emulator and Metro running at once.
- Working with coding agents: dev servers Claude Code, Cursor or Codex started and left running.
- Docker, OrbStack and Colima: containers grouped by Compose project, and the VM that keeps its memory.
- Low on disk: Xcode and Android leftovers you can't see from Finder.
Comments
It started with my own Mac. One afternoon memory pressure was at warning with 4.4 GB in swap. When I went looking, Xcode's build service held 1.4 GB and five Claude Code sessions about half a gigabyte each. Activity Monitor told me something was using the memory. It didn't tell me it was yesterday's simulator. So I built Ramback: one list of the dev stack by tool, with a stop button that does what the tool itself would do. It leaves databases and builds alone, and its CLI and MCP server let coding agents check what's running before they start something new.
Premium Products
Makers
Makers
Comments
It started with my own Mac. One afternoon memory pressure was at warning with 4.4 GB in swap. When I went looking, Xcode's build service held 1.4 GB and five Claude Code sessions about half a gigabyte each. Activity Monitor told me something was using the memory. It didn't tell me it was yesterday's simulator. So I built Ramback: one list of the dev stack by tool, with a stop button that does what the tool itself would do. It leaves databases and builds alone, and its CLI and MCP server let coding agents check what's running before they start something new.
Premium Products
New to Fazier?
Find your next favorite product or submit your own. Made by @FalakDigital.
Copyright ©2026. All Rights Reserved