Can KFA Marketplace be vibe coded?
Run a small used-keyboard market for a community you already have
The software is the vibe-codeable part: listings, cart, Stripe checkout, shipping labels, seller payouts. An agent can stand all of that up in a focused implementation, and the consolation prompt below does. What it cannot stand up is the market. KFA is a two-sided used-keyboard exchange where every board passes through a warehouse for inspection and PCB testing before the buyer sees it, and the fee pays for that inspection and for the crowd on both sides. A clone launches empty.
Jump to the build brief ↓Legacy-calibrated assessment
Checked Aug 2026
high editorial confidence
Tracked separately from the pricing check
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- List used keyboards with photos and condition notes, take Stripe Checkout payments, buy shipping labels for sellers, and track each board from sold to delivered.
- Manage a small catalogue and checkout flow for products you fulfil yourself.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- liquidity: buyers and sellers who are already there, which is the product
- warehouse QC: every board is inspected and its PCB tested before delivery
- buyer protection backed by that inspection instead of a seller's photos
- payout operations: KYC, earnings ledgers, and withdrawal handling
- The buyer and seller network cannot be generated with code.
- The value comes from the people already using it.
Build, switch, or keep paying
Narrower, with trade-offs
List used keyboards with photos and condition notes, take Stripe Checkout payments, buy shipping labels for sellers, and track each board from sold to delivered.
Use the build brief ↓2 checked options
- r/mechmarket ↗Where used keyboards already trade for free; protection is seller flair, PayPal G&S, and your own skepticism.
- Mercur ↗Multi-vendor marketplace software you deploy yourself; vendors, buyers, and the warehouse remain your problem.
Recommended
Nobody pays KFA for its Django code. Sellers pay 6.5% + $1 to reach buyers without eating scam risk, and buyers pay 6.5% for a used board that a human has opened, inspected, and PCB-tested before it ships. The free alternative is r/mechmarket, where trust is flair count and PayPal disputes; the fee is the cost of turning that into a guarantee.
Visit KFA Marketplace ↗Why people still pay
Nobody pays KFA for its Django code. Sellers pay 6.5% + $1 to reach buyers without eating scam risk, and buyers pay 6.5% for a used board that a human has opened, inspected, and PCB-tested before it ships. The free alternative is r/mechmarket, where trust is flair count and PayPal disputes; the fee is the cost of turning that into a guarantee.
The buyer and seller network cannot be generated with code.
The value comes from the people already using it.
Trust, audits, and counterparties matter more than feature parity.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to KFA Marketplace
Context
KFA Marketplace — Run a small used-keyboard market for a community you already have.
The software is the vibe-codeable part: listings, cart, Stripe checkout, shipping labels, seller payouts. An agent can stand all of that up in a focused implementation, and the consolation prompt below does. What it cannot stand up is the market. KFA is a two-sided used-keyboard exchange where every board passes through a warehouse for inspection and PCB testing before the buyer sees it, and the fee pays for that inspection and for the crowd on both sides. A clone launches empty.
This brief describes a focused, single-operator replacement for the part of KFA Marketplace 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
List used keyboards with photos and condition notes, take Stripe Checkout payments, buy shipping labels for sellers, and track each board from sold to delivered.
Manage a small catalogue and checkout flow for products you fulfil yourself.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Stripe account.
EasyPost account.
Public HTTPS deployment.
Email provider.
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 two-sided marketplace for used mechanical keyboards like KFA Marketplace, for a community I
already have. Requirements:
Django + SQLite, server-rendered templates with vanilla JS, no frontend framework, one process.
Sellers post listings: board name, condition notes, up to 8 photos, a fixed price, and a shipped weight in
pounds. Single quantity, sold means gone.
A /moderate queue: new listings stay hidden until I approve them.
Stripe Checkout for purchase; verify the webhook signature and mark a listing sold only when the payment
event lands, not on redirect.
On sale, buy a label through the EasyPost API from the seller's address and the listing weight, then email
both sides the tracking link.
A seller ledger: each sale credits the seller's balance minus a fee percentage from .env; a /payouts page
shows what I owe whom, paid out by hand and recorded manually.
Stripe and EasyPost keys in .env; Django's built-in auth for buyers and sellers, no telemetry, everything
on my own server.
Out of scope: escrow, buyer protection, dispute flows, and inspecting anything. Trust between strangers is
my problem, not the app's.
README with setup, stripe listen webhook config for local testing, and the fee math.
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:
Liquidity: buyers and sellers who are already there, which is the product.
Warehouse QC: every board is inspected and its PCB tested before delivery.
Buyer protection backed by that inspection instead of a seller's photos.
Payout operations: KYC, earnings ledgers, and withdrawal handling.
Fraud and dispute handling when a deal goes sideways.
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
Manageable. A personal version is realistic if you test the critical journey and keep reliable backups.
Editorial confidence in this assessment: high. No reviewed project implementation is linked yet.
Existing alternatives
Before building, compare these checked options:
r/mechmarket — Where used keyboards already trade for free; protection is seller flair, PayPal G&S, and your own skepticism
Mercur — Multi-vendor marketplace software you deploy yourself; vendors, buyers, and the warehouse remain your problem
Prior art
Working open-source software you can read, fork, or borrow from before starting:
Medusa — Active open-source commerce platform with modular checkout and fulfillment primitives
django-oscar — Domain-driven e-commerce framework for Django, the stack KFA itself runs on
Generated by Can It Be Vibe Coded? · Full report: https://www.canitbevibecoded.com/kfa-marketplace
You still own the product
- 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.
Projects built from this idea
No reviewed implementation has been linked for KFA Marketplace yet. A submission is evidence for review, not automatic proof that the whole product was replaced.
Built a version of KFA Marketplace?Submit the project as evidence for this report.
Open-source prior art
Before you start
Can KFA Marketplace be vibe coded?
Not faithfully. The software is the vibe-codeable part: listings, cart, Stripe checkout, shipping labels, seller payouts. An agent can stand all of that up in a focused implementation, and the consolation prompt below does. What it cannot stand up is the market. KFA is a two-sided used-keyboard exchange where every board passes through a warehouse for inspection and PCB testing before the buyer sees it, and the fee pays for that inspection and for the crowd on both sides. A clone launches empty.
What can an AI coding agent reproduce from KFA Marketplace?
List used keyboards with photos and condition notes, take Stripe Checkout payments, buy shipping labels for sellers, and track each board from sold to delivered. Manage a small catalogue and checkout flow for products you fulfil yourself. A responsive interface with real empty, loading, success, and error states.
What will a DIY KFA Marketplace replacement still be missing?
liquidity: buyers and sellers who are already there, which is the product; warehouse QC: every board is inspected and its PCB tested before delivery; buyer protection backed by that inspection instead of a seller's photos; payout operations: KYC, earnings ledgers, and withdrawal handling; The buyer and seller network cannot be generated with code.; The value comes from the people already using it.
What do I still own after building a KFA Marketplace alternative?
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.