RepDB VS urur.dev

RepDB's answer

RepDB is sold as a one-time download, not a metered API — you own the JSON/SQLite data and WebP images outright, with no rate limits, no per-request billing, and no risk of the vendor cutting off access. It's also the only dataset in this space with EN/DE/ES translations, transparent (alpha-channel) images with no watermark, muscle-group highlighting, safety/goal tags, and looping animations on the higher tier.

urur.dev's answer:

urur.dev focuses on one thing: validating ideas before you build. Unlike feature request tools (Canny) or launch platforms (Product Hunt), urur.dev lets you test demand at the idea stage — before writing a single line of code. Browse freely, sign in to vote and engage.

RepDB's answer

Most alternatives are subscription APIs — you pay monthly, you're capped on requests, and ExerciseDB's terms of use explicitly forbid caching or storing the data at all, so every image render is a live paid API call. RepDB is the opposite: pay once, download the files, self-host with zero ongoing dependency. It's also the only option offering true DE/ES localization and transparent images instead of a white box behind every exercise.

urur.dev's answer:

It's simple and free. No signup required to browse ideas. Sign in to vote "Want!" and track ideas you care about. Post your idea, share the link, and see if real people want it — validation in minutes, not months.

RepDB's answer

Solo developers and small teams building fitness or workout-tracking apps (iOS, Android, web) who need licensed exercise images and structured exercise data, but don't want to build their own media pipeline or depend on a rate-limited third-party API.

urur.dev's answer:

Indie developers and solo founders who build side projects. People who've wasted time building something nobody wanted and don't want to make that mistake again.

RepDB's answer

RepDB grew out of a consumer workout app its creator was building solo. Sourcing exercise images and data meant either paying for a subscription API with usage caps and no caching rights, or producing everything from scratch. The illustrated, multi-language dataset was built for us first, then split out as its own product once it became clear other indie developers had the same problem and preferred to buy the data outright rather than rent it through an API.

urur.dev's answer:

I spent 6 months building a side project nobody wanted. Twice. I realized the problem wasn't my code — it was building without validation. So I created urur.dev — the name comes from "uru uru" (売る売る), Japanese for "sell sell." The idea is simple: find your customers before you build, not after. A place where you can test if anyone actually wants your idea before you invest your nights and weekends building it.

urur.dev's answer:

HonoX (Hono + Islands architecture), Cloudflare Pages, Supabase (PostgreSQL + Auth), Vite, Tailwind CSS, and Resend for email notifications.