Websites and hosting decision

Pixpa

A capable developer can build a useful subset (site + galleries + Stripe checkout) over weeks, but reproducing Pixpa's polished visual editor, template catalog, managed hosting, print-lab fulfilment and support at the same level is non-trivial—so DIY is viable for a narrow workflow but not a full replacement.

Visit website
You pay

$5.4/mo

$65/yr

Read off the official pricing page.

You’d pay instead

$100one-off80 h to build

$30/mo10 h/mo upkeep

On cash alone, building overtakes the subscription at 8 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 Pixpa alternatives, with the arithmetic →

What a replacement has to do

  • Allow a creative to publish a portfolio site, share private client galleries with proofing/favouriting, and sell images/products via a checkout.

What it still won’t have

  • 200+ designer templates and polished visual editor experience
  • Built-in print-lab auto-fulfilment (WHCC) integration
  • 24/7 real-human support and managed onboarding
  • Tuned image pipeline (automatic AVIF/WebP) and turnkey CDN hosting
  • 100+ pre-built app/integration catalog and marketing tools

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 8 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 portfolio+galleries+store using Next.js + Tailwind, Postgres (or Supabase), S3-compatible storage, CloudFront (or Cloud CDN), and Stripe. In scope: user accounts, publishable pages from a block-based editor, a template system with at least 5 starter templates, image upload + automatic WebP/AVIF conversion and responsive derivatives, private client galleries with multi-user favouriting and expiring links, product listing and Stripe checkout, blog posts with SEO metadata, and basic order/contact forms. Out of scope: print-lab auto-fulfilment, WYSIWYG visual designer parity with Pixpa, multi-language integrations, and a 100+ app marketplace. Include authentication, access controls for galleries, server-side image processing, background jobs, sensible tests (unit + integration for core flows), error handling, logging, and a Docker-based deploy with Terraform/CloudFormation examples and a one-page README for setup.
How we checked4 sources · 3/3 runs agreed · evidence score 67

How the score was reached

  • Partly verdict base52
  • An open-source build was found+5
  • 4 cited sources+3
  • Price verified on pricing page+3
  • 3/3 assessment runs agreed+4
  • Evidence score67

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✓ 3 independent runs, one answer✓ Citations limited to fetched pages! 1 moat recorded