Mopup › About
Who makes Mopup
I'm Suman Maharjan, and I make Mopup on my own. I write the code, ship the updates and answer the email that comes to support@mopup.online.
Why I built it
In October 2026 my MacBook was down to 36 GB free on a 500 GB disk and swapping 13 GB of memory. I assumed my projects had grown. My code was about 2 GB. The rest was what development leaves behind:
- 85 GB of build caches.
- 52 git worktrees, many of them made by coding agents, and 12 GB of them in branches already merged.
- A dev server an agent started and nobody stopped: 42 processes holding 7.6 GB of memory.
- Two workerd processes still running 8 hours after their dev server quit.
I wanted one place that found all of it and said which parts were safe to remove. So I built a Mac app that finds it, says what each item is and what removing it means, and removes only what your tools rebuild or what you pick.
It grew from there into a cleaner for any Mac: a map of where your space goes, a look inside System Data, duplicate files and photos, an uninstaller, and a chart of how your disk fills up over time.
How it's made and sold
- Mopup is a native Mac app, written in Swift, for macOS 15 and later.
- Every release is signed with my Developer ID and notarized by Apple before it reaches you.
- There's no account, no analytics and no tracking. What Mopup finds on your Mac stays on your Mac. The privacy page lists the little it does send.
- Paddle runs the checkout as merchant of record, so your receipt comes from Paddle.
What you can expect from me
- Mopup deletes only what your tools rebuild, or what you choose. The safety page lists every rule it follows.
- If Mopup gets something wrong, I want to know. Write to support@mopup.online and you'll hear back from me.
- Not for you? You get your money back within 30 days, no questions asked. See the refund policy.
- Updates arrive in the app, each with a note on what changed.
Get in touch
Email support@mopup.online, or use the feedback form, which you can also open from Mopup's settings.