Sign up

For creators

You wrote the code. Everything after it is our problem.

Checking, licence keys, device binding, checkout, invoices, VAT, refunds and payouts all run on our side. You upload a build and set a list price: you receive 85% of it per licence, the buyer pays 115% of it, and nothing is charged until something sells.

Apply as a creator See a sample certificate
release pipeline Live
01Formal checksubmission + identity
02Static scansource code
03Backtestour market data
04RobustnessMonte-Carlo
05Scoringyour declaration
06Decisiona person
seal sha256 7d41…9b0c compiledopen source
your economics delivery: compiled
Your list price€100
Service fee · 15%− €15
Buyer pays€115 and VAT, as one total
You receive · 85% $85

Per licence, after payment clears. The buyer pays your list price plus a 15% service fee and VAT by their country, shown to them as one total. Price and delivery mode are fixed once the product is admitted.

No fee to apply
No fee to be checked
No fee to list

The wall

Your code is finished. The hard part isn’t.

This is what a stranger is thinking while they read your thread. None of it is unfair — you would think the same thing. And none of it is answerable by you, which is the actual problem.

“He picked the period.”

True, and you cannot disprove it with another screenshot. Only a test on data you never saw can.

“Nobody has read that code.”

Also true — and publishing it is not the answer you want to give. Someone has to read it independently of you.

“Looks like the last three that blew up.”

You are being priced with everything else in the category, because there is nothing on the page that separates you from it.

“Fine — but what happens at version 1.5?”

Trust you spent months earning resets on release day, every release, for as long as you sell this way.

You cannot vouch for yourself. That is not a marketing problem and no amount of copywriting fixes it. It needs verification independent of you, with a method and a published record.

Before you submit

The three we send back most often.

Anonymised, straight from the reports:

The manifest described one entry point. The build shipped with a second one.
An outbound call to a host that appeared nowhere in the declaration.
Parameters fitted to the exact window it was tested on. One month either side and it stopped working.

None of these is a verdict on you, and two of the three are usually accidents. Each one comes back as a report naming the stage, the finding and the case that broke it — fix it and resubmit, as many times as you need. Failing costs nothing and publishes nothing: certificates go public, rejections never do. The six steps, in order →

Your code

Read once, by us, and it goes no further.

The check is not possible without reading the source, so the only honest thing to do is say exactly who reads it, what happens to it afterwards, and what we are never able to do with it.

What we do with it

Your source is analysed against your declaration — dependencies, network calls, file access, risk sizing — and anything the analysis cannot settle on its own is flagged for a person. The build is then run on periods we hold back, hashed, and sealed. A reviewer signs the result off before it publishes. The certificate reports findings, never code.

what we analyseyour source, not a binary
who signs it offa person, on every submission
where it is storedthe review environment, nowhere else
what the certificate showsfindings and scope, not source
what a buyer seesonly what you chose to publish

What we cannot do with it

Not promises about intent — limits written into the agreement you sign before anything is uploaded. You keep every right to your software; Viroan never takes ownership of your code.

publish your sourcenever, unless you choose to
reuse it in anything of oursprohibited, in writing
pass it to another creatorprohibited, in writing
modify the build we sealthe hash would stop matching

And you choose the delivery mode, per version: publish the source when openness is what sells the product, or ship it compiled and licence-locked when it is not. The check reads it either way — publishing is a decision about how you sell, never a condition of being listed.

Creator economics

You set one number. You receive 85% of it.

The fee is split across both sides of the sale: 15% comes out of your list price, and another 15% is added to what the buyer pays. Stated plainly, because you will do this arithmetic anyway — and because nothing at all is charged before a sale: applying, the check and the listing are free, pass or fail, and there is no monthly fee on either side.

€85You receive

85% of the €100 list price, on every licence sold

€30Viroan

15% out of your side, 15% onto the buyer’s

€115Buyer pays

and VAT by their country, shown to them as one total

On a €100 list price: you receive €85, the buyer pays €115, and the €30 between the two is ours — 30% of your list price, 26% of what the buyer actually pays. VAT at the rate of the buyer’s country is included in the one total the buyer sees and never comes out of your side. The exact figures and the payout schedule are in the creator agreement, which is the document that governs, not this page.

What the €30 pays for

Everything between your build and a paid licence. Not visibility: featured placement and search priority are separate paid features, clearly marked as paid, and buying them never touches your score.

the check, every versionsix steps
licence issuing & device bindingour side
invoices, receipts, VAT filingour side
hosting the listing and the certificateour side

What we will not put on a landing page

Two things belong in a signed document, not in marketing copy.

