Image and video decision
AI Photo Forge
A single capable developer can build and operate a Telegram-based AI headshot bot in about one week using existing open-source stacks and hosted inference; no durable moats are evident from the site, so self-build is realistic and cost-effective for a technical user.
Visit website↗Built by Alex, who ships 10 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.
$100one-off36 h to build
$50/mo6 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- User sends a photo to a Telegram bot → bot uploads and validates image → run headshot-style image generation model → store result and return generated headshot to the user
What it still won’t have
- Hosted, polished production deployment with existing user base
- Any proprietary UI/UX or product polish specific to AI Photo Forge
- Built-in Telegram audience and associated traffic
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
AI Photo Forge 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 AI headshot Telegram bot using Node.js (Fastify/Express) and Python (FastAPI) for model inference. Core features in scope: (1) Telegram bot webhook to receive photos and commands, (2) image validation and face detection, (3) call a Diffusers-based inference service (local or Replicate API) to generate headshot-style images, (4) store originals and outputs in S3 (MinIO or AWS S3) and produce expiring URLs, (5) send generated images back to users and report job status, (6) basic logging and per-user job tracking in a small Postgres database. Out of scope: payment processing, web UI dashboard, multi-tenant admin features. Require: robust error handling, retries for transient model/API failures, and unit tests for bot handlers, inference wrapper, and storage layer.
How we checked
How the score was reached
- Build verdict base78
- 3/3 assessment runs agreed+4
- Evidence score82
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 · 1
Every page the run actually retrieved.
- official productAI Photo Forge - official product
Integrity checks
What held up, and what did not.
