Image and video decision

Filmia

A competent developer can build a useful subset (templated video generation, personalization, storage and basic UI) using open-source components, but the full managed product—enterprise integrations, scale, analytics/optimization and vendor compliance attestations—is not practical to reproduce cheaply.

Visit website

Built by Borja Soler, who ships 3 products in this index

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-off116 h to build

$200/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

  • 1) render templated video creatives (combine assets, captions, scenes) into MP4 via FFmpeg and image/video generation models; 2) generate voice-over from text (TTS) and stitch to video; 3) apply per-recipient personalization (text/image replacement) and produce variants; 4) store assets and variants in S3-compatible storage and record metadata in Postgres; 5) provide a minimal HTTP API and web UI to create campaigns and trigger batch generation; 6) basic reporting endpoint (views/conversions ingestion).

What it still won’t have

  • Managed scale and latency SLAs for high-volume ad generation
  • Proprietary optimization/analytics and campaign automation workflows
  • Enterprise integrations, billing, and service-level support
  • Any proprietary/closed-source models or datasets Filmia may use
  • Certifications and attested compliance by the vendor

What remains hard

  • Compliance and regulationGDPR COMPLIANT SSL ENCRYPTED DATA ENCRYPTED AT REST EU AI ACT COMPLIANT
Read the build prompt

First-year cost

No published price

Filmia 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 video-ad generation service using Node.js (Express) backend, Postgres database, React admin UI, and S3-compatible storage. Core features in scope: (1) accept a campaign definition with a template (scene sequence, text placeholders, image slots), (2) render MP4s by assembling images/video clips and captions via FFmpeg and invoking open-source models (sdnext/diffusers) for any generated frames, (3) generate TTS audio via an open TTS service and mux to video, (4) batch-personalization engine to produce per-recipient variants, (5) HTTP API to create campaigns and trigger generation jobs, (6) store metadata and asset URLs in Postgres and S3, (7) simple analytics ingestion endpoint and a basic report page. Out of scope: multi-tenant billing, high-volume autoscaling, proprietary model training, and advanced campaign optimization. Include error handling, retries for provider calls, unit tests for core logic, and basic E2E tests for the API flow.
How we checked2 sources · 3/3 runs agreed · evidence score 54

How the score was reached

  • Partly verdict base52
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Hard moats found in the evidence-3
  • Evidence score54

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

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat quoted from the page