PhotonTest gives you predictable pricing based on credits – not complexity. Choose a plan that fits your workflow, or request a custom setup for your organization.
1 automated test case ≈ 30 credits (≈ 300K tokens)
1 test case execution ≈ 3 credits (≈ 30K tokens)
Photon TCM
Test cases automation and execution
Test cases generation
Photon helps you automatically generate new test cases and optimize existing ones to be more structured, readable, and AI-friendly — so your automation runs faster and smarter
Requirements analysis
We prepare your test cases in the format required for efficient automation
1 automated test case ≈ 30 credits (≈ 300K tokens)
1 test case execution ≈ 3 credits (≈ 30K tokens)
Photon TCM
Test cases automation and execution
Test cases generation
Photon helps you automatically generate new test cases and optimize existing ones to be more structured, readable, and AI-friendly — so your automation runs faster and smarter
Requirements analysis
We prepare your test cases in the format required for efficient automation
What is the difference between a token and a credit?
In PhotonTest’s billing model, a “credit” is the currency you pay with. A “token” is an internal unit of compute or work that underlies certain AI operations (for example, when processing text with a language model). Credits convert that compute (tokens plus other resource usage) into a simpler, unified billing unit. In other words, tokens measure usage inside the engine; credits measure how you pay for that usage.
How is the number of credits per test case calculated?
PhotonTest does not charge a flat fee per test case. Credits are consumed based on actual compute usage: model inference, runtime operations, and the amount of data processed. In practice, this means each test case uses a different amount of compute depending on its complexity. According to our internal usage data, an average test case typically consumes around 30 credits, though the exact number may vary depending on the models and steps involved. You always pay only for the credits consumed, not for the number of test cases.
Do I pay per test case, or only for credits used?
You pay solely for credits consumed. PhotonTest does not charge on a “per test case” basis. Whether your test suite contains a hundred or a thousand test cases — what matters is how many credits the system uses to run/generate them. This model ensures you’re only billed for actual compute resources, not arbitrary per-test fees.
Is there a limit to how many credits I can add?
PhotonTest does not impose an arbitrary maximum on how many credits you can buy or top up. You pay only for credits – you’re not capped on “number of tests.” Because credits are the billing unit, you control spend by deciding how many to purchase. As long as you add credits, you can continue to run tests.
What does the “requirements analysis” include?
The requirements analysis is a phase where Photon helps you take your high-level specifications or acceptance criteria and automatically generate structured test cases. It translates human-language requirements into executable, maintainable tests. This saves QA teams time on manual test-writing, ensures coverage consistency, and reduces human error. As with other Photon operations, you pay only for the compute credits this analysis consumes — you don’t pay per test case generated.
Can I use Photon with BYO (Build Your Own) models?
PhotonTest supports a BYO workflow, which lets you plug in your own AI models directly into the testing pipeline. Your custom or proprietary models run inside Photon the same way built-in engines do, and credits are consumed based on the compute resources your model uses. This gives you full flexibility to test the exact models you rely on, not just the ones provided out of the box.
Ready to scale your QA the smarter way?
Start free, explore your 75 test cases, and experience how Photon automates the hardest parts of testing – without locking you in