Pricing your app

Paid apps are priced with a price book per major version line (1.x, 2.x, …). A price book offers one or more plans (editions, such as Starter and Team). The installer picks a plan and consents to its prices. Verentis bills the customer, and you earn your revenue share of every charge.

Price books

• One line per major version. Installations of 1.x are billed by the 1.x price book, even after you ship 2.x. Updates within a major keep the plan the customer consented to.
• Revisions are reviewed. Every revision is reviewed before buyers see it, and a submitted revision can't be edited. To change prices, propose a new revision.
• Two ways to author.
  • Propose the first revision in the manifest (spec.pricing; see Usage metrics & pricing). It is submitted automatically when you publish the first version of a major.
  • Edit in the developer portal: Packages → your package → Pricing → Create price book / Propose price change, then Submit for review. The API is POST/PUT /v1/packages/{packageId}/price-books[/{id}] and POST /v1/packages/{packageId}/price-books/{id}/submit.
• Packages without a price book for the installed major are free (or use the deprecated single price plan).

Plans and components

Each plan combines up to one component of each kind:

Monthly prices are prorated per day.

Tiers. Any component can be tiered.

• With graduated tiers, each unit is charged at the price of the tier it falls into.
• With volume tiers, every unit is charged at the price of the tier the total reaches.

Plan options.

Currencies. USD is required. Add other currencies to set local prices; otherwise prices are converted from USD at the platform's monthly FX rate.

Active users

A user is an active user of your app in a month if they use one of its installations at least once that month. Verentis observes activity on the platform side; you don't report it. A user counts when they:

• open one of your app's documents (the platform mints an app token for the launch);
• start or join a collaboration session in your app (WOPI or native);
• run one of your app's programs, including scheduled and triggered runs;
• use one of your app's tools through the AI assistant.

Each user counts once per month: once per account (default uniqueness), or once per workspace with uniqueness: workspace. Each user is charged as they are first seen in the month, so the bill grows with adoption rather than being estimated upfront.

Audiences

Each audience you price is a separate component. An audience without a component is free. If your app runs mostly as a service principal, decide whether to price service users or leave them free.

Reporting usage

Apps with a backend report custom metrics to price with usage components. First declare the metrics in spec.usage-metrics, then report them with the backend's own client-credentials token:

POST /v1/installations/{installationId}/usage
Authorization: Bearer <backend client-credentials token>
Content-Type: application/json

{
  "records": [
    {
      "metric": "documents.converted",
      "quantity": 3,
      "idempotencyKey": "job-8f2c:convert",
      "occurredAt": "2025-05-14T09:30:00Z"
    }
  ]
}

Retry failed requests with the same idempotency keys.

Review and effective dates

Reviewers check every submitted revision. Prices above the marketplace's guardrails are flagged for closer review, never rejected automatically. A rejection includes the reviewer's reason.

A revision that mixes increases and decreases is an increase as a whole. Until it takes effect, customers keep the previous prices and see the upcoming change on their billing page and on your package page. Accounts with an active installation are notified by email.

GET /v1/packages/{packageId}/pricing returns the active and upcoming price books for every major.

Your earnings

You earn a share of every charge for your app, including subscriptions, fees, active users, usage and minimum top-ups. The default share is 70%. Refunds and credits reverse earnings at the share they were earned with.

Next