Design and diagrams decision

UI SFX

Do not rebuild: the project is open-source (MIT) and the repository is available, so a technical user should self-host or import it rather than reimplementing the product.

Visit website
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$20one-off6 h to build

$0/mo1 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All UI SFX alternatives, with the arithmetic →

What a replacement has to do

  • Serve the sound asset files and a tiny JS player that maps semantic cues (hover, press, success, error, etc.) to MP3/Ogg files and exposes ui.play('cue') and ui.stop('loop').

What it still won’t have

  • Hosted demo site and sponsor-managed landing pages
  • Sponsor-funded continuous sound updates (if you don't sync with upstream)
  • Any curated sponsorship placement or discovery provided on the official site

What remains hard

  • Content rightsCC0 audio license
  • Execution qualityZero dependencies
Read the build prompt

First-year cost

No published price

UI SFX does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a self-hostable UI sound library using Node.js + static hosting (Vercel/Netlify) and a tiny client JS module. Scope in: import the repository of 936 MP3/Ogg files, generate a JSON manifest mapping 78 semantic cues × 12 feels, implement a createUISFX({pack}) API that preloads sounds, exposes ui.play('cue') and ui.stop('loop'), and a demo page with feel selector and cue browser. Out of scope: authoring new sounds or training models. Include error handling for missing assets, graceful fallback when audio is blocked, automated manifest tests, and a small CI step that validates all files referenced in the manifest exist.
How we checked2 sources · 3/3 runs agreed · evidence score 99

How the score was reached

  • Self-host verdict base92
  • An open-source build was found+5
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Hard moats found in the evidence-3
  • Evidence score99

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 2

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 2 moats quoted from the page