Pricing

Specmatic Plans

Pro

$550/month

Enterprise

$3,500 /month

Which API specifications do you use?*

Note: AsyncAPI, gRPC, GraphQL, RESP & JDBC are only available for Pro & Enterprise Licenses.



0
2500


1
6250


1
2500

One last step!

Our licensing is based on three key parameters

1. Seats

  • The license includes a specified number of active users (“seats”), which can be used by Architects, Developers, Testers, DevOps Engineers, or Product Managers who will use any Specmatic product.
  • To provision their license, each user will log into Specmatic Insights via SSO and download a unique license file, which is required to activate Specmatic products.
  • CI/CD agents will authenticate via a service account and do not consume seats.
  • Admin users can deactivate licenses if needed (Ex: when users leave the organisation).
  • As the users, use Specmatic features locally, their usage data will be shipped to insights. This will help Admins understand the adoption and engagement metrics.

2. Number of API Specs

  • This parameter limits the number of unique API specification files (OpenAPI, AsyncAPI, GraphQL SDL, Protobuf) that can be used in CI/CD.
  • When Specmatic is executed as part of CI/CD, spec file details are reported to Insights to track the total number of unique API spec files in use.

3. Daily CI/CD Runs

  • This parameter sets the maximum number of times Specmatic can be run via CI/CD pipelines in a single day.
  • Admin can create any number of service accounts for CI/CD agents to execute Specmatic.
  • If your cumulative (across all service accounts) daily CI/CD run threshold is exceeded, we will not block CI/CD runs (to avoid any impact on critical release workflows). However, users will be temporarily blocked from running Specmatic locally for the rest of the day. This usage returns/resets within the licensed threshold the following day.

Threshold Management

Specmatic Insights allows you to configure notifications when you approach or exceed your licensed thresholds, enabling proactive management and uninterrupted usage.

Prorated Billing and Tier Adjustment

If additional licenses are required during the prepaid period, and the increased quantity results in a new pricing tier, then future charges for all licenses (existing and new) will be recalculated at the new tier rate for the remainder of the prepaid period. Any unused portion of your original payment will be credited toward the new total.

Example Calculation:

Suppose you purchase 1,000 licenses for one year. Amount paid for 1,000 licenses (1 year): $156,248 USD

Scenario 1:

After 4 months, if you need 500 additional licenses (total now 1,500 licenses):

  1. Value of 1,000 licenses used for 4 months:
    ($156,248 × 4/12) = $52,083 USD
  2. Credit for unused 8 months (original payment):
    $156,248 – $52,083 = $104,165 USD (credited toward new purchase)
  3. Cost of 1,500 licenses for 8 months (at new rate):
    ($164,498 × 8/12) = $109,665 USD
  4. Additional amount due:
    $109,665 – $104,165 = $5,500 USD

Scenario 2:

After 4 months, if you need 200 additional licenses (total now 1,200 licenses):

  1. Amount paid for 1,000 licenses continues as is.
  2. Cost of 200 additional licenses for 8 months (at current rate):

    ($13 * 200 * 8) = $20,800 USD

  3. Additional amount due: $20,800 USD

Our licensing is based on three key parameters

  1. Seats

  • The license includes a specified number of active users (“seats”), which can be used by Architects, Developers, Testers, DevOps Engineers, or Product Managers who will use any Specmatic product.
  • To provision their license, each user will log into Specmatic Insights via SSO and download a unique license file, which is required to activate Specmatic products.
  • CI/CD agents will authenticate via a service account and do not consume seats.
  • Admin users can deactivate licenses if needed (Ex: when users leave the organisation).
  • As the users, use Specmatic features locally, their usage data will be shipped to insights. This will help Admins understand the adoption and engagement metrics.
  1. Number of API Specs

  • This parameter limits the number of unique API specification files (OpenAPI, AsyncAPI, GraphQL SDL, Protobuf) that can be used in CI/CD.
  • When Specmatic is executed as part of CI/CD, spec file details are reported to Insights to track the total number of unique API spec files in use.
  1. Daily CI/CD Runs

  • This parameter sets the maximum number of times Specmatic can be run via CI/CD pipelines in a single day.
  • Admin can create any number of service accounts for CI/CD agents to execute Specmatic.
  • If your cumulative (across all service accounts) daily CI/CD run threshold is exceeded, we will not block CI/CD runs (to avoid any impact on critical release workflows). However, users will be temporarily blocked from running Specmatic locally for the rest of the day. This usage returns/resets within the licensed threshold the following day.

Threshold Management

Specmatic Insights allows you to configure notifications when you approach or exceed your licensed thresholds, enabling proactive management and uninterrupted usage.

 

Prorated Billing and Tier Adjustment

If additional licenses are required during the prepaid period, and the increased quantity results in a new pricing tier, then future charges for all licenses (existing and new) will be recalculated at the new tier rate for the remainder of the prepaid period. Any unused portion of your original payment will be credited toward the new total.