Publish your model. Get paid when it earns.
If you trained, tuned, merged, or meaningfully shaped a set of weights, the OMLA License keeps your model free for researchers and hobbyists — and puts 30% of commercial value back in the hands of the people who made it. Publishing is a browser flow you can finish in an afternoon; payment comes straight from the commercial user to you.
From weights to on-the-record in five steps
1. Sign in
Create an OMLA account. It anchors your registrations — your signature is bound to it, so nobody can replay your work as theirs.
2. Publish
The wizard generates your Ed25519 keypair in the browser, takes the SHA-256 hash of your weights, records lineage, and signs the registration. Your private key never leaves your machine — keep it safe; OMLA cannot recover it.
3. Set up your wallet
Your omla1… wallet names the payment destination you already have — Stripe, PayPal, Lightning, ACH, SEPA, or Wise. Verification checks the address and requires a usable destination.
4. Declare the split
Allocate exactly 30 points across your contributors and any direct base models. Solo work on an original model? All 30 points are yours.
5. Watch it work
Your model appears in the public registry with a compliance badge. When commercial users report usage, statements with your share land in your earnings dashboard.
If it's you, a GPU, and a good idea
- Keep your reach. Non-commercial use stays free, so researchers, students, and hobbyists can keep building on your work without asking.
- Use the payment account you already have. No new financial infrastructure — your wallet points at your own Stripe, PayPal, Lightning, or bank details, and users pay you there directly.
- Your details stay private. Wallet destinations and split tables are not public registry data — they surface only on the statements sent to the specific user who owes you.
- Derivatives owe you too. When someone builds a commercial fine-tune on your model, their declared split must credit you as a direct parent — and OMLA computes your share on their reports.
- No copyleft, no telemetry. You can keep private fine-tunes private; the license asks only that commercial use pays its royalty.
If a whole team put work into the weights
- One split table, every contributor. The 30-point creator pool divides across as many verified wallets as your team needs — allocation is explicit, exact, and recorded at registration.
- Provenance that survives an audit. Registration signs the SHA-256 weight hash and the exact license version into an immutable record, and every subsequent change lands in a hash-chained audit log.
- Statements your finance team can use. Amounts are computed in exact cents, statements are versioned with the payee details snapshotted at publish time, and corrections supersede rather than overwrite.
- Base-model credit is structural. Lineage is a strict parent-child graph; a derivative's split must include its direct parents, so upstream labs are paid by design, not by goodwill.
- Crypto-agile identity. Signing is Ed25519 today; the verification path already supports hybrid ML-DSA-65 post-quantum signatures for when clients catch up.
How the 30-point split pays out
Every model divides its creator pool — 30% of a commercial user's royalty basis — using a table that must sum to exactly 30 points. Suppose you fine-tuned a base model and declared 18 points to your own wallet and 12 points to the base model's creator. A user reports a quarter with a $10,000 basis:
| Payee | Points | Amount owed |
|---|---|---|
| You (fine-tune creator) | 18 | $1,800.00 |
| Base-model creator (direct parent) | 12 | $1,200.00 |
| Creator pool (30% of $10,000) | 30 | $3,000.00 |
Split recipients must be the model's own verified wallets or its direct lineage parents, and a statement is only published against verified payees — the math fails closed rather than paying the wrong person.
What's still in progress
OMLA is in public beta and builds in the open. Richer payment-method display, in-browser post-quantum signing, and publishing SDKs are on the roadmap; the FAQ covers splits, lineage, and worked payout examples in more depth; and the operative License §3–§5 is the binding text behind everything on this page.