Build on Shinobi. Get paid on every install.
Every industry wants its own cards, connectors and playbooks: restaurants book tables, salons book chairs, print shops track presses. Publish yours to the App Store and earn on every workspace that installs it. Our own add-ons (PrintflyOne, Sensei, and soon Autopilot) ride exactly the same rails.
85% of every sale is yours; Shinobi keeps 15%. Founding developer terms: 0% platform share on your first $50K of lifetime revenue. Price your listing as a monthly subscription, a one-time purchase, or metered usage. All three are first-class. Payouts arrive through Stripe when marketplace billing switches on.
Components: in-chat cards built on the marker protocol: pickers, trackers, product cards, forms, staged progress. Declarative templates over Shinobi's primitives, never arbitrary script on a customer's site (the same strict-whitelist law our own SVG customization follows; that rule is what makes the store safe to open). Connectors: wire a platform's accounts, orders or tickets into the console. Packs: workflow bundles, knowledge packs, voice presets for a vertical.
The publishing lane is live in every console today: bundle composed cards, workflows and knowledge articles into an app from the App Store page, publish it internally in one click, then submit it for marketplace review. Approved listings go live in the App Store of every workspace on the platform. Installs write real entitlements, the same engine that gates Shinobi's own editions, so your app is on the moment a customer buys it. Apply below for a publisher account.
Apply to publish
Questions
With platform billing (Stripe) going live. Applications are open now so founding developers are first in the catalog. Your $50K founder floor starts counting from your first sale, whenever that lands.
Yes. Subscription, one-time, and metered are all supported listing types; metered listings report usage the same way Shinobi meters its own AI actions.
People, not queues-for-show. Every listing is reviewed by the Shinobi team before it reaches a single workspace, and the sandbox rules are enforced in code, not in policy documents.