Image and video decision

PhotoGenius

A competent developer can reproduce core photo-enhancement workflows in about a week using open-source models and tools, but matching the mobile polish, App Store distribution, subscriptions, and product UX of the paid app is outside the small-scope replacement.

View on the App Store
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

$100one-off40 h to build

$200/mo6 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 PhotoGenius alternatives, with the arithmetic →

What a replacement has to do

  • Upload photo → run enhancement/repair model → store result → download/share

What it still won’t have

  • App Store distribution, iOS-specific UX polish and native camera integrations
  • In-app purchase/subscription plumbing and platform payment handling
  • Any proprietary/trained models or datasets the vendor may use
  • Existing user base, ratings, and brand/trust
  • Polished multi-style presets and video features listed in the app

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

PhotoGenius 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 minimal AI photo-enhancer web service using FastAPI + React, containerized with Docker and deployed to a single GPU VM. Core features in scope: HTTP photo upload, enqueue job to a Redis/RQ worker, run an open-source restoration/upscale model (use PaddleGAN/GPEN) inside a GPU Docker container, store originals and outputs in S3-compatible storage, provide an API endpoint to poll job status and download results, and a basic web UI for uploads and downloads. Exclude: App Store packaging, in-app purchases, multi-style marketplace, analytics/telemetry, and video-generation features. Require: containerized builds, basic auth for the UI, retry/error handling for inference jobs, unit tests for API endpoints, and a small infra README with deployment and GPU instance sizing notes.
How we checked3 sources · 2/3 runs agreed · evidence score 60

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 3 cited sources+3
  • Evidence score60

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 · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded