Pricing
The English user guide is currently in beta preview. Most of the documents have been automatically translated from the Japanese version. Should you find any inaccuracies, please reach out to Flatt Security.
Takumi Pentesting is billed on a credit basis. Each assessment workflow you run consumes credits from your organization's credit balance.
Credit Model
A base subscription includes a monthly allowance of credits. Each assessment workflow consumes a variable number of credits depending on the size and complexity of the target. The Takumi API uses the same credit pool — workflows triggered via the API are billed identically to workflows triggered from the web console. See Takumi API > Pricing & Billing.
For current per-credit unit pricing and your organization's credit allowance, open Settings > Takumi in the Shisho Cloud console.
What Consumes Credits
Every Takumi feature that uses AI internally consumes credits. Consumption is roughly proportional to LLM token usage, so it scales with the size of the target and the number of assessment perspectives Takumi applies.
Representative examples:
- Whitebox Assessment: Depends on the number of functions in the target and the number of assessment perspectives applied.
- Blackbox Assessment: Depends on the number of target endpoints and the number of assessment perspectives applied.
- Auto-Triage: A small amount of credit per Dependabot PR triaged.
- Autofix: Depends on the size of the fix target.
This is not an exhaustive list. Any other feature that runs AI inference internally also consumes credits.
Controlling Consumption Per Run
Credit consumption within a single assessment run is controlled by a credit limit. Setting an appropriate initial limit lets you cap unintended consumption and commit more credits incrementally as you watch progress. For how to set the limit and what happens when it is reached, see Quickstart > Completing an Assessment.