Using qeti
Current practices · September 27, 2026
Trial and availability
qeti is in early access. The trial includes 3 completed checks over 7 days from the first admitted test, once per workspace. No card is required and it does not turn into a paid subscription automatically. Free trials share 5 starts per UTC day and 100 per calendar month. All workspaces have a limit of 5 test starts per UTC day. Tests are subject to shared capacity; there is no start-time or completion-time guarantee.
What your allowance covers
Each check tests one saved flow. A passed check, confirmed failure, or flaky result with evidence uses one check. Automatic verification retries are included in that check. Technical failures, inconclusive results, and cancellations return the check credit, but admitted tests still count toward the daily start limit.
Monthly subscriptions
The current price and allowance are shown in Plans and confirmed in Stripe before purchase. Monthly subscriptions renew until you cancel. Unused checks do not roll over and there are no automatic overage charges. Cancel renewal in Manage billing; active paid access continues until the displayed period end. Evidence keeps its original expiry date. Payments are processed by Hamurabi Saas and your statement may show HAMURABI.
Authorized testing only
Connect only applications and repositories you are authorized to test. Use staging, synthetic data, and dedicated test accounts. Do not submit production payment credentials or use tests to make real purchases.
Your release decision
A verdict applies only to the journeys evaluated in that run. Inconclusive and flaky results need review. Evidence scores are heuristics, not guarantees. Your team remains responsible for reviewing findings and deciding whether to release.
Integrations and external services
Enable an integration only for destinations your team controls. Connected services may have their own limits and charges. qeti does not automatically upgrade your provider accounts.
Early-access scope
qeti tests the flows you configure. It does not replace all quality assurance, provide a dedicated human tester, or guarantee that your app is free of bugs. The recorded example uses synthetic data and does not start a live test.