Creator and commerce decision

CarteCadeaux

A capable technical user can reproduce the core gift-card storefront and delivery workflow in ~34 hours and maintain it cheaply; no strong durable moats are evident and an open-source project exists to shortcut implementation.

Visit website
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-off34 h to build

$30/mo3 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 CarteCadeaux alternatives, with the arithmetic →

What a replacement has to do

  • Customer selects a gift card product and denomination -> checkout & payment -> assign a digital code from inventory -> deliver code by email/WhatsApp -> record order and allow refund/Support.

What it still won’t have

  • Existing supplier relationships and negotiated wholesale pricing
  • Established brand trust and customer reviews
  • Built-in fraud-detection / chargeback handling tuned to this business
  • Scale operations and vendor agreements for a broad catalogue
  • Localized payment/reconciliation workflows already in place

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

CarteCadeaux 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 small Django + PostgreSQL web app deployed on a single small cloud VM (DigitalOcean/AWS t3a.small). Core features in scope: public product catalog with region/value variants; admin CSV upload for code inventory and automatic assignment on purchase; checkout integrated with Stripe (or a local payment gateway) and order records; templated email delivery (SendGrid) and optional WhatsApp webhook/send; user auth and order history; admin dashboard for refunds and code management. Out of scope: multi-merchant marketplace, automated wholesale replenishment, advanced fraud-scoring. Include error handling for failed payments and deliveries, unit/integration tests for checkout and inventory assignment, and Docker-based deploy scripts.
How we checked2 sources · 3/3 runs agreed · evidence score 88

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 2 cited sources+1
  • 3/3 assessment runs agreed+4
  • Evidence score88

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 recorded