Aikido: why reviewing 160 PRs a month may require an initial $500 USD top-up
Teams already using Aikido and planning to add Deep Review need to calculate review consumption separately from cash spent on top-ups. Each PR costs 1 credit, but manual top-ups have a 500-credit minimum; checking the wallet balance first is especially important for small trials.
For teams already using Aikido Security, budgeting for Deep Review means more than asking how much each pull request (PR) costs. The official documentation charges credits per PR, while wallet purchases have a separate minimum quantity. Teams planning infrequent trial use should check their balance before deciding whether to top up. This article examines only that incremental expense; platform subscription fees, taxes and consumption by other features are excluded from the example.
160 reviews: consumption and payment are separate calculations
Aikido's Deep Review documentation states that each PR costs 1 credit; additional reviews after new commits to the same PR do not cost extra. The budget should therefore use the number of distinct, billable PRs, rather than the number of commits. The wallet documentation specifies that 1 credit equals $1 USD, each manual purchase has a minimum of 500 credits, and the balance does not expire.
Suppose a team needs to review 40 unique PRs each week for 4 consecutive weeks, starts with a balance of 0, receives no free credits, and has no other features drawing on that balance. This is a budget scenario, not a record of measured usage. Consumption is 4 × 40 = 160 credits, equivalent to $160 USD. If the team chooses a manual purchase, however, the minimum initial payment is $500 USD. Buying 500 credits leaves 340 credits at the end of the month.
If the team reviews another 160 unique PRs the following month, with no other consumption or added credits, it does not need to buy again and has 180 credits left. The remaining balance is not a review expense already consumed, nor should it be counted again in each month's cash outflow. For a team that only wants a one-off small trial, the key question is whether it is willing to put more money into the wallet upfront than it needs for the current period, rather than whether each review looks cheap.
Automatic top-ups do not immediately refill an insufficient balance either
The automatic top-up documentation lists a minimum of 100 credits, but this is a different purchasing route and cannot replace the 500-credit threshold for manual purchases. It uses invoicing, and credits arrive only after payment. Before adopting this route, check whether the workspace meets the activation requirements and make sure the person responsible for payment knows when to handle the invoice.
When the balance is exhausted, Deep Review skips reviews. Purchase limits and feature spending limits separately control how much is bought and how much is used: limiting purchases does not mean limiting review consumption, and setting a feature limit does not guarantee money in the wallet. Teams need to check the balance, payment status and whether reviews actually ran, rather than directly interpreting no feedback as no problems.
First estimate consumption from the number of unique PRs in a normal work cycle, subtract the confirmed available wallet balance, and then choose a purchasing method. If the aim is simply to find out whether Deep Review is worth adding to the existing review process, start with a smaller trial and record which checks actually helped the review before deciding on a long-term budget. This usage example does not establish review quality or the value of replacing human review.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:help.aikido.dev