Supporting 1.7 million pulls without a support team
Aurral has been pulled 1.7 million times. There's no support team. There's me, a few regulars on Discord, and a system that's mostly about being findable and fast. Here's how it works.
Go where people already are
Most people with a problem don't open a GitHub issue. They post on Reddit, ask in a general self-hosting thread, or mention Aurral in passing while asking about something else. I use F5Bot, a free service that emails me whenever a keyword shows up on Reddit. Every time someone mentions Aurral, I get an email and can go help.
That covers a lot of ground. In August someone posted on r/Lidarr that Aurral 2.1.0 couldn't reach Lidarr anymore. Someone else asked r/Softwarr how Aurral compared to Dropneedle. Someone asked r/selfhosted whether people liked Aurral and whether it was vibe-coded. None of those people tagged me. A reply from the developer in a public thread helps the person asking and everyone who searches the same question later.
Give the community a home
The Discord, now over 300 members, is where ongoing conversations live. Setup help, bug reports that need back-and-forth, test builds, and feature ideas all happen there. A few regulars help answer questions and moderate. Their help is the only reason support keeps working at this size.
GitHub handles what needs a paper trail. As of October, 277 issues have been closed and 585 pull requests merged, from 29 contributors.
Answer it once, then fix the cause
A question I answer twice is a docs gap. A question I answer five times is a product bug. Some examples of what that loop produced:
- Configuration moved from an
.envfile to the web UI with a first-run setup flow. - Health checks show which service is down instead of a generic error.
- docs.aurral.org has a setup guide for each integration and a troubleshooting page.
- A Spotify CSV converter in the docs walks people through bringing their playlists over.
Tell people what changed
Aurral has shipped 224 releases since January. Most people don't read release notes, so the important
changes also go where users are. My Reddit updates list the biggest changes and link each one to its pull
request. When 2.0 changed how Aurral is deployed, the post included a migration cheat sheet with the old
setup next to the new command. Before v2 went stable, a :test image let eager users try it
early and report problems.
Be honest up front
The first line of my launch post said Aurral was made with AI. So when someone asked months later whether it was vibe-coded, the answer was already public and there was nothing to dig up. People can decide whether they're fine with how something was built. They can't forgive finding out you hid it.
The same goes for limits. If a fix depends on another project, I say which one and link to it.
What I'd bring to a team
- Set up mention alerts for every place your product gets discussed, not just your own channels.
- Reply in public whenever you can. The answer gets read long after it's written.
- Track repeat questions and turn them into docs, then into product fixes.
- Give your most helpful community members real responsibility.
- Take release notes to the places where users already are.