Case study: growing Aurral to 1.7M pulls with no ad budget
Aurral is a self-hosted music discovery app for Lidarr users. I built it in January 2026 because I wanted an Overseerr for music and nobody had made one. Eight months later it has an audience I never planned for. This is what I did to get there and what I think actually mattered.
The numbers
| GitHub stars | 1,710 |
|---|---|
| Forks | 81 |
| Container pulls | 1.7 million |
| Releases | 224 |
| Merged pull requests | 585 |
| Closed issues | 277 |
| Code contributors | 29 |
| Discord members | 300+ |
| Marketing spend | $0 |
Figures are from GitHub and Discord on October 1, 2026, eight and a half months after the first commit. Container pulls count every pull, updates included, so they measure activity, not unique installs. Aurral has no telemetry, which is part of why people trust it, so I can't give an install count.
The starting point
My YouTube Premium subscription ran out, I went back to running my own music server, and adding music through Lidarr was painful. Movies and TV had Overseerr and Jellyseerr. Music had nothing comparable. I built the first version in a day and posted it to r/selfhosted.
The launch post was not a marketing document. The first line was a wall of siren emojis saying the app was made with AI, built for me alone, and that I wouldn't add features. It got 469 upvotes and 165 comments. In hindsight it worked because it was honest and because the gap was real.
Two weeks earlier I had posted Hypermind, a joke P2P project, to the same subreddit. It got 2,014 upvotes. Some people recognized my name when Aurral showed up, and I think that helped the launch get read.
My main Reddit posts about Aurral
| Date | Where | Post | Result |
|---|---|---|---|
| Jan 16 | r/selfhosted | Launch | 469 upvotes, 165 comments |
| Feb 13 | r/selfhosted | "Aurral 2.0: from vibe-coded weekend project to actually-good music overseer" | 0 upvotes, 20 comments |
| Feb 13 | r/Lidarr | "hi i created an app to help make lidarr a little better" | 135 upvotes, 53 comments |
| Feb 16 | r/Softwarr | "I think my app might belong here!" | 89 upvotes, 31 comments |
| Apr 27 | r/Softwarr | 1.52.0 update with PR links | 38 upvotes, 9 comments |
| May 28 | r/Lidarr | Three-month update | 42 upvotes, 44 comments |
| May 30 | r/ARR | Plain introduction | 7 upvotes, 3 comments |
| Jun 18 | r/Softwarr | Call for v2 testers | 56 upvotes, 29 comments |
That's eight posts in eight months, leaving out a few crossposts. I didn't post on a schedule, and most of the growth happened between posts.
What I learned from the posts
Niche communities beat big ones after launch. On the same day, my 2.0 post flopped in r/selfhosted and a plain, lowercase post did well in r/Lidarr. My read is that r/selfhosted had seen Aurral already and the word "vibe-coded" in the title invited an argument. r/Lidarr was full of people with the exact problem Aurral solves.
Updates work when they show receipts. The April update listed star count, download count, 97 merged PRs, 106 closed issues, and linked each feature to its pull request. People could see the project was alive.
Asking for help beat announcing. The June call for v2 testers did better than either update post before it. People like being asked.
Other people's posts did more than mine. Users crossposted Aurral to r/Servarr. Someone started an "Aurral Opinions?" thread with 22 replies. Someone else built Jellygate, a Jellyfin login bridge for Aurral, and posted it to r/jellyfin. By August people were asking "Aurral vs Dropneedle?" without me involved. That's when I knew it had its own momentum.
What drove growth between posts
Showing up wherever Aurral was mentioned. I set up F5Bot to email me whenever anyone on Reddit mentions Aurral. When someone has a problem or asks a question, I go to that thread and help. A stranger getting a reply from the developer is better marketing than anything I could post myself, and everyone who finds that thread later sees it too.
A Discord with a small team. The Discord has over 300 members and is where support, testing, and feature discussions happen. A few regulars help me answer questions and test builds, so new users get help even when I'm asleep.
Shipping in public. 224 releases in eight months means existing users always had a
reason to come back and an update to talk about. A separate :test image let eager users try
new work early, and they became the people reporting bugs before stable releases.
Taking criticism seriously. When Soulseek users complained that Aurral clients took files without sharing, I started a fix that day, shipped sharing on by default a week later, and eventually rebuilt the downloader around slskd. I wrote that up separately in When my users became someone else's problem.
Docs and a real website. aurral.org and docs.aurral.org now have setup guides for 13 integrations and a troubleshooting page. Every repeated Discord question is a candidate for a docs page, and every docs page is something that shows up in search.
What didn't work
- Crossposting the same text to r/musichoarder and r/navidrome got nothing. Each community needs its own framing.
- My May update post was removed from r/selfhosted by moderators. Big subreddits have rules about repeat project posts, and I should have read them first.
- Launching with "I won't add features" set an expectation I immediately broke. It turned out fine, but it's not a promise I'd make again.
What I'd take to a company
- Find the community that already has the problem, then post there in its own voice.
- Be upfront about the weak spots before someone else points them out.
- Back every update with numbers and links people can check.
- Treat support threads as public content. They get read far more than they get written.
- Turn repeat questions into docs and product changes, and tell people when you did.
- Listen to the communities next to yours, not just your own users.
Aurral is MIT licensed and on GitHub. If your team is hiring for developer relations or developer marketing, I'd like to hear from you.