Skip to content
Salieno Marketplace

Build for the companies running Salieno Core.

Hosting companies run their billing, provisioning and storefront on Salieno Core. What they plug into it — the gateway that takes payment in their market, the panel they provision on, the registrar they sell domains through, the theme their customers see — comes from here. If you have built one, you can sell it.

Start with an application

Authorship is reviewed by a person, so the first step is telling us who you are and what you plan to publish.

Sign in to apply

Your Salieno account is the same one you use for licences and billing.

Four kinds of extension, and only four.

Each one has a real loading contract in Core — an entry point Core instantiates and an interface it calls. There is no “other” bucket, because that is how a curated catalogue turns into a plugin dump.

Payment gateway

Take money the way your market actually pays.

Control panel

Provision and manage hosting from Salieno.

Domain registrar

Register, transfer and renew domains through your provider.

Theme

Reskin the storefront or the client area.

A theme declares which surface it skins: the storefront, or the client area.

How a build reaches a customer

  1. 01

    You upload an archive

    A zip with a salieno.json manifest at its root: kind, name, version, entry point and the range of Core releases it supports. The upload is size-capped, hashed and statically scanned before anything inside it is trusted.

  2. 02

    A person reviews it

    Not a bot with a rubber stamp. We read the package and the listing together on a first release, oldest submission first. If the scan flags something, that is what brings a human in sooner, not what rejects you.

  3. 03

    Approval signs the bytes

    On approval we re-hash the archive and sign that exact digest with Salieno's key. A signature means a human reviewed these bytes, which is why it happens at approval and not at upload.

  4. 04

    Installs verify the signature

    Core checks the signature against a pinned public key before it runs anything. Not the connection — the artifact. An unsigned version can never go live.

We don't publish a queue time we can't hold to. What we will say is that the queue is read oldest first, a rejection always carries a reason you can act on, and a listing that comes back with changes requested keeps its place by submission time.

The money, stated plainly

Salieno keeps a platform fee

A percentage of each paid sale; the rest is yours. The rate is set by Salieno rather than hard-coded into anything, it is shown on your earnings page the moment you are approved, and the rate that applied is recorded on every individual order — so a sale you made last year keeps the split it was made under, whatever the rate is today.

We pay you directly

Save one destination — USDT or USDC on TRON, or a PayPal address — and ask for what has cleared. A person here sends it and records the transaction reference against your request. There is no account to open with anyone else and no verification queue at a third party, which matters: the payment processors that serve marketplaces like this one do not operate in most of the countries our authors write from.

Salieno is the merchant of record

The buyer's contract is with us, so you get the sale, the amount, the fee and the receipt number — not the customer's email address. Refunds are issued by us against the order and show up on your statement as a negative line.

Price freezes at first publication

Once a listing has been public, its price, currency and kind are fixed: buyers hold entitlements recorded against what they actually paid, and a refund is computed from the order. Everything presentational — name, copy, screenshots, tags — stays editable forever.

Before you apply, know these

  • A sold listing is delisted, never deleted.

    The moment one payment has been captured you can take it out of the catalogue, but you cannot remove it. Buyers keep what they bought and their installs keep working.

  • Every version must be strictly newer.

    Installs update forward. Republishing a lower number would be invisible to everyone who already has the higher one, so it is refused. Undoing a bad release is a rollback, which we do, and which says so.

  • Your support address is yours to answer.

    A listing carries your support email or URL and customers will use it. We route product questions to you, not the other way around.

  • A suspension is not cosmetic.

    If we suspend an author account, that author's published listings come down in the same transaction and no new version can ship until it is resolved.

  • Money clears before it can be withdrawn.

    A sale credits your balance immediately but waits out a hold before you can ask for it, because a refund or a chargeback can still arrive after the fact. A new payout destination waits too — that pause is what would give you time to stop a change you didn't make.

Ready when you are

An application asks for your name, the handle you want, what you have built before and which of the four kinds you plan to publish.

Build for Salieno · Salieno Marketplace