About
Music that stays yours.
LoopMaker is built by Tarun Yadav · tarun-yadav.com
What LoopMaker is
LoopMaker is a native macOS app that turns plain-text descriptions into finished, royalty-free music on Apple Silicon Macs. Describe a sound — a warm lo-fi bed at 82 BPM, a cinematic cue, a beat for a rap demo — and LoopMaker renders it locally, then exports WAV or M4A ready for your editor or DAW.
There is no cloud render queue, no per-generation credit, and no subscription. LoopMaker is a $49 one-time purchase, and every export is yours to keep and use anywhere.
Why local-first
Music software should not ask you to upload your ideas to someone else's server to hear them back. LoopMaker runs its models on your Mac's unified memory: your prompts, your lyrics, and your rendered tracks never leave your machine during generation. The internet is used once, for license activation and the initial model download; after setup, generation works offline.
That boundary also shapes how LoopMaker integrates with AI agents. The bundled MCP server talks only to the app on localhost, so agents can queue, monitor, cancel, and find generations without any audio or prompt ever reaching a third-party service.
Who builds it
LoopMaker is developed and maintained by Tarun Yadav, an independent developer based in India. One person builds the app, answers support email, writes the release notes, and decides what ships next — which means feature requests go straight to the person who can build them.
The product is deliberately focused: a private sketchpad for music ideas rather than a replacement for a full studio production suite. Cloud tools may still be stronger for heavily polished vocal output, and the site says so plainly.
Contact
You can reach us through tarun-yadav.com. Purchase and licensing questions are handled through the same contact path; see the privacy policy for how license data is handled and the terms for license terms including the 30-day money-back guarantee.
For developers and AI agents
Machine-readable product facts live in llms.txt, integration documentation lives in the developer hub, and MCP setup is documented on the MCP page.