Local QA + security / For developers and agencies
Pro lifetime license
Generate Cypress or Playwright tests, check your source code and verify fixes from your own workstation or CI.
Test private staging and authorized client applications from your own environment. Bring your preferred AI provider or use managed cloud triage. Keep tests, reports and regression history in your project.
Whether you write the code or build with AI, understand what needs attention and test the changes you make. Keep editable Cypress or Playwright tests and evidence in your project.
Local execution · Bring your own AI keys · Your CI
$100
The work, opened up.
Test framework
home-page-greeting.cy.ts
Generated test
// Save the first name and verify the greetingcy.getByTestId('name-input') .clear().type('Ada Lovelace') .should('have.value', 'Ada Lovelace');cy.contains('button', 'Save name').click();cy.getByTestId('greeting') .should('contain', 'Ada Lovelace'); // Update the saved namecy.getByTestId('name-input') .clear().type('Grace Hopper');cy.contains('button', 'Save name').click();cy.getByTestId('greeting') .should('contain', 'Grace Hopper') .and('not.contain', 'Ada Lovelace');Fits the way your team already ships
01The team workflow
For developers, teams, and agencies turning fast-built apps into software they can test, review, and maintain.
See the setup requirements01
Point NoryBot at an application you are authorized to test. Choose Cypress or Playwright and a small, representative workflow.
Input / Application URL
02
Read the selectors and assertions. Adapt them to your product requirements, and commit the tests alongside the application.
Output / Editable test files
03
Execute the suite locally or in your own CI. Review test results and Pro security findings before deciding what needs attention.
Evidence / CTRF, JSON, Markdown
Security regression proof
NoryBot reruns the same ownership contract after a fix. The comparison keeps identity checks, owner access, and the boundary request visible at the same time.
Baseline run
Risk reproduced
Other user could read the invoice.
The setup checks pass, then the boundary request returns a protected resource with HTTP 200.
3/4
assertions passed
HTTP 200 leak
01
Identify
Two signed-in users
Owner and other user identities confirmed
02
Control
Owner requests the invoice
HTTP 200 · expected invoice returned
03
Boundary
Other user requests that invoice
HTTP 200 · protected invoice returned
same contract rerun
Verified rerun
Fix verified
The same request is blocked.
Owner access still works, while the other user's request is rejected with HTTP 403.
4/4
assertions passed
HTTP 403 blocked
01
Identify
Two signed-in users
Owner and other user identities confirmed
02
Control
Owner requests the invoice
HTTP 200 · expected invoice returned
03
Boundary
Other user requests that invoice
HTTP 403 · protected invoice blocked
Recorded evidence
The meaningful change is isolated to the cross-user resource request. The owner flow still passes after the fix.
Cypress: 2 passed · 0 failed
Playwright: 2 passed · 0 failed
Reproduced
The boundary failed in the baseline.
The other user's request returned HTTP 200.
Changed
The ownership check was patched.
The same contract was rerun without changing the assertion.
Verified
The protected resource stayed private.
The rerun returned HTTP 403 and all assertions passed.
Observed on an internal invoice fixture. This verifies the supplied assertions, not every authorization path or application. Recorded 2026-09-07. AI assessments do not change test outcomes.
02Security checks / Pro
Does the application expose avoidable security risks? What did the scan actually check? Connect findings to local evidence and supported regression tests, then compare the results after a fix.
Read the scope and limitationsweb-report.json
Illustrative finding
HTTP response / Security headers
Medium
Test client applications and private staging from a machine you control. Keep source checks, generated tests, scan history and reports in your own workspace.
No repository upload to a NoryBot scanning service. No required hosted dashboard. Your chosen AI provider receives the context needed for enabled AI features; Pro licensing connects to Polar.
On your machine
Execute code checks and browser tests from your workstation or CI runner. Reach private staging through your existing network access.
Scan scopeIn your project
Editable Cypress and Playwright tests, local SQLite evidence and exportable reports stay under your team's control. Share them when you choose.
Reports & CIWith your provider
Use your own provider account and approved model. QA context and optional redacted security evidence go to that provider. Review its retention and processing terms.
Provider configurationLocal execution does not mean completely offline. Pro license checks contact Polar, dependency audits contact registries, and optional semantic indexing uses an embedding provider. See the data destinations.
04The commercial model
QA discovery, test generation, and test runs are free. Pro adds security checks, lifetime updates, and email product support.
Use your own AI keys and pay your provider directly, or use optional NoryBot Cloud for managed test generation and security review.
Lifetime means updates and email product support for the maintained life of NoryBot. Installation, licensing, and product bugs are covered; custom test development and consulting are separate.
Billing and license documentationLifetime license
$100
USD once
Price excludes tax, calculated at checkout. AI and optional cloud usage are separate. Pro scans need internet access for license validation. After purchase, download the release ZIP and retrieve your license key in Polar Purchases.
Add credit and let NoryBot handle the AI for test generation and security reviews. No provider accounts, API keys or model selection to manage.
$10
USD credit
$25
USD credit
$50
USD credit
Requires a Pro license. Sign in, link your activated license and accept the Cloud terms to buy credits. No subscription or automatic top-up; tax is calculated at checkout. The $100 license includes no cloud credit.
Scans and browser tests run locally. Choose managed AI or use your own provider keys.
05Field notes
06Before you evaluate
NoryBot packages application exploration, framework-specific generation, local execution, and reporting into one CLI workflow. Pro adds scoped security checks. The value to evaluate is whether that repeatable workflow helps your team—not whether AI can produce test code.
Generated Cypress or Playwright tests are files in your repository. Run and maintain them with your existing engineering process. There is no required hosted test dashboard.
QA page and test context goes to your QA provider. Optional security triage sends selected, redacted findings and code evidence to its separately configured provider. Optional semantic indexing uses an embedding provider. Dependency audits contact registries, and Pro license validation contacts Polar. Generated tests and reports are written locally.
Yes, using the CLI and the selected test framework. Supply provider keys through your CI secret store. Pro has two device activations; plan license handling for ephemeral runners before adopting them.
Start with one representative flow and review the generated assertions. Establish generation reliability, maintenance effort, and scan usefulness on your own application. The current product is an early pilot, not a promise of comprehensive coverage.
Put it to work on your application
Tell us about your product or authorized client application and one workflow you want to test. We’ll help you start with a release ZIP and your own AI key. Free QA needs no paid license; your tests and evidence stay in your project.
Request a pilotEmail support@norybot.com with your application and workflow.
Open the pilot setup guide Get Pro · $100 once