Image and video decision

Postpix

A competent technical user can build and operate a one-user replacement in about a week using existing image models and payment integrations; the vendor's proprietary style tuning and polished templates are the main things you'd forfeit.

Visit website

Built by mitch, who ships 5 products in this index

You pay

$9/mo

$108/yr

Read off the official pricing page.

You’d pay instead

$100one-off38 h to build

$20/mo3 h/mo upkeep

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

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

  • Take a markdown blog draft, detect image placeholders, generate prompts per section, call an image-generation API to create images, return images and decrement user credits.

What it still won’t have

  • Proprietary tuned "Ghibli-style" model and any vendor style filters
  • Packaged premium templates and UI polish (bulk generation UX, advanced templates)
  • Priority/24/7 support and white-label/enterprise features

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 4 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 minimal self-hosted Postpix-like web app using Node.js + Express, React, Postgres, and S3-compatible storage. Core features: 1) Upload or paste markdown and detect image placeholders; 2) Convert each section to an image-generation prompt using a small templating layer; 3) Integrate with a third-party image generation API (configurable endpoint) to generate images and store outputs; 4) Implement user accounts, a credit wallet, and a Stripe-based one-time pack purchase flow; 5) A simple editor UI showing markdown with generated images and ability to bulk-generate; 6) Persist posts, images, and credit transactions in Postgres; provide error handling, retries for API calls, basic unit and integration tests, and deployment scripts for Docker on a single VPS.
How we checked1 sources · 2/3 runs agreed · evidence score 81

How the score was reached

  • Build verdict base78
  • Price verified on pricing page+3
  • Evidence score81

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.

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