About Specksy — Creator Marketplace Codebase
Two-sided marketplace with escrow, disputes and payouts. Built, never launched.
A complete marketplace platform for digital products and commissioned creative work. 474 commits, finished to production standard, never launched. No users, no revenue, no customer funds held. You’re buying the codebase and the time it represents, not a business. Working end to end Listings for digital goods and for commissioned services with packages, revisions and a delivery clock Order lifecycle: brief → delivery → revisions → completion, with escrow and a buyer-protection hold before funds release Disputes and refunds with admin adjudication; an open dispute freezes the seller payout Seller dashboard: overview, orders, listings, earnings & payouts, reviews, storefront editor, support, settings Buyer side: checkout, order workspace, secure downloads Messaging inbox with attachments and custom offers Reviews with verified-purchase enforcement and creator reputation Support desk: help centre, tickets, dispute cases Admin: analytics, finance, users, moderation VAT handling, invoice generation, paid listing promotions Transactional email and in-app notifications Payments are an adapter, not the architecture. The marketplace runs on a double-entry ledger — balances, escrow holds, settlements, refunds and payouts are all currency-agnostic. Only 12% of source files and 27% of migrations touch payment rails at all. Currently wired to on-chain settlement on Ronin (RON/PIXEL): deposits, balances, withdrawals and treasury sweeps, all working. Card payments are not built. Adding Stripe means one new currency value and a deposit/withdrawal adapter against the existing ledger — the escrow, dispute, refund, VAT and payout logic above is untouched by that change. The Web3 layer can be kept or removed. Stack. TypeScript · React 19 · TanStack Start · Bun · Supabase/Postgres · Cloudflare Workers · Tailwind Numbers. 1,205 files · 198,000 lines of application code · 63 routes · 166 SQL migrations · 311 unit-test files · 49 Postgres integration suites run against real Postgres, not mocks. Not a template. Row-level security on every table, server-side authorisation on every money path, bounded error handling so database internals never reach the browser. Included: full source, complete git history, database schema and migrations, design assets. Good fit for: a head start on a Fiverr/Gumroad-style marketplace, or a reference implementation of escrow and disputes done properly.
Project details
Website: https://specksy.xyz/
Video 1: https://youtu.be/TXdPGlY9GPk
Next step: <p>Easiest route is to aim it at one niche. Categories, commission rate, currencies and branding all live in config, so you can re-skin it for whatever people sell to each other: design assets, audio, 3D models, templates, code, tutoring, freelance work.</p><p><br></p><p>First job for a buyer is adding a card processor. Stripe Connect drops in fairly cleanly because the escrow hold, release schedule, refunds and payouts already exist and are tested. You're swapping the payment rail, not rebuilding the logic around it.</p><p><br></p><p>After that it's getting sellers on board. That's the hard part of any marketplace, and it's the part no amount of code solves for you. At least you won't be spending the first two months building the plumbing.</p><p><br></p><p>The crypto payment rail is built and switched off by default. Turn it on if your market wants it, ignore it otherwise.</p>
For sale
Asking price: $4,900 USD
What's included
Domain name, Source code, All related design work, Twitter account, Email account, All related data
Also included: the Supabase project (database, schema and all 166 migrations), the Cloudflare Workers deployment, the Discord server, and the full design assets. Plus a written handover - architecture notes, how the money flow works end to end, and the deployment runbook. I'll stay reachable for 30 days after the sale for questions.
Reason for selling
I am busy with other things and no longer have time to maintain this project.