What are SQAI Credits?
SQAI Credits are the usage currency of the SQAI Suite. Every task you run, from a chat message to a full traceability map, consumes a set number of credits.
Why we moved away from tokens
Token-based consumption is unpredictable by design. The number of tokens a request consumes depends on prompt length, document size and a range of factors that you control directly. That makes AI spend genuinely difficult to forecast by our customers.
Over the past months we analysed every type of usage across SQAI Suite, grouped it into categories, and assigned each category a fixed credit value. The result is a cost model where:
Everyday, high-frequency work is priced as economically as possible.
Specialised, high-output actions cost more, in proportion to what they produce.
You can calculate your expected annual consumption in advance.
Action costs
Action | Unit | Credits (on average) | Number of runs on The Scale Plan |
Generate diagram | per module or page set | 2,5 | ≈10,800 |
Generate test cases | per subsystem's documentation | 4,5 | ≈5,500 |
Documentation drift | per document checked | 5 | 5,000 |
Generate test automation | per test case | 28 | 892 |
Traceability health map | per run — tickets vs codebase | 164 | 152 |
Generate documentation | 5 sections in one run | 249 | 100 |
The above table is made on 21/08/2026 and is subjective to change as new features will be added. Two things are worth noticing in this table:
The work you do most is the cheapest. Diagrams, test case generation and documentation drift checks, the actions that make up the bulk of daily work in SQAI, sit at the bottom of the scale. This is deliberate. These are the operations teams run continuously. Traceability mapping and test automation generation for example, are the most credit-intensive operations in the suite . They're also the two that produce your highest-value assets: your audit evidence and your executable test suite. A traceability health map reconciles your ticket history against your codebase in a single run; test automation turns test specification into runnable code. The credit cost reflects the depth of the work involved.
What's included in your license
Included credits are allocated for the full 12-month license term, not per month. You are free to use them at whatever pace suits your team, a quiet quarter followed by an intensive release period is entirely fine, and there is no monthly cap to work around.
Why the spend is predictable
Everyday work is the cheapest part. A full year of daily drift checks, 100 diagrams and 100 test-case runs together use under 8% of a Scale license.
Two actions carry the weight. Traceability mapping and test automation . They also produce your two highest-value assets: the audit evidence and the executable suite.
Real-time spend analytics. Built-in analytics show credit consumption on company-, workspace- and user level in real-time. So, spend is visible long before renewal.
How codebase size affects credit use
The credit values above are measured against a reference codebase of 190,932 lines across 1,800 files. Credit use scales ×2 and ×4 for codebases of roughly double and quadruple that size.
This mainly affects the codebase-wide operations like documentation generation, drift, traceability health maps and test automation generation. If your codebase is significantly larger than the reference, factor the multiplier into your annual budget planning, and speak to our Customer Success Managers about the right pricing tier.
Where your credits live: company-level quotas
Quotas are company-level: one shared balance across all your spaces.
This means:
You don't need to divide or pre-allocate credits between spaces.
A team that has a heavy month doesn't need a quota transfer to keep working.
Your license and credit balance are managed in one place, under your company settings.
Tracking your usage
Built-in analytics show credit consumption as it happens, at three levels:
Company: your total balance and consumption against your annual allocation.
Workspace: which teams and spaces are consuming what.
User Level: keep track of individual credit consumption in your space statistics
Because consumption is visible in real time, there is no scenario where usage becomes a surprise at renewal. If your team's pattern changes mid-term, you'll see it in the analytics long before it becomes a problem.
Credit Overage Packs
If your team needs more credits than your license includes, extra overage packs can be bought whenever the team needs more.
Pack | Price | Discount |
10,000 credits | €1,000 | List price · minimum overage pack |
25,000 credits | €2,250 | 10% discount |
50,000 credits | €4,250 | 15% discount |
Overage packs stay valid for 24 months from the date of purchase.
This is deliberate: if your team has an intensive period followed by a quieter one, the credits you bought don't disappear at your next renewal. They remain available across two full license terms.
There is no variable, consumption-based billing at any point.
Will my team need an overage pack?
In most cases, no. Every pricing tier includes a standard credit allocation, sized against how teams actually work in SQAI. If your usage pattern does look like it will exceed your allocation, you won't have to work it out alone or discover it at the wrong moment.
Our Customer Success Managers monitor usage alongside you.
If you're tracking your limit, our CSMs contact you personally.
You review your actual consumption together and calculate live whether an overage pack makes sense, and which size fits.
You can also start that conversation yourself at any time, our CSMs are happy to run through your numbers and help you plan the year.
Frequently asked questions
Does the same action always cost the same number of credits?
No,credit values are not fixed per action type and may vary with contextualization or prompt length. An additional variable (in case of code -related tasks) is the size of the codebase being analysed — see above how codebase size affects credit use.
Are credits consumed per month or across the whole term?
Across the whole term. Your included credits cover the full 12-month license period, with no monthly cap.
Can different spaces run out of credits independently?
No. Quotas are company-level, so all spaces draw from one shared balance.
Can I see which team is consuming the most?
Yes. The built-in analytics break consumption down by company, workspace and individual run.
How long do overage credits last?
24 months from the date of purchase, longer than a single license term, so credits survive a quieter period.
Is there a minimum overage purchase?
Yes, the 10,000-credit pack at €1,000 is the minimum overage pack.
What if my codebase is much larger than the reference codebase?
Credit use scales ×2 and ×4 for codebases of roughly double and quadruple the reference size. Our CSMs can help you model this before you commit to a tier
What happens when my balance reaches zero? Y
our workspaces will be locked for usage until a credit overage pack has been purchased. Do keep in mind that our CSMs will have reached out multiple times before this occurs, to avoid your workspaces from locking up.
Do unused included credits carry over at renewal?
No, pricing plan credits outside overage packs are not carried over at renewal
Getting help
Questions about your own usage or license tier: contact us or your Customer Success Manager directly.
Questions about how credits work: the rest of this support portal section covers usage categories and analytics in more detail.
Anything else: [email protected]
Keep in mind that within every pricing plan, credit usage is according to our fair use policy.