VyroAI

Loading...

Buying a Project

Paying credits for someone else's plugin: what you get, what you keep, and where it lives afterwards.

What is for sale

Some public projects carry a price. When they do, the project's page shows what you get for it — the compiled .jar, or the jar plus the full source — and the download waits behind it.

Prices are in credits, the same credits you spend on generating, and every price on the page is written with the real money underneath it so you always know what you are agreeing to.

Buying is not switched on yet

Today, buying does not go through. Pressing Buy for … credits first opens a confirm window: the price with the money under it, what you will have left, what you get, and a box to tick — I want it right away, and I understand I can't cancel once it's mine. The buy button stays greyed out until that box is ticked. Confirm, and the window closes with Buying is not switched on yet — The plugin marketplace is still being built — nothing was charged.

That is the whole message: nothing was charged, no credits left your balance, and there is nothing wrong with your account or the project. The rest of this page describes how buying works once it is switched on.

What you are promised

Buying is once, and three things come with it:

  1. The current build, whenever you come back. Download the seller's latest kept build any time. You never buy it again.
  2. New versions while the seller ships them. Each time they build, your download becomes that one.
  3. Your receipt survives the seller leaving — the download does not. If they delete the project or close their account, their builds go with it: your purchase stays on record, but there is no build left to download. That is one more reason to keep your own copy (see below).

You get the seller’s latest build, not every build

The Bought shelf lists the builds a seller has published and marks two of them so you can tell them apart at a glance: what you bought, and any build that is new since you bought.

What it does not do is keep the older jars. The app says so on the purchase panel itself: "Each time they build, your download becomes that one. Older jars are not kept." A new build by the seller replaces the file you were downloading, and the one it replaced is deleted.

So if a particular build matters to you — the one you tested your server against — download it and keep your own copy. Your purchase and your receipt never expire; the jar files can — older ones as soon as a new build replaces them, and all of them if the seller deletes the project or leaves.

Where your purchases live

Everything you have bought is on your profile under Bought. Each row links back to the project and downloads the current build.

When a seller has deleted the project or left, the row turns amber and reads The seller is gone — you still have this, adding that every build is still downloadable. Only the receipt part is true: the builds went with the project, so the row's button reads No build yet. When there have been builds since you paid, the row marks them new since you bought.

Nothing there expires, nothing renews, and there is no "your access ends".

Before you press buy

The panel answers the awkward cases rather than showing a button that cannot work: it steps aside on your own project, tells you when your balance will not cover the price, asks you to sign in first if you are a visitor, and hands over to the ordinary Download button on something you already own.

Where to next

18 of 31 in Account & Billing · Last checked 11 September 2026 · Previous: Spending Limit