Frequently Asked Questions

Every listing states the versions the author supports, and it is the author who wrote that line, not an automatic guess. If your setup is unusual, ask before buying — the messaging is open before the sale, not only after it.

When the author provides a demo, a link sits on the listing and opens a working version. There are no trial licences: a digital file cannot be taken back, so we would rather you look at a real demo than download something you cannot return.

The product files, the author’s documentation, and a licence file naming your order. The listing must describe what is included, and a description that promises more than the archive holds is one of the main reasons we refuse a product.

Yes. The archive is inspected before publication: secrets left in the code, obfuscated files, dependencies that do not exist, and archives that are simply broken. It is not a security audit and we do not pretend it is — it catches the obvious, and the obvious is most of it.

From the author, not from us. We host the catalogue, take the payment and issue the licence, but the product is theirs and so is the support. Their name and their shop are on every listing, and you can write to them before buying.

Because the author sets them and keeps all of it. Elsewhere a large share of the price goes to the platform, so the author has to price for that. Here they do not, which is why the same work can carry a different number.

The author’s price, plus our service fee, plus VAT where it applies. All three are shown separately before you pay, never after. The fee is ours; the author receives their price in full.

By card, through Stripe. You get an invoice for every order, and you can add a company name and a VAT number to your account before buying so they appear on it. The product is invoiced by its author, the service fee by us — two lines, two issuers, both on the same document.

Yes, and it is not a marketing trick. Your licence key, your invoice and your downloads live in that account, and a dispute or a licence transfer needs somewhere to happen. Creating it takes an email address and a password, nothing else.

Look in your account before looking in your inbox: the licence and the download appear there the moment the payment is confirmed, without waiting for an email. If the order is not there either, write to support with the card’s last four digits and the date.

Yes. Put the company name and the VAT number in your account before you order and they appear on the invoice. Adding them afterwards means reissuing the document, which is possible but slower — set them once and forget it.

In your account, under your licences. Every purchase stays there with its key and its download, and you can download it again as many times as you need — a new machine, a lost file, a server rebuilt. There is no download limit and no expiry on that page.

Yes, from your account settings, and your purchases follow. Do it rather than opening a second account: two accounts mean your licences are split across both, and nobody can merge them afterwards.

It depends on the licence you choose, and the number is written on the listing before you buy. A licence covers a domain and every subdomain under it, so moving from example.com to shop.example.com costs nothing. Test and staging addresses never count.

Yes, and the licence page on each listing says on how many sites. What matters is who ends up holding the licence: if the site is the client’s, the licence should be transferred to them, otherwise their site depends on your account. Transferring takes one step from your licences page.

No. You may use the files in the work you deliver, but you may not share them, resell them, redistribute them or pass your licence key to anyone. Doing it ends your licence without refund, and the author can come after you directly — the product is theirs, not ours.

No. A licence is bound to a domain, not to a server, an IP address or an installation. Move the site wherever you like; as long as the address does not change, nothing does.

No. What has an end date is the updates, not the right to use what you bought. A product you paid for in 2026 still runs in 2031 — it simply stops receiving new versions once the update period is over.

We cannot, and that is deliberate: we never store your key in a readable form, only a fingerprint of it. What you can do is regenerate it from your licences page. The old one dies at that moment, so change it in your installation right after.

No. localhost, the .local and .test endings, and the usual dev., staging. and preprod. prefixes are all recognised as trial addresses and consume nothing. Build, break and rebuild as much as you like.

At least twelve months on every product, often more, and the exact figure is on the listing before you buy. Security fixes are part of that commitment, not an extra. When the period ends the product keeps working — you simply stop receiving new versions.

The author, through the messaging built into the site, so the exchange is kept and can be used if a dispute follows. We do not provide technical support on the products themselves — we did not write them, and pretending otherwise would waste your time. What we do handle is the order, the licence and the dispute.

The new version appears on your licences page with its date and the author’s note on what changed. You download it there; nothing installs itself on your site without you.

Each shop displays the response time its author committed to. Past that, open a dispute: it puts the exchange in front of us, and an author who stops answering their buyers does not stay on the catalogue.

No, nothing forces you. But when the author flags a release as a security fix, treat it differently from a new feature: an unpatched extension is one of the most common ways a site gets taken over.

