Image and video decision

Imgezy

A capable developer can build a useful self-hosted replacement in ~34 hours and run it cheaply; Imgezy's durable value (proprietary models, polish, support) isn't evidenced as unreproducible by a small team.

Visit website

Built by 两万焦, who ships 8 products in this index

You pay

$9.99/mo

$120/yr

Read off the official pricing page.

You’d pay instead

$100one-off34 h to build

$100/mo3 h/mo upkeep

On cash alone, building overtakes the subscription at 11 seats.

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 Imgezy alternatives, with the arithmetic →

What a replacement has to do

  • User uploads an image, types a natural-language edit prompt, send image+prompt to an image-editing model, receive edited image, preview and download; credits are consumed per edit.

What it still won’t have

  • Vendor-trained or proprietary image models and any fine-tuning they may have
  • Polished, curated UX and ongoing product polish (instant preview flows, presets)
  • Priority support, SLAs, and fraud/billing operations
  • Any undisclosed optimizations or server-side inference scale the vendor may run

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 11 seats.

Paid seatsseats

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 one-user self-hostable AI image-editing web app using Next.js (React) + Tailwind, Postgres for users/credits, Redis + BullMQ for background jobs, S3-compatible object storage for images, and Stripe for subscription & credit accounting. Integrate a third-party image-editing API (e.g., Replicate or OpenAI image-edit endpoints) to perform object removal, background replacement, and enhancement; implement model selection and credit-cost estimation. Core features in scope: image upload, prompt input, job queueing, preview before/after, download, image history, user auth, monthly credits tied to subscription, and basic admin for viewing usage. Out of scope: training your own image model, multi-tenant enterprise SLAs, advanced team roles, and mobile native apps. Include error handling, retries for model API failures, server-side validation for uploads, and unit/integration tests for the upload, job processing, billing, and API-integration paths.
How we checked4 sources · 2/3 runs agreed · evidence score 89

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 4 cited sources+3
  • Price verified on pricing page+3
  • Evidence score89

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.

Integrity checks

What held up, and what did not.

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