April 22, 2025
Definition of Snyk Platform Access - Billable Credits & Rate Card
Capitalized terms used, but not defined herein, shall have the meaning as set forth in the Customer’s governing services agreement, or other applicable documentation found on docs.snyk.io.
Learn how Snyk Platform Access is managed using the Snyk Platform Access Subscription model.
To get started using Snyk, contact your Snyk Account Representative. Your sales representative will provide you with further details.
Snyk Platform Access Overview
Simplify security management with Snyk Platform Access, which unifies Snyk Code, Open Source, Container, and IaC under a single license. Deploy these products instantly without contract modifications, enabling rapid response to security incidents and evolving threats. Our flexible credit system lets you allocate resources precisely where needed, eliminating administrative overhead. Rate changes, including new products or pricing adjustments, are announced 30 days in advance through your Billing and Usage dashboard.
If you are on the legacy Snyk licensing model, refer to this page for information on your pricing plan.
Understanding credits and tests
The Snyk Platform Access plan uses a credit system. You can redeem these credits for services, and they are then deducted from your credit balance. Credits must be used within the term of their order. Any unused credits will expire and cannot be redeemed, refunded, or credited. Credits are not redeemable for cash and cannot be transferred.
If you run out of credits, you agree to negotiate in good faith with Snyk to purchase additional credits and settle any outstanding consumption.
Billable events
Billable events draw down credits and are based on what Snyk considers monitored tests, assets, fixes, & users. Please see more detail below for information on these categories.
Monitored and Unmonitored tests
What is considered a monitored test (billable)?
Monitored tests are billable events. Snyk manages monitored tests to help with prioritization, reporting, and compliance. The results of these tests are stored on the Snyk platform, which generates Snyk issues.
The historical record provided by monitored tests allows teams to track issues over time, prioritize fixes based on severity, generate detailed reports, and ensure compliance with security standards.
The following test actions are considered monitored tests:
Test Category | Test Action | Definition | Billable |
---|---|---|---|
Monitored | Using the Snyk UI or API to schedule a recurring test (the default for all SCM imports via the Snyk UI). Running `snyk monitor` to schedule a recurring test Running ‘snyk code test —-report` to upload Snyk results Triggering a manual re-test from the Snyk UI Commit to monitored branch | Snyk tests which generate issues stored inside the Snyk Platform. These tests help manage and scale your program, risk posture, and compliance. Monitored tests help you stay secure as changes occur to your code, snyk rule enhancements, or newly discovered vulnerabilities or Zero-day events. | ✔ |
A product-specific, detailed list of actions that are considered monitored tests and are therefore billable is provided below:
Snyk Open Source | Snyk Code | Snyk Container | Snyk IaC |
---|---|---|---|
CLI monitor SCM import (Within the UI and through the API) Recurring tests Manual retest (via UI *screenshot below) Push event SBOM monitor | CLI test (with upload beta) SCM import (Within the UI and through the API) Recurring tests Manual retest (via UI *screenshot below) Push event | CLI monitor SCM import (Within the UI and through the API) CR import Recurring test Manual retest (via UI *screenshot below) Manual retest (via CR) Kubernetes integration Push event (using a Dockerfile) SBOM monitor | CLI scan (using --report) SCM import (Within the UI and through the API) TF Cloud import Recurring test Manual retest (via UI *screenshot below) Manual retest (using Terraform Cloud) Push event |

More information on assets, fixes, and users to come as new products are released and put on the platform.
What is considered an unmonitored test (not billable)?
Unmonitored tests are not billable. They offer immediate feedback without saving results in a central location. They can give you feedback directly or be part of a development process, but they're not meant to store information long-term.
The following test actions are considered unmonitored tests:
Test Category | Test Action | Definition | Billable |
---|---|---|---|
Unmonitored | IDE | Tests executed by the integrated development environment (VS Code, JetBrains, etc.) Snyk integration, within a user’s IDE. | X |
Unmonitored | Snyk Test | Checks projects for vulnerabilities and license issues. The test command tries to auto-detect supported manifest files with dependencies and test those. Eg: User enters in snyk test in CLI Note: There are specific snyk test commands for the Snyk Code, Container, and IaC scanning methods: code test, container test, and iac test | X |
Unmonitored | PR | Tests triggered by submitting a Pull Request (PR) within Source Control Manager (SCM) | X |
Rate Card
Snyk Platform Credits are structured as follows for Monitored Tests:
Product | # of Tests Per Credit Unit |
---|---|
Snyk Open Source | 10 |
Snyk Code | 1 |
Snyk Container | 10 |
Snyk IaC | 10 |
As new products and features are made Generally Available (GA), they will be added to the Platform Access Rate Card and available in the Snyk Platform for credit-based usage.
Credit Usage Policy
Snyk Platform Credits or “Credits”, as designated on this Order, form part of Customer’s Subscription Allocation. When Credits are applied, the number of Credits required to redeem services are deducted from Customer's Credit balance. Credits must be used within the term of this Order, after which any unused Credits will expire and cannot be redeemed, refunded, or credited. Credits are not redeemable for cash and are non-transferable. Upon Customer's exhaustion of its Credits, Customer agrees to engage in good faith negotiations with Snyk to purchase additional credits and otherwise true-up Customer's consumption.