Skip to content

Marketplace

Publishing on the marketplace

The Hedlo Marketplace lists plugins, themes, email templates and invoice templates for Loom, Bolt and Shuttle. Anyone with a verified account can publish free items. Selling paid items needs a verified identity.

What you can publish

KindWorks withContains
PluginLoom, Bolt, ShuttleCode that uses the product's plugin API, with its native manifest
ThemeLoom, BoltColour tokens, fonts and storefront sections
Email templateBolt, LoomSubject and body templates for one or more notification types
Invoice templateBoltThe invoice and credit note layout

Before your first upload

  1. Create a marketplace account and confirm your email address.

  2. Turn on two-factor sign-in. Publishing is blocked without it.

  3. Create a publisher profile, either for yourself or for an organisation. Organisations can invite members and give them roles: owner, maintainer or finance.

  4. Install the Hedlo CLI and run hedlo login.

The package manifest

Every package has a hedlo.json file at its root, next to the product's own manifest (for example loom-plugin.json).

{
  "id": "acme.backups",
  "kind": "plugin",
  "product": "loom",
  "version": "1.2.0",
  "name": "Offsite backups",
  "summary": "Copy every server backup to S3-compatible storage.",
  "categories": ["backups", "storage"],
  "readme": "./README.md",
  "changelog": "./CHANGELOG.md"
}
  • id is vendor.name and must start with a vendor prefix you own. The marketplace reserves it on your first upload.

  • version follows semantic versioning and must match the version in the product manifest.

  • kind is plugin, theme, email-template or invoice-template. product is loom, bolt or shuttle.

  • Run hedlo validate to check the package before you upload it.

Review

Every new version is reviewed before anyone can install it, including updates to items that are already listed.

  1. Automated checks run as soon as you upload: manifest and version rules, size and file limits, file types, declared capabilities against the code, known malware signatures and leaked secrets.

  2. Human review follows. A reviewer installs the version in a clean test installation and checks that it does what the listing says and uses only the capabilities it declares.

  3. The result is approved, changes requested with notes, or rejected with a reason. You can reply to the reviewer in the review thread.

  4. Approved versions are signed with the marketplace key and published. Installations that trust the marketplace key accept them.

Reviewers never review packages from their own publisher.

Selling paid items

Paid items unlock when both of these are true:

  • You have two approved free items on the marketplace.

  • Your publisher profile has passed identity verification. This runs through Stripe and asks for your legal name, address, date of birth and a bank account, or the company's details for an organisation.

You then choose a price for each item. The marketplace sells to the customer, keeps the platform fee shown in your dashboard and credits the rest to your publisher balance.

Balance and withdrawals

  • Each sale is credited to your balance as pending. It becomes available once the refund window for that sale has passed.

  • Request a withdrawal of your available balance at any time from the publisher dashboard. It is paid to the bank account connected during verification.

  • Refunds and chargebacks are taken from your balance. The dashboard lists every credit and debit with its sale, so you can reconcile each payout.

  • Download monthly statements and the tax forms that apply to you from the Tax page.

Discounts

Create discounts for your own items from the dashboard:

  • Sales lower the price of chosen items for everyone between a start and an end date.

  • Codes give a percentage or fixed discount to customers who enter them, with an optional limit on uses and an expiry date.

The platform fee is calculated on the price the customer pays after the discount.