Marketplace

Build on Glime

Extension structure and revenue share, published before the store opens — so partners can build now without fearing an architecture rework.

The marketplace storefront ships in Phase 5 of the roadmap. The listing format, extension manifest, and revenue-share terms below are final — anything built against them today will list on day one.

Extension types

Type	What it is	Distribution
Integration	Connects Glime to an external system (ERP, billing, e-sign) via the public API and webhooks	Free or paid
Pricing-rule pack	Reusable CPQ rules — dependency, exclusion, quantity, attribute — for a vertical	Paid
Industry template	Object layouts, quote sections, and document branding for a specific industry	Free or paid
AI skill	Prompt + tool bundle extending Glime AI (e.g. RFP-response drafting)	Paid

Listing manifest

Every listing is described by a single glime-extension.json:

{
  "id": "acme.netsuite-sync",
  "name": "NetSuite Order Sync",
  "type": "integration",
  "version": "1.2.0",
  "pricing": { "model": "subscription", "usd_per_month": 29 },
  "permissions": ["orders:read", "orders:write", "webhooks:subscribe"],
  "support_url": "https://acme.dev/support",
  "privacy_url": "https://acme.dev/privacy"
}

Revenue share

80% to the builder, 20% to Glime, calculated monthly on net receipts. Free extensions pay nothing. Billing, tax, refunds, and payout run through the platform — builders never touch card data.

Review policy

Permissions must be declared and minimal; undeclared API scopes fail review.
Extensions run against the API only — no direct database access exists to misuse.
Security review required for anything handling customer PII beyond Glime records.

Read the API docs Join the partner program