Image and video decision
Loremfaces
A single developer can reproduce the core hosted service (five stable placeholder images + URL routing + docs) in a weekend and run it cheaply; no durable moats prevent replacement.
Visit website↗Built by Rahul K, who ships 15 products in this index
Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$20one-off10 h to build
$5/mo3 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 Loremfaces alternatives, with the arithmetic →
What a replacement has to do
- Serve five stable avatar images at size-based URLs, route requests like /{size}/id/{id}.jpg, and provide framework examples and docs.
What it still won’t have
- The vendor-managed convenience of an instantly available hosted endpoint and domain.
- Any proprietary branding, analytics, or backlink bundle offered on the vendor site.
- Built-in site comparisons and curated framework integration pages unless recreated.
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Loremfaces 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
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
Build a minimal placeholder-avatar service using Node.js + Express (or a static site + redirect rules) and AWS S3 (or Cloudflare R2) + Cloudflare CDN. Core features: (1) store five distinct avatar images, each pre-rendered at sizes [24,42,48,96,128,256]; (2) implement URL routing /:size/id/:id.jpg validating size ∈ {24,42,48,96,128,256} and id ∈ {1..5} and returning the correct image with proper caching headers; (3) host a small docs site with HTML/React/Vue/Next/Svelte integration examples and a live preview snippet; (4) include health-check endpoints and automated tests that verify each URL returns 200 and correct Content-Type; (5) add CI pipeline to deploy images and docs to S3/R2 and purge CDN cache on deploy. Out of scope: training or running custom AI models, generating faces on-demand, user accounts, analytics dashboards. Require error handling for invalid sizes/ids and unit/integration tests for routing and deploy steps.How we checked
How the score was reached
- Build verdict base78
- An open-source build was found+5
- 4 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score90
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 · 4
Every page the run actually retrieved.
- official productLoremFaces homepage
- official docsLoremFaces docs
- open sourcepremieroctet/photoshot
- open sourceCodennnn/vue-color-avatar
Integrity checks
What held up, and what did not.