Your licence stays valid and your download stays available. What stops is the updates and the support, because those depend on a person. This is true of every marketplace; the difference is that we say so before you buy.

European law gives you fourteen days to change your mind on a digital purchase — but that right ends the moment you download the file, and we ask you to confirm that you understand before the download starts. After that, a refund depends on the product being broken or not being what was described.

From the order, in your account. You state what is wrong, the author is notified and answers in the same file, and we read both before deciding. Everything stays written down, which is the point.

The author has a few days to answer, then we decide. It is a person reading, not a rule firing, so a complicated case takes longer than a simple one — but you get the reasons in writing either way, and you can contest them.

You can, but it is slower and blunter. A chargeback takes weeks, costs the author a fee whether they were right or wrong, and closes your account here. A dispute opened on the site is read within days and can end with a full refund. Try that first.

A human being, here, reading both sides. Not a score, not an automatic rule. The buyer opens a case, the author answers, and we decide with the reasons written down. Either of you can then go to a court or to an out-of-court body, and the terms say which ones.

Nothing. You set your price and you receive it in full. Our revenue is the service fee the buyer pays on top, shown to them before payment. There is no listing fee and no subscription required to sell.

A verified identity, a Stripe account in your name, and a product that passes our checks — the archive is inspected for secrets left in the code, obfuscation and obvious breakage before it goes live. European law requires the identity check; the rest is what keeps the catalogue worth browsing.

Forty-eight hours is what we commit to, and most are faster. A first submission takes longer than an update, because the identity check happens at the same time.

Yes. We neither impose a floor nor suggest a number, and we will never change your price to make a sale more likely. The buyer sees your price and our fee as two separate lines, so raising yours never hides anything.

Yes, and it is a reasonable way to be discovered. A free product still goes through the same checks and still carries a licence, because you may want to know where it ended up and to stop it if it is abused.

Yes. Nothing here is exclusive, and we will never ask you to take your work off another marketplace. You keep every right on what you wrote; we are given the right to sell it here, and nothing more.

You get the reasons in writing, point by point, and you resubmit once they are fixed. There is no limit on attempts and no penalty for a refusal. Most refusals are the same three things: a secret left in the code, a dependency that does not exist, or a description that promises more than the archive contains.

You can unlist it at any moment, and it stops being sold immediately. What you cannot do is take it away from the people who already paid: their licence stays valid and their download stays available. If you no longer want to maintain it, unlist it and say so — that is far better than leaving it to rot on the catalogue.

Yes, and it is the one commitment we hold you to: answer through the messaging within the response time displayed on your shop, and ship at least twelve months of updates including security fixes. You choose that response time yourself. Announce two days and answer in two — an honest slow is worth more than a fast you cannot hold.

One account, one shop. If you sell under two brands, the cleanest answer is two accounts with two identities and two Stripe accounts — which is also what the law expects, since the identity behind a sale has to be the real one.

The payment is created directly on your own Stripe account, never on ours, and released fourteen days after the sale to cover the withdrawal period. We are not the holder of your funds at any point. If this marketplace vanished tomorrow, the money already collected would still be yours.

You do. You are the seller, so your tax obligations are yours: we collect no tax on your behalf and we give no tax advice. What we give you is the data — every sale, every country, exportable — so your accountant has what they need. Ask one if you sell across borders; the rules are not intuitive.

If the refund happens during the fourteen-day hold, the payment simply never leaves. After that, the amount is taken back from your Stripe account, and the service fee the buyer paid is refunded too — we do not keep our part when a sale is undone.

No. An individual can sell, and many do. What you do need is a verified identity and a Stripe account in your own name. Whether your country expects you to register a business for that income is a question for your own tax office, not for us.

Because we take nothing from the author. Most marketplaces keep between 30 and 80 percent of what a developer charges. We keep none of it, so the platform has to be paid somewhere, and we would rather it be visible on your side than invisible on theirs.

Payment is handled entirely by Stripe. We never see your card number and it never touches our servers. What we keep is the order, the licence and the invoice, which we are legally required to hold.

On servers in Europe, and the privacy page lists every item we hold, why, and for how long. It was written from the code rather than from a template, so what it says is what actually happens.

Money already collected is in the authors’ own Stripe accounts, so it stays theirs. Buyers keep the files they downloaded and the rights they bought. What would stop is this site: the catalogue, the licence checks and the disputes. We would rather you knew that now than discover it later.