# Build brief — a focused alternative to Podia

> **Verdict:** Partly, if you narrow it · **Buildability:** 38/100 · **Category:** Creator Commerce
> **Source:** https://www.canitbevibecoded.com/podia
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Podia. Verify current pricing and capabilities before acting.

## Context

**Podia** — Creator platform for courses, digital products, email, and memberships. It currently costs $49/mo.

Selling a few digital downloads or a course is buildable, but Podia bundles checkout, file delivery, courses, email, memberships, affiliates, and support.

This brief describes a focused, single-operator replacement for the part of Podia that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Build product pages, Stripe checkout, gated downloads/course lessons, customer accounts, and email receipts.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Stripe.
- File storage.
- Auth.
- Hosted site.
- Email service.
- Course/content database.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me a small digital-products store to replace Podia, for selling a few downloads,
not running a course business. Requirements:

- Node + Express + better-sqlite3, server-rendered pages with nunjucks, deployed on my
  VPS behind my existing reverse proxy.
- Products live in products.json: slug, title, price, description, and the file to
  deliver. Delivered files sit outside the web root.
- One page per product plus a /store index. The buy button goes straight to Stripe
  Checkout (keys in .env); no cart, no coupons.
- Stripe webhook on payment: record the order in SQLite (email, product, amount,
  timestamp) and email the buyer a download link via Resend or SMTP (creds in .env).
- Download links are signed tokens that expire after 7 days or 5 uses; an expired link
  shows a resend-by-email form.
- An /admin page behind HTTP basic auth: order list and revenue per product.
- Out of scope: memberships, drip courses, email marketing, and affiliates. Do not build
  customer accounts, the receipt email is the account.
- README: Stripe webhook setup with the CLI test command, and a plain note that
  VAT/sales tax is on me, Stripe Tax exists if it matters.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Checkout/product UX.
- Course hosting.
- Email marketing.
- Memberships.
- Compliance, licensing, and legal accountability are core features.
- Reliability at the vendor's scale is an operations problem, not a prompt.

## What you still own after launch

- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.

## Risk

**High consequence.** Use this as a prototype or personal aid. Keep a qualified human and an established provider in the loop for consequential decisions.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Ghost](https://github.com/TryGhost/Ghost) — Open-source publishing and memberships; combine with Stripe/file hosting for some Podia us

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/podia