Payments & Digital Goods
LiveSell access to documents worth paying for.
The problem
Selling one document is disproportionately hard. A storefront, a payment processor and a delivery mechanism is a weekend of work for a file somebody would happily pay six dollars for, and every existing route either takes a cut for hosting a whole audience or requires the buyer to make an account first. So most people give the file away, or never publish it.
No listing fee, subscription, or payout minimum
Anonymous checkout through Stripe
Issued only after a verified payment
How it works
Selling a single document usually means standing up a storefront, a payment processor and a delivery mechanism for one file — so most people give the file away instead. Link Drop is the smallest thing that closes that gap: a drop is a file, a price between $1 and $500, and a link. Buyers never register, which removes the step that loses most of them; they pay, a Stripe webhook confirms it, and the server mints a signed download URL that expires in sixty seconds. Sellers are paid on a weekly schedule after a short clearing hold, because chargebacks arrive long after the sale does.
Documents only — PDF, plain text, CSV, Markdown, spreadsheets and slide decks, up to 25 MB each and 20 files in one drop. Anything between one and five hundred dollars. Preview images can be attached so a buyer sees something before paying.
That is the entire storefront. The drop has its own page, and it can also appear in the public directory for people who are looking rather than arriving.
Checkout runs through Stripe with no account step, which removes the point where most buyers leave. A webhook confirms the payment before anything is released.
The server issues a signed download link that expires in sixty seconds — long enough to download, short enough not to be worth resharing. The seller keeps 80% and is paid weekly.
What it does
Engineering
The part of a build that is worth reading is rarely the feature list. These are the calls that shaped the product, and the reasons they were made.
The revenue split, payout logic, moderation and signed-URL issuance all have to run with privileged database access behind our own authorisation checks — never in the client. So the client speaks GraphQL to a server that enforces the rules first and reaches the database second, with row-level security as the second line rather than the only one.
No images, no video, no archives, no executables. That removes the primary vectors for content abuse from the product entirely and keeps storage small, which is a better trade than moderating everything the internet can upload.
It is encryption at rest, TLS in transit, and short-lived signed URLs — not end-to-end. True client-side encryption is incompatible with anonymous buyers, because an account is where the key would live. Saying so is better than implying a guarantee the design cannot make.
A sale's net becomes payable after a clearing hold and pays out on a weekly schedule, so a refund landing after the money has left does not leave a negative balance to chase.
Limits
Every product page lists what the software can do. This one lists what it cannot, because that is the half you would otherwise find out afterwards.
Questions
Also from the studio
Next step
Tell us what the software has to do and who it is for. We come back with a scope, a first milestone, and a number. Discovery is free and commits you to nothing.