Plan: Enterprise
Partner API & webhooks
Per-store keys, a fixed ability catalogue, and a secret shown exactly once
9 capabilitiesSee the detail
Channels & delivery
App marketplace
Installing is minting a key — there is no second permission system
An app store is the partner API plus distribution. A developer registers an app declaring which abilities it needs, and a platform admin reviews it. The store owner sees those abilities in plain language before anything is minted. Installing mints a partner key with exactly the abilities consented to; uninstalling revokes it — and there is no second auth system anywhere in the product.
From the Enterprise plan up
What this covers
- The supply side — developer registration, app submission declaring the abilities needed, and platform review
- Consent — the owner sees the exact abilities in plain language before agreeing, from the same translated ability catalogue the key-management screen uses
- Install mints a partner key with exactly the approved abilities; uninstall revokes it
- Re-consent — an installation is pinned to a version; a version wanting more stays pending until the owner agrees, and the app keeps running on its older, narrower key
- A revenue-share ledger with a frozen rate per row, one-time charges at install and monthly rows from a scheduled command
- A launch catalogue of five first-party listings, each pointing at a connector that already exists in the product
Where this stops
- The marketplace runs on a first-party launch catalogue. The external developer programme is open, but the catalogue is not yet as deep as the largest competitors’.
We write this here because finding it out during implementation is far worse than reading it now.
Related features
All featuresSubscription & billing
Your plan, your limits, your invoices — and entitlements cached so the till works offline
8 capabilitiesSee the detail
See it on your shop
Thirty minutes on your products, your tax setup and your hardware — not a slide deck.