Disclosure: this article contains affiliate links. If you buy through them we may earn a commission at no additional cost to you. Our recommendations are based on the evidence recorded alongside this article, and prices were verified on the date shown.

You're looking at ElevenMusic Sounds because it showed up on Show HN with an unusual premise: the loop library itself grows as other people generate new sounds. That's the whole pitch, and it's the only claim currently verifiable about the project. This piece tells you exactly what's confirmed, what isn't, and what the "grows as people generate" model implies if you're the one who ends up building or hosting something similar.

What changed and why it matters

The submission title is specific and checkable: ElevenMusic Sounds is a loop library that grows as other people generate sounds, posted to Show HN by a user identified as sigvef, pointing to elevenmusic.io/sounds. The page was directly captured and confirmed live as of August 15, 2026 — it's a real, currently reachable project, not a dead link or a placeholder.

What makes this worth a second look isn't the novelty of AI-generated audio — that's common now. It's the growth mechanic: the catalog isn't fixed at launch, it expands with every user who generates a sound. That single design choice has direct consequences for anyone thinking about building, cloning, or hosting a similar product, because a library that grows indefinitely from user activity is a storage and database problem before it's a music problem.

The list

Here's what's actually confirmed, what's explicitly missing from the record, and what the model implies for infrastructure decisions.

• Core mechanic, verified: ElevenMusic Sounds is a loop library that grows as other people generate sounds, per the project's own Show HN submission title. This is the one factual claim with a direct source.
• Source and attribution, verified: the submission was posted by user sigvef, and the destination page (elevenmusic.io/sounds) was live at time of check.
• Pricing, licensing, and format: not stated. Nothing in the available record specifies what the loops cost, how they're licensed for reuse, what audio format they ship in, or whether there's a usage cap. If you need those answers before evaluating the project, they aren't part of the verified record here — treat that as an open question, not an assumption to fill in.
• Scale and traffic: not stated. There's no confirmed figure for how many loops exist, how fast the library is growing, or how much traffic the Show HN post drove. Any number you see elsewhere should be checked against the source directly.
• The implied storage problem. A catalog that grows from user-generated audio files, with no stated ceiling, needs object storage that scales without a manual resize step — that's the category DigitalOcean Spaces object storage sits in, and you can Check current price for DigitalOcean Spaces object storage to see what that tier actually costs today.
• Best for: developers evaluating the Show HN post as a signal about generative-audio tooling, or anyone scoping the infrastructure a growing user-content catalog would require.
• Skip it if: you need firm answers on pricing, licensing, or catalog size before making a decision — those specifics aren't in the public record yet, and this piece won't manufacture numbers that don't exist.

What to do next

If the appeal of ElevenMusic Sounds is the growth model itself — a catalog that gets bigger because users keep contributing — the practical next step isn't signing up for the app. It's pricing out the three components any project like this actually runs on: file storage, compute, and a database that can track what's been generated and by whom.

Start with where the files live. User-generated audio doesn't shrink, and a storage tier that bills predictably as it scales matters more here than raw speed. You can Check current price for DigitalOcean Managed PostgreSQL for the managed database layer that would track sounds, tags, and generation history without you running your own PostgreSQL instance — check current pricing before committing to a schema design that assumes unlimited headroom.

For the app itself, a small compute instance is usually enough to start — you don't need a fleet to serve a Show HN launch. You can Check current price for DigitalOcean Basic Droplet (2 vCPU / 4 GB) to see whether a 2 vCPU / 4 GB tier covers a first deployment, and scale from there once you have real traffic numbers instead of guesses.

None of this requires committing to DigitalOcean specifically, but if the three-service pattern above matches what you're planning to build, it's worth seeing the numbers rather than estimating them. You can See current pricing at the merchant for the full current rate card before you size anything.

The decision in front of you isn't whether ElevenMusic Sounds is good — the evidence doesn't cover that. It's whether the model it's built on (a catalog that grows from user activity) is one you want to build yourself, and if so, whether the storage, compute, and database costs pencil out before you write the first line of the generation pipeline.