payout schedule and minimumscreator agreement
reporting we are obliged to filecreator agreement

You read and sign the creator agreement before your first listing goes live. Nothing about payouts is decided by a sentence on this page.

The obvious objection

Thirty percent is a lot.

It is, and it is more than the marketplaces you are already selling on take. Those charge around 20%, out of your side only. We are not going to argue that number down or dress ours up, so here is the comparison you would run anyway — on what each side actually does, drawn from published terms rather than opinion.

Where this is sold todaycompiled-binary marketplaces
Heresix steps, then a published record
what gets analysed
A compiled binary. The platform never receives the source, so it cannot examine it.
Your source, read against the scope you declared in writing. Compiled delivery to buyers is still your choice.
who decides
The pre-test. Passing it ends the process.
A person, on every submission, from the report and whatever the analysis flagged — and they can stop a listing the machine was happy with.
the test
An automated pre-test: a formal check for known programming errors, then a run on historical data.
Simulation on periods we pick and hold back from you, then stress: gaps, spreads, fee changes, outages.
who picks the settings
The seller. Period, costs and parameters come from the submission.
We do. Fees, spread, slippage and funding are counted in, not optional.
what the buyer reads
Your description and your figures.
A certificate with our findings and our name on it — including the four things the check did not cover.
at version 1.5
The same automated pre-test, again.
Back through all six steps before it reaches a single buyer.
out of your side
~20%
15%
onto the buyer’s side
—
15%

Read as a fee, ours is ten points worse. Read as what it buys, the ten points are the difference between a shelf where every product is a screenshot and a shelf where every product has been verified independently of its creator. And it is €15, once, per licence sold — not per month, not per listing, not per submission, and nothing at all when a build fails.

The part we cannot prove yet. Your product will list 15% above the same product on a marketplace that does not check anything. We are betting that a checked product converts better when it sits next to unchecked competition, and that the buyers who pay for software rather than pirate it are exactly the ones who read a certificate. That is a reasoned bet, not a measured result: the marketplace has no sales history, so anyone quoting you a conversion number today — us included — would be making it up. You are pricing higher into a market that has not been tested. Decide with that in front of you.

And if the real objection is the review itself — that you do not want anyone outside reading your source, at any price — that one we cannot solve for you, and we are not going to try. The check is the product. Sell where a compiled binary is enough, and treat this page as a thing to come back to if that stops working.

What runs on our side

Four things you don’t have to build.

The shop

Your product

Licence issuing, binding and revocation

A key per order, bound to the devices the buyer is entitled to, revoked when a refund settles. You never write a line of it, and you never hold a key.

creator/licensing · liveHandled

ISSUElic_8f21 → order #4471

BINDdevice fingerprint · slot 1 of 2

REVOKElic_7a03 · refund settled

PAYOUTqueued → creator ledger

issuing, binding, revocation and the ledger run on our side

A new version means a new check

Buyers keep running the build that was sealed, so a release cannot quietly change what somebody already paid for. An update re-enters the pipeline before it reaches anyone, and the certificate is reissued with it — which is also the end of trust resetting every release.

v1.4.0sealed · buyers run this build
v1.5.0in check · step 3 of 6

Checkout, invoices and VAT

Licences for a term in months or for a lifetime, sold to the buyer by Viroan, which issues the invoice.

01invoices02VAT by country03receipts04payout ledger

One inbox, and most of it never reaches you

Anything about money, access or the certificate is ours. What is left is the part only you can answer.

how the strategy behavesrouted to you
refund requestshandled by us
licence and device problemshandled by us
payment disputesnever reach you

Before you apply

What we need from you.

Six things. Five are paperwork you already have. The sixth is the only one we cannot bend on.

a build that runscompiled or source
a manifestentry point, deps, parameters
declared scopemarkets, timeframes, venues
declared risk per tradeand we check the code
the limits you already knowwhere it does badly
identity verificationbefore anything publishes

Two things people ask before they upload: price and delivery mode are locked once the product is admitted, and a new version does not reopen them — existing licences keep the terms they were sold under. And a refund request never reaches you: Viroan handles it as the seller. A refund for a defect, or because the buyer withdrew as the law allows, comes out of your share of that order; a refund caused by Viroan does not.

The one that is not negotiable: the build cannot change what it does after we seal it. No remote switch, no configuration fetched at runtime that alters behaviour. If a sealed build can become a different build, the seal means nothing — and the seal is the entire product.

Get it checked.

Applysubmit a buildpass the checkget paid

Apply as a creator

No fee to apply · no fee to be checked · no fee to list · the fee exists only on a sale, and the buyer pays it